v2.0.1 — Hotfix
This patch addresses several bugs introduced in v2.0.0’s hunter system and resolves a compatibility issue that prevented the mod from loading on some SPT 4.0.13 installs.
Bug Fixes
Hunter kill counter overflow
The hunter eliminated notification could display counts beyond the actual number of hunters (e.g. 7/2). PMC kills after all hunters were dead continued incrementing the counter. Both the counter and the hunter detection slot are now capped correctly.
Mod failing to load / TypeLoadException on raid start
Notifications are now resolved entirely at runtime via reflection with no compile-time type references.
Bot spawning mod interference (ABPS / DONUTS / SWAG)
The hunter detection window was too wide (±60s), causing PMC waves from other bot spawning mods to be misidentified as hunters. The window is now tightened to ±15s around the fingerprinted spawn time
Hunter count hardcoded on client
The client was hardcoding hunter count and spawn chance values instead of reading from config.json. Changes to EscortCount, SpawnDelay, BaseChance, ChancePerSurvival, and MaxChance in the config now take effect without a recompile.
Changes
- O key scan: Hunter status now shows
Hunters in raid. or No hunters this raid. — kill count removed
- Debug menu (F12): Added Force Hunters toggle to guarantee hunter spawns every raid for testing
Notes
The HunterStripPatch (which removes hunter spawns when the roll fails) is logging a warning on some installs — investigation ongoing. Hunters still function correctly when the roll succeeds. If you see Could not find BossLocationSpawn list in your BepInEx log, hunters may occasionally spawn even when the roll fails; this does not affect any other functionality.
