-
Bug
-
Resolution: Awaiting Response
-
None
-
1.20.4, 24w05b
-
None
-
Unconfirmed
-
(Unassigned)
While Every Other Type of update Populates a crash report with information on the source of the block that caused the crash, shape updates do not do so, meaning there is no information on were the exception occurred.
You can reproduce this by setting maxChainNeigbourUpdates to -1 and causing an ArrayOutOfBounds with signs or similar means.
Steps to reproduce:
0. set you server config to have maxChainedNeigbourUpdates = -1; (this allows you to reach integer max limit and create an error)
1. place integer max limit amount of budpowered rails
2. at the end remove a couple of rails and place floating signs
3. update the rails from the beginning
What will happend:
A crash report will be created with out the block off information that would usually come with it with header "Exception while updating neighbor's" if the update weren't a shape update, no information of the place were the exception occurred is present.
What you expect to happen:
A crash report will be created with the block off information that would usually come with it with header "Exception while updating neighbor's" mimicking the behavior of normal updates and leaving a information trace as were the place were the exception ocurred is present