- Code: Select all
haven.render.RenderTree$SlotRemoved
at haven.render.RenderTree$TreeSlot.chstate(RenderTree.java:677)
at haven.render.RenderTree$TreeSlot.cstate(RenderTree.java:702)
at haven.res.ui.surv.LandSurvey.tick(surv.cjava:210)
at haven.Widget.tick(Widget.java:744)
at haven.GameUI.tick(GameUI.java:1458)
at haven.Widget.tick(Widget.java:744)
at haven.UI.tick(UI.java:236)
at haven.GLPanel$Loop.run(GLPanel.java:380)
at haven.JOGLPanel.run(JOGLPanel.java:246)
at java.base/java.lang.Thread.run(Thread.java:834)
Okay to be very fair here, this is not the vanilla client.
Still tho, I'm super sure, there's nothing wrong with the involved code in a sense that it is the same as vanilla.
These errors are super hard to replicate, because I'm kinda certain, that this is because the tick happens right after something got removed from the render slot.
The question I have is, why have it programmed that way? Why does the client has to crap it's pants when it encounters a Removed slot on a tick instead of cancelling the tick and live on?
It feels like giving my son the task to take out the trash, but since my wife already did that, my son get's a mental breakdown because there is no trash anymore to take out.
