I get this all the time now at the origin chunk, or the chunk the starts at 0X/0Z coordinates. It was in 1.4.6 and 1.4.7, if I fly away and back, it gets filled in, so its a server sync issue. Relogging does fix it, so this is a different bug than the one I reported, but my bug got merged into this as a duplicate, so here I am.
I had to use mcedit to move all of my worlds far away from 0,0 to avoid this issue. I suppose normal servers arent as affected by this as creative servers like ours where everyone has flymods. To cope with this I used mcedit to edit all of our worlds to have them start at 1000,1000.
I hope this gets fixed by 1.5.
MC-9969
I get this all the time now at the origin chunk, or the chunk the starts at 0X/0Z coordinates. It was in 1.4.6 and 1.4.7, if I fly away and back, it gets filled in, so its a server sync issue. Relogging does fix it, so this is a different bug than the one I reported, but my bug got merged into this as a duplicate, so here I am.
I had to use mcedit to move all of my worlds far away from 0,0 to avoid this issue. I suppose normal servers arent as affected by this as creative servers like ours where everyone has flymods. To cope with this I used mcedit to edit all of our worlds to have them start at 1000,1000.
I hope this gets fixed by 1.5.
This is really becoming a big problem on my server where I let users use the /item command.