sativaphil
Assigned
Reported
Comments
It's unfortunate that they do not keep us updated on whats going on. I disagree this is not a high priority issue and I will leave it there. Thanks for the advice that this system is not worth using to watch tickets.
Absolutely by "we" I meant the team of devs. It would be great to see some activity on this major issue. It effectively renders the game unplayable if players explore - which im sure you understand and agree is a fundamental part of the minecraft experience that currently servers are struggling to deliver. It's somewhat disapointing to see a game breaking issue, that has a fix provided in the original report to still have NO progress made on it 😞
Doesnt look like it. Guys this is a serious issue that needs to be fixed. Can we assign this issue soon
Confirmed
I can confirm the above mentioned issues. And again can confirm this is not client related it is a serious issue with the game itself. Again another server where players CANNOT explore previosly un generated chunks as it causes major TPS and renders the server unplayable.
1.9.1 needed ASAP
Yes that appears to be the required fix 🙂 Thanks for your help all seems to be working correctly now.
Still an issue on pre-2 also. Out of curiosity, am I the only one with this issue and is it going to be fixed? Official release is 2 days off and with no response to this bug report other than updating each time I comment worries me that I might not be able to use 1.9.
Kind Regards
Still an issue one the pre release
Just noticed I had the texture packs enabled for when re creating issue for screenshot. The use of the faithful64 and failthfil1.9 is not the cause as I had first identified the issue and since posting the image link re-tested in pure vanilla 1.9 - no packs and the issue is present.
This is the game output along side the game window that is not responding. 3 grass blocks had been turned to the new dirt path and then it just stalls, never fully crashes and closes the game.
Sorry i missed out the detail this was using an iron shovel, so far the only one I have found to be affected.
MODS, My server is not a large server we have a community of around 30 players and an average online count of 6. At no point have I suggested I run a "large" server. I Never have more than 12 online at a single time and so if the official minecraft server software is not sufficient enough for that then we have far greater issues than chunk generation. This underlines even more so how important this issue is for the devs to be working on and not adding elytra sounds! The idea that I run some huge server is just wrong and being used as a reason as to why the game is not working correctly. The fact is your game is horrendously broken and the priorities of the devs seem to be WAY off the mark. Having tested the issue on the same hardware I used problem-free for 1.8. The issue is present with only 2 players online (this has been mentioned a couple of times by other members in other posts) which means the issue is NOT limited to large servers.
I do completely believe that we should be getting some actual feedback on this matter and not mods speculating as to what is going on. It seriously doesn't take much for someone who actually knows what's going on to say "Hi guys, I'm here, we're on it" however right now we are getting 1.9.1 Pre-releases with no fixes listed that match the report and no feedback on this ticket.
I understand this particular one is a heavy undertaking when compared to adding elytra sounds as it needs a total rework. It feels like its just being ignored in favour of an easier ride. You say mojang resolve things internally, while this may work well for them I suggest that those who report issues and aid in the game's continued improvement be given the courtesy of up to date feedback. This is my feedback on the matter for future issues as above I am no longer watching this one - getting totally fed up it. We try to help make this game better and its like everyone sticks their fingers in their ears because its to much work.