Open Beldantazar opened 9 months ago
Just to confirm I've seen this. Been reported often. Never was able to repro this. I would love a save file + apworld zip + user when this happens. If quitting and reloading doesnt fix it, that save file I could use to add a fix.
This happened to me just recently. Daivuk, lemme know exactly what files you want to examine and I can send them over.
Just to confirm I've seen this. Been reported often. Never was able to repro this. I would love a save file + apworld zip + user when this happens. If quitting and reloading doesnt fix it, that save file I could use to add a fix.
Here, instance that just happened to me -- contains apstate.json
and all DSG files for the run up to that point, user is "Wryyyong": AP_W70925506325953290800_57727979796F6E67.zip
A small workaround as well, until this is fixed:
AP_W70925506325953290800_57727979796F6E67
)apstate.json
in your text editor of choice.player.health
to any value between 1
and 200
, and save the file.At this state, the player should now not be in a bugged death state (can lose health, can interact with objects and demons, etc.), but your weapons will still be bugged for the current level. To fix this, just open the pause menu and select 'Kill' (or just die again) to properly reset the level and player state, and the issue should be resolved.
Background
Version of Crispy Doom: Archipelago 1.0.3
Operating System and version: Windows 11
Game: (Doom/Heretic/Hexen/Strife/other) Doom 1993
Any loaded WADs and mods (please include full command line):
Bug description
Observed behavior: When I died as part of a multiworld game (reset level on death was enabled) it did not reset the level on death at all and I just stayed dead. I was unable to trigger a respawn and had to release all items to allow the other players to proceed.
Expected behavior: For the game to reset the level as described on the options.