ButteryStancakes-BarberFixes icon

BarberFixes

Fixes several issues with Barbers. Now allows restoring spawn behaviors from previous versions of the game.

Last updated 3 months ago
Total downloads 162761
Total rating 14 
Categories BepInEx Monsters Bug Fixes
Dependency string ButteryStancakes-BarberFixes-1.1.0
Dependants 181 other packages depend on this package

This mod requires the following mods to function

BepInEx-BepInExPack-5.4.2100 icon
BepInEx-BepInExPack

BepInEx pack for Mono Unity games. Preconfigured and ready to use.

Preferred version: 5.4.2100

README

Barber Fixes

All players need to have this mod installed.

Fixes bugs with the Barber:

  • Fixed the Barber AI so it actually functions when multiple Barbers spawn.
    • In vanilla, only the first Barber spawned would work as expected. Any future Barbers would slide around with no sound or animations and then eventually get stuck in place.
  • Fixed some unsafe code in the Barber AI, causing them to freeze in place and generate errors in the console.
    • This doesn't happen in vanilla because the code responsible doesn't run at all (due to the first bug)
  • Fixed all Barbers (sometimes) freezing in place indefinitely when the first Barber kills someone that isn't the host.
  • Fixed drumroll sometimes being desynced from the first jump that happens after a player is killed.
  • Fixed the drumroll playing (and overlapping the immediate "parade" sound) when a Barber first spawns.

Also adds some config settings to re-enable certain behaviors:

  • OnlyOneBarber - When disabled, up to 8 Barbers are allowed to spawn in one day, like before v62. In vanilla, Barbers have been spawn-capped at 1, likely to hide the synchronization issues mentioned above.
  • SpawnInPairs - When enabled, Barbers will spawn in groups of 2, like "intended" in the first v55 beta. VentSpawnFix is REQUIRED for this to function!
  • DrumrollFromAll - When enabled, all Barbers will do a drumroll before they "jump." In vanilla, only the original Barber plays the drumroll. It's unclear whether this is intended or an oversight (the code is inconclusive)