Become a premium member to remove ads


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Time Online

    24855d 3h 14m 7s

About haloman30

  • Rank
    Owner of Chaotic United
  • Birthday 07/30/1999

Profile Information

  • Gender
  • Location
    I am the clouds
  • Interests

Community Information

  • Minecraft
  • Steam
  • Discord

Recent Profile Visitors

17,264 profile views


  • Elated
  • Currently Feeling Elated
  1. haloman30


  2. So, last night the forums and main website went offline for a little while. The reason? It wasn't just some typical maintenance this time - rather, it was a frantic effort to try and restore corrupted SQL data. What happened is that last night, my power flickered for just a mere second - and this would end up creating a nightmare scenario that I'd have to untangle. The webserver runs out of my house of course, and the power flicker caused it to briefly shut off. As a result of this power flicker, the SQL server used by the cPanel/WHM VM that hosts the websites themselves became corrupted - and I was initially unsure if I'd be able to get anything back. Luckily, it turns out that we had an automatic backup from just a couple months ago. Along with that, I was able to drag and drop the current databases into a clean mysql folder - and most of them turned out to be undamaged. A handful of tables were refusing to load - as part of the restoration process required a file called ibdata1 from the backup, and several new tables have been created since then that didn't exist before. These tables were the ones that failed to load. Chaotic United's forums didn't suffer from those tables much. Only one table was in that state, and it was just a table for basic caching - nothing important. Elaztek's website however had tables for Stratagem that were added - which is what we use over there (and in CU as well) to track various bugs, features, and overall progress for various projects. Thankfully, I was able to start up the old, damaged mysql folder with innodb_force_recovery set to 5 - and was able to then dump the stratagem tables for Elaztek, start up the clean and good mysql folder, and reimport them - and it worked. At that point, all tables in all databases were found to be clean with no obvious errors, and I could breathe a sigh of relief. We were extremely lucky to escape this situation unharmed, however it's still partially my fault. Not the power outage, of course - but the fact that the most recent backup was still two months old. You see, WHM (the software under which Chaotic United and Elaztek's websites run within, and used within virtually any webhost plan out there) can (and is) configured to run automatic backups. It was previously set to run backups every other day, once a week, and once a month together. The idea is that we'd have numerous backups available, going back up to 6 months. Then, in the event that a situation like this were to happen - no sweat, just restore the backup from yesterday or the day before. The issue is that there are perpetual disk space issues that I've continued to struggle with, and as such the machine that hosts the webserver is critically low on disk space just like everything else. Backups don't get created if there's less than 5% available - which, as of right now, there isn't. The good news is that Michael is going to help me solve this in the short term - since my long term solution is still nearly a year away. He's going to help me get a UPS for the machine in order to avoid any future power failures, as well as get me a spare 6TB hard disk that I can use to free up some breathing room on both my main PC as well as the webserver. This ought to ensure that this wont be an issue going forward, rather than having this be a potential risk for the next 12 months or so. The other good news is that, once again - we managed to come out the other side effectively unscathed. All data is intact, including the data for Elaztek's stratagem. All databases have been checked over and everything seems to be in order. But of course - in the offchance that you find something that seems as if it could be a sign of database corruption, let me know immediately. Other than that, well - I'm sorry. I apologize for putting us in this situation to begin with, and I'm going to do everything I can to ensure that it never happens again.
  3. haloman30

    7/15/2021 Update

    * Updated VentureChat from 2.22.8 to 2.23.3 * Hub server no longer runs under MCMyAdmin * Redesigned rank icons for donation store * Updated icons used in tab list to match classic cyan color revert - Removed Killerteddy
  4. That isn't why you were banned, at least not entirely. It was primarily because you were spamming the gif/video that caused people's Discord clients to instantaneously crash upon so much as viewing the channel - including sending those out to many members of the Discord and generally being kind of a dick to at least myself in direct messages (as well as continued crash gif spam). Please re-submit your appeal with this information accounted for, as you haven't really appealed for the thing that got you banned in the first place.
  5. haloman30

    7/13/2021 Update

    * Fixed an issue where PlotSquared wasn't able to check permissions correctly * Fixed HardcoreDarkness being impoperly configured on Age of Rebirth server - Removed Killerteddy
  6. haloman30

    7/11/2021 Update

    + Added MobMoney to Beta 1.7.3 (only block money support is available at this time) * Fixed solder subdomain not pointing to the correct server, thus causing players to be unable to download the Age of Rebirth modpack * Set EMC value for Basalt Cobblestone to 1 on Age of Rebirth * Set EMC value for Marble Cobblestone to 1 on Age of Rebirth * Set EMC value for Gray Limestone Cobblestone to 1 on Age of Rebirth - Removed Killerteddy
  7. haloman30

    7/9/2021 Update

    * Re-started the MC donation store * Updated Main MC server to 1.17.1 * Re-started Age of Rebirth (Modded MC) server * Reset Age of Rebirth world with a new seed * Recompiled LWCX to be compatiable with MySQL 8.0 driver * Finished migration of main MC server to new dedicated server * Updated HawkEye from 1.0.4b to 1.0.5 * HawkEye on Beta 1.7.3 now uses HikariCP instead of its own built-in connection pool * Fixed votes from vote sites not issuing rewards ingame * Fixed an issue where the server icon for the Main MC server would sometimes not display in the server list * Fixed topic thumbnails not displaying correctly in Chaotic United - 2021 theme - Removed Killerteddy
  8. Hey, everyone! A whole ton of stuff has been going on over the past few days. For the most part, it's just technical stuff - but there's still some genuine new features in some cases as well. Dedicated Server 2: The Unexpected Sequel First and foremost, the biggest technical change that's gonna enable a lot of stuff going forward is the migration to a new dedicated server. A little over a year ago, you may remember a post where I announced the migration to a brand new 32GB dedicated server that I was paying for myself. At the time, this was more than enough to handle all of our services with plenty of breathing room. However, as time went on, things started expanding. First, we actually started hosting the MC server for another community called Ruin Community. For those unfamiliar with them, it's one of a few MC servers that I played on back in 2012 while browsing to try and find a good server to make my home - which eventually ended up being Chaotic United. The other two being Ruin Community and Legendary Island of the Lost Treasures. Ruin had closed well before the old CU did, but Legendary Island actually persisted into 2015 before it eventually closed. However, as you all are most likely aware - I've got a compulsive attachment to things, and to the preservation of history. As they became available, I've been purchasing the domains associated with both Ruin and Legendary Island. In the offchance that some of the old members (or staff) wanted to try and check things out, I left a message with contact details on the homepage of Ruin's website. One day, I was contacted that the Ruin Community folk were attempting to re-unite and have a sort of reunion server to get everyone together again. Part of that effort was to host a private, whitelist-only MC server for the old Ruin folk - and I, being the one holding their original domain, happily offered to not only point the domain to their website, but also to point their Minecraft IP to their server as well as host it for them - no strings attached. I normally have a hard, unwavering rule about advertising other MC servers - as well as staff helping to host other servers - however, seeing as this was a server from my own childhood, it was a domain that I'd already owned for years prior, and that the server wasn't even a public server - I figured that this was a reasonable approach. If you do happen to be a member of the old Ruin Community and want to find them again, check our Partners page to join their Discord. Note that their server is NOT for any casual folk - it's intended for members of the original Ruin Community and nobody else. Anyway, with that history lesson out of the way - the other, more significant expansion was the recent move to BungeeCord. I had far underestimated the resource requirements of moving to BungeeCord - and it was at this point that Modded MC had to actually be briefly shut down, as the 32GB dedicated server wasn't enough to handle Ruin, Modded, and all the Bungee servers. However, with Modded offline, everything else was able to run without issue. That was, at least, until 1.17 - where for whatever reason, the server went from having 4-6GB free with all gamemodes online, to having 3-4 free with Minigames and the Waiting Room offline. Having modded shut off was one thing - as it never got a ton of attention. But having some of our gamemodes offline is a nonstarter. Theoretically I could tell Ruin to host their own server, but even then we'd still be at our limit - assuming that'd even do it. Plus, who else is going to be willing to either host a server with full access free of charge, or be willing to pay a monthly bill to keep a barely-played MC server up? So, instead - we made the decision to upgrade. Our old server was a SoYouStart dedicated server with 32GB of memory. Our new one is a proper OVH server - with all the modern bells and whistles. Automatic bill renewal so I can't accidentally forget to pay the bill, newer and more modern features, and in our case - an upgrade to 64GB of memory. As of now, our MC server, Ruin's server, and the donation store have been fully moved over. And of course, with this newfound freedom, we've got some new things we can do - such as... Return of Modded MC Such as turning Age of Rebirth back online! Finally! Not much has changed since the last time it was started - however, since some users had previously destroyed any hope of normal progression through more EMC generation exploits, as well as the fact that it's been down since last year - we've opted to do a world reset. The previous world is currently in the process of being archived and uploaded to the download center, and once it is you'll be able to revisit the old world anytime. Beta 1.7.3 Upgrades In addition to bringing Modded MC back online, we've also done some upgrades and updates to our Beta 1.7.3 server. Up until now, the Beta server has been kind of the forgotten child of Chaotic United. It had no real integration with the rest of the community, and barely anyone ever played on it. Even features that have been standard on our main MC server either took far too long to come to Beta (land claiming), or simply never arrived at all (dynmap). Well, thankfully, all that has finally changed. A few days ago, a user who goes by leow showed up and, initially, abused a duplication glitch and spammed diamond blocks all over the place. However, rather than stopping there and calling it a day, he reached out to me and offered to point me on how to fix it. Turns out there's a whole other world of Beta 1.7.3 servers that has been quietly brewing just out of my sight. There's a modern fork of CraftBukkit 1060 called Project Poseidon - which includes several feature enhancements, bugfixes, and optimizations. He also pointed me to a Discord centered around development for classic Minecraft - where I was able to track down and locate something I've been wanting to add to Beta for ages. Discord integration. Yes - as of now, we have a #b173-chatlogs channel on Discord, which works just like #mc-chatlogs and #rebirth-chatlogs - you can see when users join and leave, and you can see their chat messages and chat with them through that channel. But that's not all. Since Poseidon is based on CB1060 instead of our previous CB1000 build, we were able to finally introduce dynmap to Beta 1.7.3. It works just like it does on the main server - where you can see different perspectives as well as see outlines of land claims and worldguards. Another thing that we've done to hopefully ensure Beta runs as smooth as possible (as well as to allow for enough disk space for dynmap to work), is that we've moved it onto the new 64GB dedicated server. The old version of dynmap has no support for MySQL tile storage - and the VPS it was hosted on (which, fun fact - is the same VPS which hosted our own MC server for a while back during the Nuclear District days) only had 40GB of disk space - not enough for all those livemap tiles. Our dedicated server on the other hand has 2TB - which is more than enough to handle some livemap tiles. With all these changes, we've also decided to perform a world reset for Beta as well. The last reset was in 2019, so it was well past time for a reset anyways. Along with that, we wanted to introduce a world border to help keep the filesize down (and to prevent people from going to the Far Lands and crashing the whole server) - and doing this on an existing world could have made existing builds inaccessible. We plan to do a handful of other minor improvements over the coming days, most notably fixing the persistent crashing issue that happens after a while by having the server restart every 24 hours. Valheim Migration Lastly, and least notably, our Valheim server has been moved away from the old Microsoft Azure VPS and onto a new server. The IP address listed on the website and Discord has been updated, though no other significant changes have been made outside of that. With all this stuff going on, we hope that all of this will be just the start of a new beginning for Chaotic United. Whether or not it'll end up being one is yet to be seen (history unfortunately doesn't bode well for that prediction) - but for now, expect this to be the first step of many yet to come. Stay tuned.2
  9. Version 1.0.0


    This is the third world that was in our modern Beta 1.7.3 server. It was used up until the 2021 reset. There are two downloads for this world: - The original world unaltered from its final iteration - Same as the other download, however the diamond block grief near the spawn area has been removed The seed for this world was chosen through a community seed suggestions Discord channel. The seed that was used in this world was For clarification - I'm not referring to seeds that make excellent terrain generation - rather I'm saying suggest some wacky/interesting words/phrases/whatever and we'll run through some of them to find the best one by FlamingFox, which was shortened to For clarification - I'm not refe as the full seed was too long to fit. You cannot take this map, or any structures within it, and run it in your own server or someone else's. This is only for those who wants to continue their projects on it instead of having to start over in single player mode. Breaking this rule will result in your download privileges being permanently suspended and could result in your account being banned.


  10. haloman30

    7/5/2021 Update

    Some of the items in this changelog were introduced within the past 1-2 days. + Added new livemap page at (modifying dynmap's own web html page breaks during updates apparently) + Added livemap link to navigation menu + Added plugin to Beta 1.7.3: Dynmap + Added plugin to Beta 1.7.3: Announcement + Added plugin to Beta 1.7.3: DiscordCore + Added plugin to Beta 1.7.3: DiscordChatBridge * Recompiled Vault for 1.17 * Fixed Craftconomy3 recompilation not being compatible with existing API hooks * Fixed MobMoney messages not including the word 'Dollar' in pickup messages * Fixed economy interactions (MobMoney pickups) in Survival and Semi-Vanilla not working * Fixed crates not being available in SkyBlock * Updated livemap links on website and ingame to new URL * Updated MC Beta 1.7.3 server to use Project Poseidon (fork of CB1060) instead of stock CB1000 * Beta 1.7.3 server now has a livemap ( * Beta 1.7.3 server now has Discord integration (#b173-chatlogs) * Moved Beta 1.7.3 server to new dedicated server - Disabled plugin on Beta 1.7.3: MCMA_compat (BukkitCompat) - Removed Killerteddy
  11. + Added plugin: IridiumSkyblock + Added plugin: Themis * Updated to Java 16 * Updated all servers to MC 1.17 * Updated to PaperMC 1.17 #71 * Reverted custom hex color to &3 in most in-game uses (not all plugins support hex colors, so changing back to ensure consistency) * Fixed an issue where the vanilla join/leave messages would show in addition to bungeecord global join/leave messages * Updated Citizens from 2.0.27-b2166 to * Updated Dynmap from 3.1-beta5 to 3.2-beta1 * Updated LWCX from 2.2.6 to 2.2.8-dev * Updated Multiverse-Core from 4.1.0 to 4.3.0 * Updated WorldGuard from 7.0.4 to 7.0.6-SNAPSHOT * Updated WorldEdit from 7.2.2-dist to 7.2.6-SNAPSHOT * Updated VeinMiner from 1.15.1 to 1.17.9 * Updated CustomCrafting from to * Updated WolfyUtilities from to * Updated ChatControl to 5.9.1 * Updated PlotSquared to 6.0.5 * Updated EditableSign to 7.5.1 * Updated LogBlock * Updated VentureChat * Updated ServerSigns * Updated ProtocolLib * Updated LibsDisguises * Recompiled Craftconomy3 against 1.17 * Changed memory allocation of BungeeCord from 4096M to 1024M * Changed memory allocation of Hub (cu) from 4096M to 2048M * Increased Semi-Vanilla world border from 6000 to 10000 * Increased Survival world border from 6000 to 10000 - Waiting Room (hub) server is temporarily offline - Removed plugin: uSkyBlock - Removed plugin: WitherAntiCheat - Removed plugin: Tennis - Removed plugin: Soccer (Football) - Removed plugin: PartMan - Temporarily disabled plugin: CratesPlus - Temporarily disabled plugin: MagicStuff - Disabled CustomHeads as it does not currently function under 1.17 (will be re-added once it gets updated) - Removed Killerteddy
  12. Hey, everyone! Our MC server has just been updated to 1.17! Surprisingly, it didn't take too long compared to past updates - only a couple weeks from the initial release. For the most part, the server is unchanged from 1.16 - however, there are a few key changes to go over. Website Updates This is a fairly minor bit, but still worth mentioning. A couple days ago we quietly updated our forums theme. Not much within the theme itself has changed, however we've done some adjustments to the logo design (for the first time since 2016). Compare these two icons - the left one being our previous Discord icon, and the right being its updated replacement. One thing we wanted to do was make a more cleaned-up version of the HD logo. You see, this specific recreation of the logo came all the way back from 2016, when I was only just learning how to do graphic design. It wasn't bad per se, but it wasn't fully faithful to the original logo either. It had a little more curvature than made sense and if you looked closely, you'd be able to see some imperfections. Since 2016, I've gotten a fair bit better at graphic design, and so I wanted to go back in and make a more faithful recreation of the logo - and at the same time, make it look just a little more fresh and line up with the current visual design by turning what used to be 2 flat colors into subtle gradients based off of those original colors. Top it all off with a drop shadow, and you've got an update that - in my opinion - manages to be both a more faithful recreation of the original logo, while still feeling fresh enough to not feel like some kind of crufty carryover. For those who might be unaware of this original logo, the only remaining image of that logo is this: If you can't tell, it's almost laughably low-resolution, and was pulled from the old CU forums in 2013. From 2014 to 2016, this is as good as we had to work with. It wasn't until 2016 - where I was finally able to both recreate the icon as a vector graphic and track down the original font used - that I was able to finally utilize a higher resolution version of that logo. There almost certainly was a higher resolution out there - but the only person likely to have it is the original designer - MikeStardust. He's not around anymore, but hey - he made that original logo all the way back then, and we're still more or less using it now - so he ought to get some credit. SkyBlock Reset Now, first up in regards to the server itself, we've ended up having to make a fairly significant change to SkyBlock. Our original plan was to keep all the worlds left unchanged until 1.18, and then perform all the fresh resets at the same time as the big world overhauls. Unfortunately, our old SkyBlock plugin, uSkyBlock, has no update to 1.17 as of yet - along with that, there's been several issues that have been persistent with that SkyBlock plugin for a while - most immediately the issue with Nether Portals not taking players to the right locations. So, we've decided to switch to a brand new SkyBlock plugin - one that seems to have a lot more active development, and which is already updated for 1.17. There's no way to migrate data from the old plugin to the new one, so this will require a world reset. The silver lining is that we won't need to reset SkyBlock come 1.18 - this new world will be retained through that update. We hope that this new plugin won't be too difficult to adjust to. Please bear with us as we all explore and learn this new SkyBlock plugin - there might be some issues here or there that crop up. If there are any, feel free to report them on our Bug Tracker. Cracked Support We have to talk about cracked support going forward. Despite my own personal belief that people really should have bought Minecraft at some point during the 10 years that CU has been around, I've made it a point to maintain CU's cracked support on the MC server - primarily because, well, we've always been cracked. Chaotic United's MC server began life as a cracked server, and that support persisted even through Nuclear District. We haven't advertised it as a feature, and premium players (people who own a copy of MC) don't have to /login or /register, but it's been left in for the few cracked users we may still have from time to time. This is something that could potentially change going forward. Early on, cracked support wasn't really too difficult to maintain. It never got in the way. AutoIn helped ensure that skins were forwarded and that premium users never had to mess around with login commands. However, over time, things have somewhat degraded a bit and cracked support isn't nearly as seamless as we'd like. In terms of minor surface-level bugs, there will sometimes be cases where the "Please /login with /login <password>" message is shown after the automatic login confirmation - which has resulted in some confusion for existing and new users, causing them to think they had to log in. Not a big deal really, but still a source of confusion. There are, however, more serious bugs which sometimes show up (and sometimes don't). There have been several cases where username changes have resulted in someone being unable to play - as FastLogin will treat them as a cracked player. Now, this issue has seemingly been nonexistent since 1.16 - but still, it's an indicator that sometimes these kinds of critical issues can crop up. Along with that, cracked severs generally get treated less than favorably by both the Minecraft community as well as server lists. This is why we haven't advertised CU as a cracked server in many years. These issues alone aren't enough for me to drop cracked support, however. Most of these issues are minor, uncommon, and when major issues crop up, they often get fixed. However, those issues combine with something else that make me willing to consider it. There's been a thought floating around within the staff team for a while now that this cracked support may be holding us back further than we realize. It's possible that players join, realize we're cracked, and then dip as a result. It's also possible that server lists are able to identify us as cracked due to AuthMe and FastLogin and are quietly burying us in the deepest pages of the list. And, of course, it's also possible that neither of these are happening and that cracked support has nothing to do with our lack of player retention. So, starting sometime soon, cracked support will be temporarily dropped. The current plan is to start this with 1.17.1, though it may be sooner or later depending on how things go. We had originally planned to include this as part of the 1.17 update, but for a number of reasons we've opted to postpone it for just a bit longer. We aren't ready to commit to ditching cracked support permanently just yet, but we want to experiment and see if dropping this support happens to fix some of these issues - most likely, this will remain the case until the end of the year. The good news is that in early testing, AuthMe and FastLogin both work without issue on 1.17 - so there won't be any technical barrier to keeping cracked support. The bad news for you cracked folk out there is that if dropping this cracked support happens to turn around our population problems, then this will likely be a permanent change. Only time will tell. The Future To wrap things up, something I plan to do starting with 1.17 is properly get back into Minecraft server stuff again. I've been doing some reflection a bit to try and figure out why it is I haven't felt the desire to do anything on CU outside of the bare minimum maintenance here and there - and I think I've figured out why. The answer is in that very question - I haven't wanted to do much CU stuff for a while because for a while, it's largely just been maintenance and bugfixing and reimplementing old features again. I haven't been getting on and working on cool things because I want to make something cool, it's because there's some big problem that I have to solve in order to maintain a baseline. What I want to do starting with 1.17 is knock the two big looming clouds out of the way. Cross-server /tp and /warp functionality. I've been putting these off for a long time - and I think the time has come to finally fix this. Once that's done, I've got a comically long list of possible features that I want to work on - and I think that's the key. I need to make new things - even if those new things are small. I need to stop sitting around and working on features that already exist and fixing bugs - I need to get in and start doing what I used to do with the server - creating new things. I've devoted a long period of time lately towards Elaztek Studios and the Blamite Game Engine - it's been over a year since I last did a hard focus on Chaotic United. And while I don't plan to spend the entirety of the next year focused solely on Chaotic United, I think it's time for the pendulum to swing in the other direction for a bit. Stay tuned.
  13. haloman30

    07/01/2021 Update

    + Added theme: Chaotic United - 2021 + Added theme: Chaotic United - 2021 (Dark) * Set default theme to Chaotic United - 2021 * Updated logo design on main website * Updated Discord icon - Removed Killerteddy
  14. You're persistent - I'll give you that. I'll admit - originally I wasn't going to lift the ban. However, I've thought on it a bit further and I've decided that I will give you another chance. I looked back on message history and found out that it was actually longer ago than I had originally thought. That time duration combined with the wide-scale messaging of seemingly everyone who is or was formerly part of the community in an effort to rejoin demonstrates at least some level of commitment. That commitment isn't something we see very often - and combined with the fairly lengthy time since the ban suggests you may indeed have changed since those times before. Your ban has been lifted and you are free to rejoin the Discord at
This page is currently work-in-progress.



  • Rank: Owner
  • Nickname: haloman30
  • Playtime: 200 days

Current Activity

  • Online
  • Playing Survival


  • Money: $0


  • Money: $0


  • Claimed Plots: 10

Enforcement History