Advertisement
FlamingYeti

Gingerfork Server Downtime 15/08/2018

Aug 18th, 2018
70
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.77 KB | None | 0 0
  1. Hello everyone. The Minecraft Server is officially going to be down until Monday (right now it's been... unofficially down? It's really just been me giving incorrect time estimates), so for the people concerned about where the server is, here's a breakdown of everything that's happened as I kind of owe it to you. Enjoy.
  2.  
  3. Basically, the Trade-O-Mat is a fucked up block that breaks the server. Never, EVER place one, heaven forbid. Specifically, it's to do with the contents. Acceleron stated that it was only when he put something in it the server crashed, and I believe it to be some kind of compatibility issue between mods. This meant whenever the chunk with the Trade-O-Mat was loaded, poked, or prodded, the server crashed. We tried a bunch of ways to destroy it, and in the end it was regenerating the chunk with WorldEdit that worked. Day is saved, everyone goes home happy.
  4.  
  5. The next issue was more... permanent. One of the ways to destroy the Trade-O-Mat that we tried was destroying everything in a six-block radius around Acceleron, as when he joined the server he'd load the chunk the Trade-O-Mat was in and it would crash the server. This solution didn't work, but hinged on a single command block in the Nether that ran a command to destroy the stuff around him.
  6.  
  7. Following that, I tried to edge as close as possible to the Trade-O-Mat without loading the chunk in an attempt to... I don't even fucking know, load the world around it but not that chunk? /fill needs the world to be loaded wherever your filling, and so I was trying to get close enough to run the command. Because of this, I unloaded the chunk with the command block that deleted stuff around Acceleron, meaning it wouldn't run until someone went near it.
  8.  
  9. This means that after the issue had been resolved, and Poepsie went into the Nether, it loaded the chunk with the command block that destroyed stuff around Acceleron again. He was doing stuff at his base, and as soon the command block triggered it tore a massive hole in his house, threw him into the void, and then started to delete blocks around him at spawn when he respawned. Acceleron disconnected, I found and destroyed the command block, and took the server down for three days to try and repair it the best I can.
  10.  
  11. The oldest backup of the world I have is from 29 days ago. I've used that to fill in holes that I can, but some stuff has been lost because it simply didn't exist then. For those areas, I just regenerated the terrain. I'm currently on holiday in Wales with shitty hotel internet. The world file is 3GB (well done Past Harry and Past Luke for generating so much bloody terrain) and I've been uploading it to our server host for 38 hours with a 500KB/s upload speed. Last night it finished uploading, and it seems something hasn't worked, my guess being it simply didn't upload correctly. Whenever I put the server up it spits out a bunch of errors claiming that a million different kinds of block don't exist, and the one time I did actually join, most of the world was gone.
  12.  
  13. But not all hope is lost! We're actually nearly there. If I join the world in singleplayer then it works a treat and everything is fine. It's only when I join the server that it's all shitty and weird. So on Monday, when I'm home, I'm going to reupload the world file and fix this fucking mess. Or that's the hope at least, you should've all learned by now not to trust my time estimates.
  14.  
  15. Regardless, that's where we're at. I want to make it 100% clear that this is 100% my own dumb fault and I should've been less careless when trying to solve the problem, and because of it we've had Acceleron lose a lot of his stuff and massive server downtime. If you have any insulting words or phrases to throw at me, go ahead, you deserve it, and can do so via Discord, Twitter, or Gravatar. Thank you and sorry again <3
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement