haloman30

Hey, everyone - there was something that happened recently that I'd like to address. Recently, there was a bit of debate in regards to a particular detail of one of our spawns - if you were in voice at the time, you likely know what I'm talking about (and if you weren't - don't ask for details). I was requested, very politely, to remove this detail - as it was inconsequential to the build (it was more of an easter egg than anything), and held some personal significance to this person. For most of you, the right thing to do will seem obvious - remove the detail. With this particular situation, though, I had a great deal of difficulty making this decision - not because I didn't understand the issue, but because this came at odds with something I feel very strongly about - archival and preservation. In the end, the detail in question was removed - but some folks were (and likely still are) concerned that this was a decision with any difficulty in the first place. After all - the right thing to do should've been obvious, right? Yes. It was - and I will not, and do not disagree with this. However - I do want to explain the perspective I had at the time, to hopefully shed some light on my own personal thought process. I don't ask that you agree, or even entirely understand - but I think it's important for me to get it out there before continuing. The last thing I want to do is come off as rude or uncaring - I care deeply about doing the right thing. I want to do right by the community, and those who are part of it. However, at the same time, I believe strongly in preserving and ensuring that nothing is lost - both the good and the bad. And I can recognize that for many of you, this likely seems ridiculous - and while I'll argue and defend my position on archival in general, I concede that - in this type of situation - I was in the wrong. This detail should have been removed - and it ultimately was. However, this shouldn't have been difficult - the fear and concern that was felt by this person, believing that my desire to preserve would overrule a largely simple request - there's no reason for that, and no doubt that it's something that I can't undo. Even for those not directly involved, but present to witness it unfold - it's likely that I came off as disrespectful and uncaring. And for that, I do want to apologize - both to the person who requested this removal in the first place, and to those who had to be there and witness this when it happened. Going forward, if we run into a similar situation as before, I'll do my best to handle it better next time. That being said - I also know that I'm always going to have difficulty doing so - and as such, I can't promise that I'll be able to make that decision any quicker or easier. As such - I've been working with our build team to create a standardized set of guidelines - both to address these types of situations, as well as some of the other disagreements and misunderstandings we've had over time. It outlines general expectations for both current and future builders - with the goal of ensuring that what I expect, and my desire for archival isn't new information. It also makes sure that the types of things that are likely to end up being requested to be removed someday in the future are simply not included in the first place - in order to best ensure these issues simply can't happen again. These guidelines will be presented to all future builders, before they join our build team - to make sure there's no surprises going in. If someone simply isn't comfortable with some of the things we do - they should know that before spending their time applying, rather than going through the entire process and being caught off guard. Or, worse yet, creating builds and not learning of some of our unusual practices until after the fact. This is especially crucial with world downloads, which are still relatively uncommon across Minecraft servers. If someone built a spawn with the understanding that it'd never leave CU, and then found out later that their build was uploaded and anyone can copy and mess with it - that's not fair to them, and so that's something they should be fully aware of going in, along with all of the other peculiars. I understand that to some, this might still seem insufficient - after all, if I understand what's right, then why can't I just handle that when/if it comes up? Why prohibit these types of things, rather than just being willing to remove them if the time comes? My reasoning boils down to the fact that, while I recognize what's right and wrong in this type of situation, it doesn't make it any easier to actually do that right thing. Not that I won't do so - but even so, deliberately letting something go does give me real pain. I can't explain why or how, and I can't realistically change this fact - and so, for me, I find that the best thing to do is to simply ensure that such a situation never has an opportunity to present itself again - and to make sure that anyone coming onto the build team is well aware of what to expect going in. Should such a situation arise, I do still intend to honor those types of requests (within reason - I'm not gonna remove a significant portion of a build) - but I still believe that it's better to avoid having to make that decision in the first place. It was never my intention to come off as some heartless or inconsiderate ass - as stated before, it's simply a battle between two things I feel very strongly about. And, in situations like these, I need to try and get better and handling them. Archival is, and will always be deeply important to me - but I recognize that, once in a blue moon, there are situations where it can be justified to leave things behind - and that's something I'll need to learn to accept. It won't happen soon - and in the meantime, I believe the best thing to do is to do what I can to ensure that this type of thing just doesn't come up in the first place. I hope that you can understand my perspective, and at least somewhat see where I was coming from. And once more, to those affected - I give you my sincerest apologies for this. I may not be able to promise that I won't be difficult, but I can promise to try and do better.

Changed Status to Fixed

* Updated CUPackage to 1.3.4 * The Anvil in the Utilites section of Survival spawn will no longer break when used * Fixed an issue where Hopper Minecarts could not pull items from chests in SkyBlock * Fixed several Moderator permission issues - Removed Killerteddy

+ Added Open Iron Trapdoors to UtilityBlocks menu * Updated CUCraftingPlus to 1.3.20 * Placing custom blocks will now properly play the placement animation while placing * Tokens can now be earned via playtime (1 token per hour, with a daily limit of 5) * Fixed an issue where the Comparator technical utility blocks would place as repeaters instead of comparators - Removed Killerteddy

Changed Status to Fixed

Hey, everyone! We've got an exciting announcement to share - as of now, we are finally re-introducing the Chaotic United Wiki! The Wiki has been an idea we've had going all the way back to 2014, and have re-introduced a few times over the years. As of now, though - it's been built directly into the website, and unlike previous iterations, it's actually got some useful information on it! As of now, you'll primarily find information about our custom Survival content - past, present, and planned for the future. Down the line, we intend to document the various communities associated with CU - such as Nuclear District, Hurricane Craft, United AlyCraft, and even some more obscure ones that were all but forgotten. We also plan to add pages detailing some of the notable users and staff members that CU has had over the years, as well as details on most of our custom plugins. For now, though - that's all we've got. Just keeping it short and sweet today. To check out the wiki, head to https://chaoticunited.net/wiki!

+ Launched the Chaotic United Wiki - Removed Killerteddy

This update includes changes from earlier on in the week. * Updated BoatRace to 1.1.4 * Updated GibCraft to 1.1.1 * Updated CUCraftingPlus to 1.3.19 * Fixed an issue with BoatRace and GibCraft where clicking the join signs would show a sign edit prompt * Fixed an issue where Durite Elytra would not be properly repaired when enchanted with Mending - Removed Killerteddy

+ Added /localwarps command - Can be used to show warps local to the current server + Added an additional checkpoint to Hardcore Temple to aid in navigation * Updated CUBungee to 1.6.4 * Player first join date/time is now displayed in /gseen * Marked several legacy warps as unlisted: benefactor2, chocolaterain, NDsurvival, penisbay - Removed Killerteddy

* Updated PGGrifblock to 1.0.5 * Updated CUMobArena to 1.0.3 * Fixed an issue where Grifblock and MobArena join signs would sometimes allow the sign to be edited - Removed Killerteddy

* Improved performance when loading homepage * News & Announcements topic thumbnails now have new URLs in order to allow for thumbnailing - Removed Killerteddy

This changelog includes changes from the previous several days. * Updated CUCraftingPlus to 1.3.18 * Fixed an issue where Observers would not detect Note Block state changes properly * Restored normal, non-April-fools hub - Removed some personal signs from Semi-Vanilla spawn - Removed Killerteddy

This is actually something we're already planning on implementing relatively soon - SkyBlock will end up with a standard economy, with the ability to buy or sell cobblestone for 1$ per block. The only reason we had the cobblestone economy stuff in the first place was due to a technical limitation we had earlier on, before we migrated to a BungeeCord setup. As of now, however, those limitations don't apply - and as such we're gonna be transitioning SkyBlock over pretty soon, once we get a new SkyBlock spawn completed in order to accomodate a larger shop, along with some other stuff we've got planned.

+ Added new hub which is clearly superior in every way imaginable * Platinum can now spawn in GUI_NUMBER_# (where # can be 0-9) items using /item * Updated CUChestShop to 1.0.1 * Fixed an issue where chestshops could be purchased from in Survival - Removed Killerteddy

+ Added /hookshotplayers command - Behaves identically to /cucp hookshotplayers + Added End Gateway to UtilityBlocks, under Technical Blocks category * Updated CUCraftingPlus to 1.3.17 * Fixed an issue where GriefPrevention claims in Survival would not claim any blocks below Y level 0 * Custom blocks which are non-interactive and Note Block based can now be pushed with pistons * Fixed an issue where blocks with rotation, direction, and/or orientation properties (Observers, Furnaces, stairs, slabs, etc) would not have the correct data when placed against a custom block * Fixed an issue where certain blocks could be improperly placed against custom blocks (many of these blocks will now simply refuse to be placed without sneaking) * Disabled note block update events in paper configuration in Survival (allows for some of the above issues to be resolved) - Removed Killerteddy