Strategia
Well-Known Member
As some of you might have already found out, the server has begun lagging more and more over the past week or so. Now, long story short, this was due to the fact that no-one refuelled the communal nuclear reactor. It didn't go WGGRRRHHMMM, rather the opposite; the uranium cells ran dry. Now this isn't terrible in and of itself, it just means the reactor stopped producing power. The problem is that the cooling system just kept going. A whole bank of block breakers had stored one and a half metric fucktons (that's one point twenty-three imperial fucktons) of snowballs each, which were supposed to be piped to a bank of compressors, which turned them into ice, which was being piped into the reactor for cooling purposes. Only the reactor was full to bursting with ice, and so were the compressors. The end result: laglaglaglaglag because of all the snowball entities.
Snook, Wild and myself just spent about half an hour trying to fix this. Every block breaker we broke unleashed a huge avalanche of lagballs, which only really stopped when we lit the ground underneath on fire. Even then it took a long while for the remaining snowballs to finish processing they were being burned. The block breakers have now been replaced, and the reactor is running again, so OPERATION: SNOWFUCK has been a success
The lesson you should draw from this is the following: never, ever leave complex machinery like that running on its own, and ALWAYS make sure the nuclear reactor is not just being cooled, but also fuelled.
There may or may not be repercussions for stuff like this in the future. Causing the entire server to lag up with your machinery while you're present and overseeing it, okay; but making it automated, thus causing the server to lag up all the time so long as the chunk is in memory, is definitely not cool. So make sure to keep an eye on your automated systems so they don't choke up somewhere like this did.
Snook, Wild and myself just spent about half an hour trying to fix this. Every block breaker we broke unleashed a huge avalanche of lagballs, which only really stopped when we lit the ground underneath on fire. Even then it took a long while for the remaining snowballs to finish processing they were being burned. The block breakers have now been replaced, and the reactor is running again, so OPERATION: SNOWFUCK has been a success
The lesson you should draw from this is the following: never, ever leave complex machinery like that running on its own, and ALWAYS make sure the nuclear reactor is not just being cooled, but also fuelled.
There may or may not be repercussions for stuff like this in the future. Causing the entire server to lag up with your machinery while you're present and overseeing it, okay; but making it automated, thus causing the server to lag up all the time so long as the chunk is in memory, is definitely not cool. So make sure to keep an eye on your automated systems so they don't choke up somewhere like this did.
