Digit1704
Assigned
Reported
Comments
And it is resolved in 20w07a!
@Oval Not a duplicate of MC-170951. Probably related! This is not teleporting below 0, it is teleporting above 255! In the future, please read the bug before leaving a comment!
@Rellik PanDragon guessing is nice, but in this case not right. So far itemframes and clocks. I tried more stuff that hangs to the wall, torches (and the like), but they are good. So, for now I just have seen it with itemframes and clocks.
In 1.14.2 Pre-Release 3 still a problem. (Why did I bother telling you guys there are real problems in the snapshots and getting told to basically shut up, because it will be alright!)
I just came online in the new snapshot, lights I had replaced to get it working, only to find now that again some of the lightsources just don't work.
Confirmed in 1.14-pre1
@Meri Diana just a little note, it is not 'a good chuck of time' for them to just come over here (they have to anyhow to see what it is now assigned to them) and just add a little note about how or what. I am a developer myself, for a big company, and I also have to do some updates now and then. If we don't do that, then management is explaning that as a lack of interest in 'the customer' who would like an update now and then... So, for me it is a vital part of development to keep them a little bit in the loop before they tell me to stop with what I am doing... So on that part I just cann't really agree with you. If I don't see comments from them, then they are not there! And you or any other Mod can say everything they want, but you are not Mojang. And yes, sometimes I tell the customer just that we really did not get any further with the problem, but at least then they know.
I do thank the Moderators for keeping this issue-list and the comments in it nice and tidy. But for this really heavy case? There might be some mussle to help out.
So, @Mojang, @MojangDevs, @Nathan Adams, give us a little straw to pull us up on. Let us know what is happening. This bug is in here from almost the first 1.14 snapshot. Lets see something, pretty pleasy?
And thanks for Minecraft, I just really like it!
@Michael Wobst we know that it does not help (obviously). The thing is we are realy scared when 1.14 is released there might be major bugs in there. I am on a few Snapshot servers and hardly anybody is playing. And when they are, they are more just waiting for the world to come up or trying not to get shot or blown up. It should be highly alarming that there seems to be nothing going on with this. No mention anywhere from the developers. Would be nice to here that this one (and the lighting bug) are really on Mojangs Top Priority list and they are doing whatever they can to get it fixed asap! We need time to test the snapshots to get bugs out but like this? So, I know this post will probably also be deleted, but hopefully that one of the major Mojang programmers could give us a bit of info on this?
Thanks!!!
Confirmed in 19w14a
The problem with this bug is that if you are anywhere in some hill-country you basically can't do normal gameplay anymore. This is a snapshot, specific to let us test stuff. Well, this makes it really, really hard to test stuff. Same with the lag-problem. If you can hardly play, then there is no use for a snapshot. Breaking the world? No problem! Just start a new one and go play. But not being able to play in a bit normal way is very anoying.
Most bugs you can play around or just don't use it. But this is basic gameplay that is very broken, so yeah, it is a big deal...
And when going down on stairs you sometimes are hovering above the block. It seems that the block-hitbox is off somewhere....
And this makes it very unplayable. I hope this will get fixed and not left like the enormous lag-problem that the snapshots currently have (that makes it also almost unplayable).
It seems to be that loading a chunk takes so much of the processor. When being alone with a good computer it is workable. But (depending on computer cpu strength) when more people are joining it get slower. At one server I am on you can just play with 2 persons, but not both running around and loading lot of chunks. On another server it takes a few more persons. And these are servers that previously could hanlde much more activity without any problems. The one where 2 are getting in trouble now, would regularly have minimum 10 online when I was playing and there was no problem with lagging whatsover. So it is very, very heavy on CPU with the new snapshots (every snapshot for 1.14).
And @Thomas Hine, yes we can and do play also on other servers. But I also like to play on snapshot-servers, but it is not really playable, so what is then the use of releasing a new snapshot if we cannot test it to see if it works? This is just one big major issue with the snapshots! It seems to me that although it is 'nice' to have new features and although stuff might not be working (I have waited for weeks to get my greens back in a previous snapshot) and that is allright. It is a snapshot. But not being able to play normal is really hard to explain. Maybe it would be good that Mojang would have a comment on this, that they are indeed having there full resources on this. It now looks that this is not considered a major issue somehow.
So @Mojang: THIS IS A MAJOR ISSUE! pfff... hope they see this red flag 😉
We solved the server-crashing problem by putting a commandblock down that repeated put a block at the hopper-location and then walking toward the chunk to get it loaded.
When placing a hopper again at that same spot (with the commandblock off...) the server crashed again. Something is wrong at that spot, somehow. I deleted the whole thing (was an auto-smelter, this was the item-input hopper) and never do anything there anymore. Don't know what the exact problem was.
We still have the problems that chest become invisible/empty and other things disappearing, item-frames falling to the ground, etc etc
Chunk-loading still is not what it should be (if they load at all).
The first problems I saw at that area was when we traveled from the nether to the normal world, and then some frames would fall off, as if the 'loading sequence' was not in the right order or something like that. We also lost items in chests, villagers, somebody had a dog with him that was also gone. This then also started to happen when logging on in that area, but after a little while that this was going on the server started to crash all of a sudden. That happend a few times and now when you get to the affected area (loading the chunk seems to be the problem) the server just crashes instantly.
We still cannot logon to the server without crashing it. At this server, the problem is that it crashes because of hoppers. I found with another logon that if you come near the place where the hoppers are, the server starts crashing. If you are far away enough it doesn't do that... When I got near and the server started to crash I had just enough time to walk away with that user, but it took me a couple of restarts. Please check what the problem is, I cannot play anymore (I am in the middle of the hoppers, so can't move)!!! Mojang, please Help!!!
Ow, the 18w46a does not resolve the issue!
We still cannot logon to the server without crashing it. At the server I am on, the problem is that it crashes because of hoppers (it is the duplicate? call MC-139200). I found with another logon that if you come near the place where the hoppers are, the server starts crashing. If you are far away enough it doesn't do that... When I got near and the server started to crash I had just enough time to walk away with that user, but it took me a couple of restarts. Please check what the problem is, I cannot play anymore (I am in the middle of the hoppers, so can't move)!!! Mojang, please Help!!!
Ow, the 18w46a does not resolve the issue!
Any idea when this might be handled? I really want green in my game!
Not a bug. 'execute as @a run' does not run AT the @a-player. You should use 'execute as @a at @s run' to get this working correctly