[1.16 2.0.7] forcing regeneration freezes game
C4PTRAMPAGE opened this issue ยท 7 comments
regenerating normally (waiting for it to happen works fine) forcing regeneration however freezes the game indefinitely
there is no log because it doesn't crash, it just freezes forever and you have to kill it with task manager when that happens and if you kill it with task manager the crash log only complains about you shutting down java.
this is a common enough problem that its very hard to believe you didn't know the game works that way.
Yeah and if it's on a server it gives you "Internal Error" instead. Although you can keep playing and the new skin does load.
this is a common enough problem that its very hard to believe you didn't know the game works that way.
There is no need for comments like this, it is just plain rude.
I have not encountered this problem, you must supply a crash report or a debug.log/latest.log after the issue occurs. You should know that Minecraft generates logs regardless by now. Even if it's just java shutdown logs, I still need it.
Yeah and if it's on a server it gives you "Internal Error" instead. Although you can keep playing and the new skin does load.
Thanks for letting me know :)
i just skimmed the logs so its possible i missed something but from what i can see its as i thought there's nothing useful about what caused the freeze, latest only has two lines after i forced a regen. and all the two say are you got an achievement and hey the games unresponsive
There is no need for comments like this, it is just plain rude.
it's no different than how i talk to my friends, family and coworkers and they don't get upset about it so i'm pretty sure i'm not the one whos in the wrong here... if your one of those types that gets offended by everything every two seconds it's not my problem.
Not offended, just not a statement needed when trying to diagnose a issue.
After confering with @MCraftBoatBloke, and reading their log and yours, the issue appears to be linked with your recent ones #350 & #352
If the issue persists after the new versions release, comment and I will re-open this