Here is also a video explaining the problem that also contains a fix for this bug: http://youtu.be/LIDNyB-Ys8w
What happens:
When you load another section of a chunk, e.g. by placing blocks in that section, then you remove everything out of that section and it stays loaded and the server still uses these empty sections for calculations like mobspawning. This does not change if you reload the world!
What should happen:
When a section is completely empty it shouldn't get used for any calculations, since they don't give any result anyway and are therefore totally unnessecary.
How to fix:
There is a method in the Chunk class (abw.class) which checks for the topmost filled section in a chunk (int h()). Don't just check that the section is not null, but also that it is not empty.
I did not find any post that describes this bug appropriately/suggests a proper solution, which is probably why this is not fixed yet!
Related issues
Comments
The post you linked is first of all wrong and it also suggests a totally different solution, which does not make any sense, which is probably why this bug is not fixed yet!
Can I re-open this issue somehow? or do I need to create a new one, because this is definately NOT duplicate!
This ticket:
...then you remove everything out of that section and it stays loaded and the server still uses these empty sections for calculations like mobspawning.
LC parameter is not recalculated when you remove a block It only recalculates on restart of the world
That sounds totally the same to me.
"LC parameter is not recalculated" and "still uses these empty sections for calculations" is NOT the same! That is exactly the difference. MC-7473 suggests to recalculate this every time a block gets removed, which is not a good idea to do since that could cause lag issues. Also it says that it would get recalculated if you reload the world. That is wrong! And this is exactly the reason why I posted this problem. The bug I describe here did not occur in earlier versions. You just cannot see that in the client, because the server does not send empty chunks to the client. It is still a very important problem!
bugi74
Code Raider: while the MC-7508 might not be the same bug, it is still quite fine to link with "related to" when/if both issues touch same method(s), or even just same classes in some cases. The idea is that if there is some bugfixing activity for either issue, and thus the files are already open, it would be a little bit faster to check the other issue at the same time.
In some cases it is almost a necessity to relate to different bugs/issues when their fixes may overlap each other, thus requiring both to be fixed simultaneously, or otherwise the other one will get a lot more difficult to fix, or at least a proposed fix becomes unusable. (I have provided at least one case of such fixes.)
Unfortunately, it would seem that Mojang isn't quite as aware of the benefit of fixing related bugs at once. But it doesn't hurt to try to help, anyway.
This is not the case for this problem here though.
'Duplicate of MC-XXXX, please use the search function to see if your bug has already been submitted. Currently over 50% of tickets are being closed as duplicate.'
I've seen this countless times, sorry for being rude but if 50% of tickets are duplicates that IS A GOOD THING !, bugs are getting fixed. And also, I have 3 bugs to report I don't do it because I don't have the time to do it properly explained, leave alone searching for duplicates, and also if I've come here it was to report a bug not to search for it. Mojang pays people ! Mojangers searching for duplicates is part of the job, welcome to bug reporting.
I'm a computer programmer and I face this exact same issue, but I react different to it, 50% duplicates means, at the very least, 100% more info than just one report per issue.
Stop saying that stupid statement, and start saying: 'Marked as related to MC-XXXX and THANK YOU for you report.' that is the proper way to do it.
I've been wanting to say this for so long... and I could have used the time to report a bug.
Duplicate of MC-7473, please use the search function to see if your bug has already been submitted. Currently over 54% of tickets are being closed as duplicate.