This resulted in me getting to about the same spot in the last hundred by late evening. I jumped back in the queue mid-morning, but the damage was already done and there was no spot boost due to the server restart having passed a while ago. I woke up to find that my spot in the queue was non-existant, due to. Third try, got up early morning, set up my position in the queue, went back to sleep. Kicked out of the queue at #85, I was sure I could do it if everything lined up just right. This boost got me down to about #85 by late evening, but since I had calculated at least another hour or two of wait time, I was not prepared when another server restart happened due to me being away. This was my first encounter with the server restart, though it didn't directly affect me as of yet. As a result, instead of starting at #1,300, I was already #900. Coincidentally, though I didn't realize it at the time, I had joined the queue directly after a restart, during the slow upward climb of the player count. My second try was more calculated, starting in late morning, in preparation for a long wait.
I tried again, but being pretty uneducated on the methods and manners of 2b2t queues, I didn't get very far before my self-appointed bedtime got in the way (not to be confused with a much earlier "normal" bedtime that I probably should have used), only about #350 or so. Two hours later, I accidentally clicked the disconnect button. On my first try, I started in late afternoon, not knowing what I was in for. The queue is very unforgiving during those times. When the wait time is 10 hours or more, it's very hard to enter the queue at exactly the right time so a server restart doesn't get in the way. They turned out to have a sort of predictable pattern, but not enough to go by. Unfortunately there were more problems.Īccording to this nifty site I found, 2b2t.io (yay it has a bunch of graphs), the server restarts every 12 hours or so at seemingly random intervals. Wait times are no match for my ridiculous attention span. My scatter plot data, when graphed, kept predicting a shallower curve as time went on, which was expected, but the horizontal asymptote was being very discouraging. According to real life (so much more accurate) the queue turned out to be at least 10 hours long, ranging from 1,000 to 1,300 players normally. After all it would only be a few hours.Īccording to sources that were somewhat outdated, the queue was not that long, only a couple hours and 600 players. This way I could estimate how long it would take and better prepare. In order to gain information about what lies ahead, I would predict it using the statistical data gained by sitting in the queue. And better yet, we'll have some fun along the way. I have been gifted with the most insane attention span known to man.
I quickly realized that the hard part was not actually playing on the server, but getting past the ridiculous crash-prone queue that guards the entrance to the Minecraft equivelant of Mordor. Granted it's apparently the worst place on earth (Minecraft-wise), but I was surprised I hadn't given it a shot yet. A few days ago I was thinking about how I could never find a good Minecraft server to play on when my thoughts jumped to 2b2t.
0 kommentar(er)
