-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Map showing the display for the incorrect floor #143
Comments
Does the crash happen again when you replay the seed? Do you have any other mods enabled? |
can you also send the crash log from when that issue occured? you can find those here: |
isaacv1.7.9b.J835-20231205-140331-18360-30404.txt |
The Log file you provided tells us the reason it crashed at the very end of the file. in your case: Those errors come from the "stats-plus" mod, and not from minimap api. I could not find any other errors in the file, so i guess that mod caused the issues you are expiriencing |
That's fine that Stats Plus caused the crash, but the map still won't display the correct floor after the crash has been resolved. I have just experienced another crash, presumably due to an unrelated mod, and the map again displays the previous floor. If there's nothing you can do, then fine, but I figured that this is something that counts as a bug with MiniMapAPI and not as a bug with something else or an interaction between mods. |
Does minimap api work correctly for you in a new run, in which no crash occured? |
Yes |
Playing as the Lost on seed TPP3 3DDA. Entering a curse room on Mausoleum II (with voodoo head, so there are two of them) caused the game to crash. Upon restarting, the floor was restarted as if I were visitng it for the first time (which is normal as far as I know) but the minimap is displaying a fully cleared Mausoleum I map instead of the map for Mausoleum II. Disabling the mod, restarting the game, entering the run made the default minimap display the correct floor, but after reenabling the mod, restarting, and going back into the run, the bug persists.
The text was updated successfully, but these errors were encountered: