Sending this issue for a friend of mine, this is the log they provided. This exact issue also happened to me yesterday after I reloaded a map with f5, however I can't share my log here as it contains a not public map I was playtesting. The image provided is from my log.txt, showing what the conflicts looked like for me.
Also in case it isn't clear from the log, this shows a postcard whenever you try to enter any map, preventing you from playing anything until you restart celeste
#Unable to enter any maps after a silver death
obtuse wagon
fresh gust
Sending this issue for a friend of mine, this is the log they provided. This exa...
restart everest
it's a crash that we know of but genuinely cannot reproduce and don't know the cause of
well, we do know the direct cause of, but we don't know the actual root cause of
safe laurel
we know what's going wrong but not why
obtuse wagon
restart everest
as in restart celeste? Or redownload the everest version
safe laurel
restart celeste
obtuse wagon
yeah im already aware that fixes it
this very much feels like one of those issues that's a pain to pinpoint the cause of
fresh gust
because it is
obtuse wagon
specfically cause it's similar to that one error thing on map reloads earlier
fresh gust
this is due to a mismatch between the executed pushfallback and popfallback calls
every single instance we have found on github matches them correctly
but yet it still happens
we've genuinely run out of options at this point
safe laurel
every single instance we have found on github matches them correctly
not even just github i decompiled my entire mods folder (on a setup where i could confirm that the bug happens) and still found nothing
safe laurel
fresh gust
oh i missed that then
obtuse wagon
my one guess is that this could be related to the newest everest stable solely because this only started happening a day after i downloaded the most recent version (the exact same goes for my friend who i sent the log of, we both downloaded the everest version for the same map)
safe laurel
it's been happening for months at least
obtuse wagon
the specific postcard version? just making sure
like kicking you out of the map and showing a postcard any time you attempt to enter any other ones
obtuse wagon
the exact conflicts?
safe laurel
the conflicts in the screenshot you sent are unrelated
fresh gust
System.IndexOutOfRangeException when the stack is not empty, and System.InvalidOperationException when the stack is too empty
obtuse wagon
the conflicts in the screenshot you sent are unrelated
good to know, just going off the fact it's the same ones reappearing for both log files
fresh gust
i do wish i could tell people to fix the conflicts...
clearly we need to implement a mapping license for a €20 fee
safe laurel
good to know, just going off the fact it's the same ones reappearing for both lo...
that's because you'll pretty much always see them even on successful loads
obtuse wagon
🔥
fresh gust
and a modding license for €50/mo
obtuse wagon
yeah the conflicts are unrelated just checked, nothing useful in the log too since one moment i reload the map just fine and then the next moment it isn't, the most i can do is if this issue reappears I can try downpatching to check if it was an issue in a really old everest version. One other thing my friend did say is that supposedly this issue would happen to specfically people with celestenet enabled, though I cannot fact check this at all so take it with a grain of salt
obtuse wagon
it wouldnt make sense to me for it to be cnet anyway since it hasn't been updated since 2024 and this is only an issue that's been happening recently
fresh gust
not so recently tbh
obtuse wagon
whats the earliest case of this?
fresh gust
phant encountered it when making the lobby for cvc
it had only one map
don't remember which
obtuse wagon
thats pretty far back yeah though still after the celestenet update at least
obtuse wagon
yet more proof
safe laurel
i've also seen it happen for people who did not have celestenet enabled
obtuse wagon
yeah I genuinely do wish I could help with this more but due to its random and infrequent nature ive got nothing, is there potentially a way to record a more detailed log since this seems to be slipping past the log.txt entirely