Autoclicking walls is now illegal and will be for the remainder of this map. That being said, from here on out players will be banned for autoclicking or fastplacing their walls when the server is un-whitelisted again.
I just thought I'd make an announcement and let ya'll know.
Cheers, happy raiding.
The drop zones recode and revamp has been completed, and will be implemented again. All drop zones will now take part inside a castle with four exits; north, south, east, and west. All four exits will be blocked off with fences and unavailable for access unless a drop zone is taking part. You will be notified 5 minutes prior to a drop to get ready for it. Just like before, you'll be able to type /dropzone join 15 seconds before the drop to join in. Upon joining the drop, you will be teleported inside the castle to a spawn point of your own where you will be unable to move or fight until the drop occurs. When the drop occurs, 9 chests will fall from the sky into the center of the castle. Only one of these chests will contain loot. When a player finds the chests containing the loot and takes it, it will be announced in chat. 15 minutes after the drop, the fences will automatically be put back in the north, south, east, and west exits. Your EXP bar...
Unfortunately, we were unsuccessful in recovering the corrupted data.
Does this mean there will be another reset? With embarrassment and too much shame to hold my head up to speak to the community after the recent calamities, yes.
I realize the past week has been a disastrous experience to any player who even attempted to give this bug filled server a try. Many are wondering as to how and why these issues occurred. Well, I'll give you guys the full story. However, I won't mention any names as I'd hate to put them in the spotlight of all the issues.
Why was 6.0 such a mess and the worst possible reset?
6.0 was planned exactly one month before the release date. Everything was ready and tested for countless days to ensure the launch of 6.0 would have zero issues. On top of that, new graphics were even made to make the server look more appealing. Exactly 1 hour and and 2 minutes before the launch of 6.0, a member in our administration team made some slight changes to...
Just got out from class, and on my way home. The server's SSD is currently having issues as a majority of our data was corrupted. While we do take daily backups, the last one stored onto one of our administrator's desktops is currently 4 days old. We'll keep you guys updated about the status. Whether it involves a rollback, or a new map, or everything being perfectly fine, the server will be back up no later than Saturday, 8 AM PST.
The server has been undergoing some issues as of the reset that are currently being worked on. We are experiencing a memory leak caused by what seems to be Essentials.
A fix is currently being worked on and we thank you for your patience. We're working as fast as we currently can and will have the server up and running ASAP. We will consider a form of compensation and will announce anything of this sort as a later date.
We will not be using any custom biome generator this map, and as such will be using vanilla 1.7 biomes with a modified bedrock layer. Bedrock will no longer spawn above Y:0, meaning that there will be a flat layer of bedrock for players to build on in the overworld. The Overworld and Nether borders will not be changing from 5.0, and will remain the same. However, building in the Nether will now be disabled. The End borders have been expanded due to popular demand. Borders:
World: 20,000 x 20,000 (10,000 -> -10,000)
Nether: 4,000 x 4,000 (2,000 -> -2,000)
End: 10,000 x 10,000 (5,000 -> -5,000)
You will now be able to claim only along the borders of the map. However, 20 chunks from corners of the borders will still be unavailable for claiming.
At approximately 4PM (PST) / 7PM (EST), an Enderdragon will be spawned in the area above spawn and will be carrying Operation Documents with various tasks on written on...
UPDATE - CraigEge: Mem leak patches should be applied on server reload
UPDATE: We are aware of the new crashing issues. I've gone ahead and notified Craig as I currently don't have access to a computer.
The past four to five days, we've been having extreme lag issues. After nearly 38 hours of constant monitoring, examining, and profiling the server, I believe we're safe to say the lag issues have been fixed. I apologize for any inconvenience this may have caused.
Well, I'm off to bed now. Need to catch a flight at three in the morning to get my treatment. When I get back, the "big" project will be launched.
Until then, sit tight.
Also, happy birthday @Nightl_lWolf! Hope you have an awesome one!