Tried to use invalid npc: GUARD5

[WindexEnjoyer]

Describe the bug

At certain intervals, the following error shows up seemingly affecting the refugee center:

Tried to use invalid npc: GUARD5. Callstack: EOC: EOC_REFUGEE_CENTER_NPC_MOVEMENT \ EOC: EOC_REFUGEE_CENTER_GUARD_FIRST_POSITION

Attach save file

Anton Chico-trimmed.tar.gz

Steps to reproduce

1. Have one guard NPC killed during Old Guard traitor quest
2. Proceed with Old Guard storyline until radio repeater mission
3. Save and Quit
4. Reload save and continue as normal
5. Encounter error at fixed intervals.

Expected behavior

No NPC issues during gameplay.

Screenshots

No response

Versions and configuration

• OS: Windows
  • OS Version: 10.0.19045.4651 (22H2)
• Game Version: 47cb4c4 [64-bit]
• Graphics Version: Tiles
• Game Language: System language []
• Mods loaded: [ Dark Days Ahead [dda], Disable NPC Needs [no_npc_food], Portal Storms Ignore NPCs [personal_portal_storms], Slowdown Fungal Growth [no_fungal_growth], Bionic Slots [cbm_slots], sees-player, run, crouch, bleed icons, retrodays [sees_player_retro], sees-player icon, HitButton_iso [sees_player_hitbutton] ]

Additional context

debug.log

[PatrikLundell]

Looks like the EOC tries to move the dead NPC to a new position twice every 24 hours, with an interval of 2 hours between the first and second move.

Presumably, the logic would need some kind of guard to not try to perform an action on non existent NPC when they run the risk of dying (which is probably all of them). This guard ought to be added to all EOCs affecting NPCs when the EOC has been tested to work normally without it (so misspelled NPC identifiers can be caught during testing).

[WindexEnjoyer]

I see. I tried fiddling around with the debug EOC's to try and trigger the FIRST_POSITION and SECOND_POSITION check and it seems to be hitting your description. What's a possible if temporary fix to this?

[PatrikLundell]

I don't know. I don't really know anything about EOCs.

Well, a local hack would be to remove the entries involving GUARD5 from the timed trigger. That would cause the game not to try to invoke those, and thus not result in the error message. That is extremely crude, and would only work if you don't update the game often (as it would have to be rehacked after each update).