Chunkreset makes exit switches inoperable

Is there a good vanilla use case where this becomes a gameplay problem?

6 minutes ago, TSBX said:

Is there a good vanilla use case where this becomes a gameplay problem?

I am not sure how common this use case would be, but I was thinking perhaps if someone was having map issues like floating/missing blocks they may try to troubleshoot using chunkreset to reset a region. And then later if they have a quest in that area and decide to double loot it (i.e. loot once, then start quest and loot again), they will have a hard time exiting the area on their first runthrough.

 

Or possibly in a very active MP server an admin may want to reset all the loot in a certain area or city without necessarily making everyone start a new game from scratch. Anyone who tries to loot the POIs later without activating a quest may have a hard time getting out.

Correction, for MP server, I mean reset all the POIs in a certain area or city. Since I know there's a lootrespawn setting that can reset the loot, but it won't reset any missing blocks, player placed blocks/nerdpoles, or loot that gets "destroyed" once you open them like ammo piles.

I'll look into this further. For the time being, using test_POIReset under the Twitch Game Events Menu (Shift+F6) does seem to reset the switches properly, at least in SP.

2 hours ago, TSBX said:

I'll look into this further. For the time being, using test_POIReset under the Twitch Game Events Menu (Shift+F6) does seem to reset the switches properly, at least in SP.

EDIT: Switches NOT triggered by generators are unaffected (Key racks included).

Your mileage may vary, the test_POIReset command doesn't appear to be working in my second round of testing.

Edited February 18, 2022 by TSBX (see edit history)

This has been confirmed and reported, thank you!