Recommended Build 7.2.3 (and how you can help us with API 8/1.14)

Announcements
1

Hey everyone!

New Recommended Build 7.2.3 for SpongeForge and SpongeVanilla

We have just released a new recommended build of SpongeForge and SpongeVanilla! Version 7.2.3 is now available for your general usage. No big things to worry about this time, but here are some things that have changed:

  • LaunchProjectileEvent will now be fired if no-one is listening to SpawnEntityEvent but a plugin is listening to LaunchProjectileEvent
  • Fixed death event not firing when using mods such as FirstAid that cancel the LivingHurtEvent to do their own damage calculations.
  • Increased performance of getting Users from the UserStorageService
  • Stagger saving and unloading offline user data to reduce the liklihood of actions such as Nucleus’ /invsee causing User {} is not initialized errors to bring down the server.
  • When User {} is not initialized errors occur, the server no longer crashes.
  • Server#copyWorld() now registers the world.
  • Fix command completion when using GenericArguments#allOf
  • Ensure that child commands do not have arguments added to the context if there are no arguments to add.
  • If chunk-load logging is enabled, queueing a chunk for load is now logged.
  • Even more performance and memory improvements!

We also added the following features that are slated for API 7.3. They are available now if you build against API 7.3 snapshots, but note that the APIs are not yet in a release build of API 7 and so are subject to change:

  • Simple placeholder support.
  • SaveChunkEvent.
  • select and whilst instead of stopFilter and skipFilter in BlockRay.
  • New world serialisation behaviour - METADATA_ONLY, which saves everything about a world, but not its chunks.

Downloads

You can download these builds from our Downloads page, https://spongepowered.org/downloads

API 8 (and what you can do to help!)

We’re now getting ever closer getting a build of Sponge for MC 1.14.4 to compile and run (and when we say run, kind of semi-not-really-playable because it’ll crash within seconds of loading, but progress)!

Are you a developer itching to have your name inscribed on the annals of Spongie’s history (the Git commit log) and the gratitude of everyone here? Want to dive in, but not sure where to start? Fear not, for @gabizou recently filled the inboxes of anyone who dares to watch SpongeCommon with many, many issues - and each one of these is a small yet crucial task that needs doing - fixing a file that exists and works in our 1.12.2 builds, but does not in 1.14.4. The person that does that could be you!

Please do not let gabi’s effort and the filling of my inbox be in vain! The issues in question are available right here. Pick an issue, which will have a link to a file and leave a comment stating you’re working on it.

Please only pick one issue at a time, and do not ask to work on something until you are ready to start on it there and then. That way, we don’t have a bunch of “claimed” files at any one time that no-one has started on.

Once you’ve updated the file, move it from the invalid sourceset to the main sourceset in SpongeCommon, or if the file is in the org.spongepowered.common.mixin package, move it to the mixin sourceset in SpongeCommon. Then commit the file to a branch, including the phrase “fixes #issuenumber”, and make a Pull Request. The PR description does not need to be fancy, as long as it references the issue. We’ll review, suggest any changes we need you to make, and once that’s done, your place in history will be sealed! Hurrah!

Hopefully this will give those of you that want to help some direction on how to help! If you have questions, ask away in #1dot14updates in Discord.

This is a huge update and a huge milestone for us, come and be part of it!

9 Likes