Become a premium member to remove ads

1.19.4 Update Released

3 posts in this topic

Hey, everyone - we've officially updated our MC server to 1.19.4!


In addition to getting things on the latest MC version, we've also made a number of bugfixes and improvements as well, some of which have been hanging around a bit too long. For now, we'll just go over the highlights:

/back Improvements

With the introduction of cross-server warp and teleportation, there were some cases where /back would behave strangely and would never seem to take you where you expected. This was because, by default, Essentials only keeps track of its own teleportation events. However, since warps and teleports were no longer handled through Essentials, using those commands wouldn't update the previous location properly. This issue has actually technically existed pretty much forever - it's just that back in the day, only admins would run into it, typically when using Multiverse's world teleportation commands. At first, this seemed like an unfixable issue - but turns out, Essentials has a handy option called register-back-in-listener which, wouldn't you know it, tells Essentials to monitor all teleportation events - completely fixing the problem. Why this isn't on by default is beyond me, but hey - it's on now, and as such using /back should once again work as expected.


Removal of ChatControl

For quite a long time, our chat filtering plugin hasn't exactly worked as expected - it doesn't work well cross-server, notifications don't work properly for staff (so in the event of a filter, we couldn't see what triggered it). As such, we've opted to remove the plugin for the time being. In the future, we'll be introducing a replacement which runs at the BungeeCord level and works cross-server properly. To be clear, however, no changes have been made to our chat rules, and racial slurs and other such content is still prohibited in chat.


Sit/Chairs Improvements

Originally, we used the Chairs plugin to allow for sitting on certain blocks - typically stairs and slabs. We later introduced SimpleSit alongside it to allow use of a /sit command that worked anywhere. As time went on, however, these plugins began to break and have various issues. Chairs broke outright, and while I did attempt to fix it, it'd have an issue where you would gradually sink further into the ground as the plugin "refreshed" its sit data, meanwhile SimpleSit no longer worked at all. Most recently, however, we started using GSit - which offered the features of both Chairs and SimpleSit, and had a few extra features, too - such as /lay. As of now, Chairs and SimpleSit are no longer used and have been replaced with GSit across all gamemodes. In addition, we've restored some previous functionality where Cauldrons could be sat in - both empty and with fluids. Overall, you shouldn't notice anything much different, besides sitting working better now.


Discord Join/Leave Messages

First and foremost, we've (for real this time, hopefully) fixed the issue where Owners and Managers wouldn't have any join or leave messages displayed in the #mc-chatlogs Discord channel. This was originally done on purpose, as for some time we didn't have a vanish plugin that worked properly across the entire BungeeCord network - so in order to prevent staff from being revealed in Discord, join/leave notifications were blocked for them entirely. Lately, though, we've been using a new plugin that does work cross-server. However, staff still had the permission nodes which were used to block out their join/leave messages. This was mostly still the case with Managers and Owners, since both ranks have all server permissions - and the permissions were not directly negated from their ranks. This has now been fixed, and join/leave messages will show as expected for all users.


Server Renaming

Previously, our BungeeCord server naming had a strange quirk - the "hub" and "cu" servers. This is for a couple reasons: first of which, was that the BungeeCord configuration can have its roots traced back to the one we used back when we were merged with NuclearDistrict - where we had three servers: "nd", "cu", and "hub". The ND server was NuclearDistrict's survival server, the CU server was our MC server, and the Hub server was used as a bridge between the two (fun fact - the spawn used in our "hub" server is a modified version of that one, and you can view the original one we used in ND by heading to /warp mergehub). The second reason comes down to how we migrated to BungeeCord more recently. For those who weren't around, we originally had our entire MC server - all gamemodes, all worlds, everything - under a single Bukkit (or rather, Spigot/Paper) server.


While this had its benefits, such as not having to do any extra work to make things like chat, teleports, etc. work cross-server, along with making updates a lot faster, it also had some serious drawbacks. Diagnosing bugs took longer, as every plugin for every feature across the entire server was sharing one Bukkit instance - thus resulting in a larger list of possible plugins to go through to diagnose and fix. It also resulted in much poorer performance, which eventually became a severe issue around 1.13/1.14 - having that many worlds and plugins all sharing one Bukkit instance was pushing the limits of what the server software was capable of handling.


As such, we decided to, for real, migrate everything over to BungeeCord. We'd actually explored this a few times prior - but each time, the amount of legwork, headache, and compromises made weren't justifiable. However, with how bad the performance issues became, it was time. However, it wasn't a one-and-done process - this was a longer process that went on over the span of a few months or so, where gamemodes were gradually migrated out of the main server and into their own separate servers. The original "Main" server was named "cu" in the BungeeCord config during this process, and when everything else was moved out, the Hub and Builder worlds were left behind, and the original MC server would instead act as the hub going forward. This resulted in the confusing situation of having a "cu" server and a "hub" server - where the "cu" server is what is generally thought of as the hub, and the "hub" server is typically considered a fallback or "waiting room" that exists in the case of the "cu" server going offline.


At this point, there's certain data which relies on the servers' existing names - such as the MySQL database used to store warp data. As such, changing the "cu" server name wasn't feasible - what we have done, however, is renamed the "hub" server to "fallback" in the BungeeCord configuration - and renamed it to "Fallback Hub" in the #mc-chatlogs channel. At a future date, the "Main" server will be renamed in the Discord messages as well, however we've left them as-is for the time being.



Unfortunately, with the update, a couple plugins ended up breaking (or rather, just refuse to even attempt to work outright):

  • LibsDisguises - This is the plugin we use for disguises in-game, and with its absence, you won't be able to disguise. This will be restored as soon as a 1.19.4 build is released, and you won't lose access to any previous disguises.
  • CustomOreGenerator - This is the plugin we use in Survival to generate Durite Ore within The End. Unfortunately, with its absence, Durite Ore will NOT generate, at all. We strongly advise that you avoid any exploration within The End for the time being until this has been resolved - as any new terrain you discover will have no Durite present at all. As with LibsDisguises, we'll be posting an update on Discord as well as a reply to this topic once everything is sorted out and these plugins are restored.


The above plugins have both been reintroduced as of 3/31/2023.


For now, though, that's all we've got! We've been a bit quiet and lacking when it comes to posting announcements on the forums lately - and that's something that we'll be working to ensure changes going forward. After all - why would anyone else use the forums if announcements don't even get posted there? Additionally, you can view the full changelog of today's changes here - there's some other minor stuff that wasn't touched on above.


As per usual, if you find any bugs while playing, be sure to let us know on the bug tracker! Once we get some immediate features finished up, we plan on doing a sweeping bugfix pass in the not-too-distant future as one of the final steps before we start exploring advertisement options.

Edited by haloman30
Cross out LibsDisguises and CustomOreGenerator removal since both are added as of now

Share this post

Link to post
Share on other sites

Hey folks, a quick update on the MC server:


LibsDisguises has been reintroduced! You can once again use all of your disguises just as before. Perhaps more significantly, we've done a plethora of bugfixes! The majority of these bugs apply to Survival and relate to custom content (such as Durite), but there's a number of other fixes, too. Some key highlights include:

  • Mending and Silk Touch now work properly on custom tools - Previously, Mending did not work properly on any custom tool, and Durite tools with extra-break functionality didn't work properly with Silk Touch. Both of these issues have been fixed.
  • Custom tools can now be repaired in a crafting table - Just like with vanilla tools, you won't be able to keep any NBT or enchantment data by repairing this way, but if you've got some standard Durite (or other custom) tools, you can slap them into a crafting table together to repair them.
  • Durite can now be smelted in a Blast Furnace
  • /bal now works properly in Semi-Vanilla
  • A handful of other quality-of-life fixes and improvements


For those interested, you can read the full changelog here: 


Share this post

Link to post
Share on other sites

Hey folks, another quick heads up:


CustomOreGenerator has been updated and reintroduced - meaning you can now feel free to explore The End in Survival as much as you'd like.


That is all (for now).

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now