Full concept MODIFICATION of S.T.A.L.K.E.R. Call of Pripyat that touches every game aspect including textures, sfx, music, weapons, A.I., items, weather, mutants, difficulty and much much more!

Forum Thread
  Posts  
Army of mutants (Games : S.T.A.L.K.E.R.: Call of Pripyat : Mods : MISERY : Forum : General subjects : Army of mutants) Locked
Thread Options
Oct 15 2017 Anchor

So I encountered something interesting at the jupiter plant. A literal mutant army, like, you know somethings wrong when you kill two controllers and four more show up to replace the first two. Or the uh, 30+ zombies behind them or the 60+ zombies patrolling the outskirts of the plant itself. I'm uh, not sure what's going on there but, somethings wrong here and I have no idea as to what.

jasper34
jasper34 MISERY PR Lead
Oct 15 2017 Anchor

We are still trying to determine what we can do to prevent this happening sometimes. If a spawn zone looks to see if it is still occupied and the squad spawned there immediately were drawn out of the spot, it may be repopulating it.

What you can try if you come across one of these situations is:

Open the xrs_debug_tools instructions for enabling are here Dropbox.com

Go to the advanced tab of the xrs_debug_tools an enter axr_dynamic_spawn.del_distant_squad(true) and execute it.

This will empty you map of all non-story squads and a few others which might cause crashes if deleted while engaged. New squads will fill every zone, but only one squad each. This normally occurs each time you change maps. You can also leave the map and return ASAP and most of that kind of stuff should clear.

Oct 15 2017 Anchor

I went to zaton and came back and it didn't fix it so I guess I'll have to do the debug thing. As much as I love fighting the armies of the undead and mutants galore, it's getting a bit silly.

Update: the command nor switching areas worked.

Final update: This ones a bit of a bitch too, save file's busted. The amount of stuff, (this time I fought no less than 14 blood suckers and a gaggle of controllers), has caused my save to corrupt. So I'm back to square one.

On that note I never had this problem back in 2.1.1, something might have gotten buggered when you finalized the 2.2 update.

Edited by: Random_Zombie#1

Reply to thread
click to sign in and post

Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.