The Meaning of Life, the Universe, and Everything.
Join Date:
9/7/2014
Posts:
41
Member Details
Seriously. The Pre-release is just as laggy as the previous snapshots if not worse, and I don't want Mojang's full release to have the same. So hold back on releasing 1.13 if you must, but make sure you get that lag taken care of.
Or any of the changes (eg. pistons & slime blocks becoming non-transparent) being slipped in – unannounced – at the eleventh hour...
Fix the bugs (at least the game killers)...
Fix the lag (the purely cosmetic start-up screen is apparently horribly laggy)...
Remove any last minute block behavior changes that have not been subgectected to a proper regime of snapshot testing...
[Block transparency changes may mean little or nothing to creative players, but will kill large numbers of technical survival builds.
Just like 'fixing' the 'bug' where one-tick pulses resulted in sticky-pistons "droppped" the attached block, the most charatable interpretation of teh change is cluelessness on the part of the devs.
Unless the goal is to alienate thechnical players and further fragment the company market demographic, this sort of change needs to be tested and the feedback from players heard before it is baked into a release.]
If [and ONLY if] the above have been done is a prelease appropriate: far better that it ship late than with fatally flaws
Rollback Post to RevisionRollBack
"Why does everything have to be so stoopid?" Harvey Pekar (from American Splendor)
WARNING: I have an extemely "grindy" playstyle; YMMV — if this doesn't seem fun to you, mine what you can from it & bin the rest.
@ScotsMiser, yes please. The Protection Bug I mentioned earlier appears to be fixed.
https://bugs.mojang.com/browse/MC-129136 "Game crash: ticking world" appears to be a problem. However annoyed you may be at certain aspects with 1.13, please consider using this release to play a FULL game with the intent of finding bugs. MC-129136 appears to be 'random'. We really need eyeballs on it to see if we can make it 'not random' by figuring out what triggers the crash and pointing the Devs to it. There may be other bugs yet-to-be discovered. Voting on bugs important to YOU is also important to highlight to Mojang the issues that have community attention. If nobody knows, then nobody can care. And quite frankly, the Devs are *NOT* going to read *THIS* message thread, but they *DO* pay attention to WELL WRITTEN, thoughtful bug reports. Please be a part of the solution and get involved.
Seriously. The Pre-release is just as laggy as the previous snapshots if not worse, and I don't want Mojang's full release to have the same. So hold back on releasing 1.13 if you must, but make sure you get that lag taken care of.
Agreed! I would much rather play survival without all that lag
Or the bug that turns all enchants, books, librarians, bows, into Protection. Heh... Try hunting with a Protection V bow!
Or any of the changes (eg. pistons & slime blocks becoming non-transparent) being slipped in – unannounced – at the eleventh hour...
Fix the bugs (at least the game killers)...
Fix the lag (the purely cosmetic start-up screen is apparently horribly laggy)...
Remove any last minute block behavior changes that have not been subgectected to a proper regime of snapshot testing...
If [and ONLY if] the above have been done is a prelease appropriate: far better that it ship late than with fatally flaws
@ScotsMiser, yes please. The Protection Bug I mentioned earlier appears to be fixed.
https://bugs.mojang.com/browse/MC-129136 "Game crash: ticking world" appears to be a problem. However annoyed you may be at certain aspects with 1.13, please consider using this release to play a FULL game with the intent of finding bugs. MC-129136 appears to be 'random'. We really need eyeballs on it to see if we can make it 'not random' by figuring out what triggers the crash and pointing the Devs to it. There may be other bugs yet-to-be discovered. Voting on bugs important to YOU is also important to highlight to Mojang the issues that have community attention. If nobody knows, then nobody can care. And quite frankly, the Devs are *NOT* going to read *THIS* message thread, but they *DO* pay attention to WELL WRITTEN, thoughtful bug reports. Please be a part of the solution and get involved.