Skip to content

4.0.0-RC9 - Blizzard

Pre-release
Pre-release
Compare
Choose a tag to compare
@byRoadrunner byRoadrunner released this 09 Jul 17:44
· 172 commits to beta since this release
4.0.0-RC9
f6ca4c3
This commit was signed with the committer’s verified signature.
0utplay Aldin
GPG key ID: 1158B6C34686E264
Learn about vigilant mode.

Update 4.0.0-RC9 - Blizzard

We are pleased to announce the ninth release candidate for CloudNet 4.0. This release includes fixes for reported issues and some improvements. We urge all users to install the update, as we will no longer provide support for RC8. Users who want to switch from 3.4.X to 4.0 can find instructions in the release information for RC1.

Please also see the changelog for RC6, this contains the detailed information about the switch to Dependency Injection in the API.

Cheers!
(Please remember, CloudNet is provided as-is - we are not responsible for data loss or corruption. You are encouraged to back up your files before any updates!)

Changelog

🐛 Fixes

  • Fixed an issue that led to console tab suggestions being in the wrong order (#1152)
  • Fixed that some buffers were not closed resulting in memory leaks (#1146)
  • Fixed an issue with the service create rest api which had request method assigned (#1166)
  • Fixed an issue that resulted in assigning default templates on both the group and the task when using the task setup (#1175)
  • Fixed an issue with opaque URIs causing exceptions in the rest api (#1181)
  • Fixed that http header in service inclusions were required instead of optional (#1188)
  • Fixed that exceptions in the sign module are not printed (#1219)
  • Fixed an issue where http handlers were called in reversed order (#1227)
  • Fixed an issue in the mysql module which would set ssl explicitly to false leading to connection problems when using recent database versions (#1256)
  • Fixed an issue that would result in npcs not spawning at all due to the fact that chunks were already loaded (#1255)
  • Fixed an issue where setting the floating npc item to AIR would break the armorstands settings (#1249)
  • Fixed an issue with http session handlers having the wrong http method (#1269)
  • Fixed an issue where module dependencies are loaded from repositories first instead of the url if given (#1259)
  • Fixed an issue with syncproxy placeholders overlapping with some bridge placeholders (#1254)
  • Fixed that the memory applied to the cloudnet launcher affected the memory of the node too (#1221)

✨ Improvements

  • The jvmOptions of a task or a group are repeatable now (#1163)
  • The document api was rewritten allowing for custom document types (#1178)
  • Updated the openapi spec according to changes in the ServiceConfiguration (#1218)
  • The cloud now warns about missing manifests and main classes in jars it is trying to start (#1217)
  • Improved the look of the default signs layout (#1230)
  • Added a new @Service annotation to integrate the service registry into dependency injection (#1232)
  • Added a placeholder to the syncproxy tablist to display the name of the player (#1235)
  • Minecraft 1.20(.1) is now fully supported (#1252)

⚠️ Important notice

It is important to note that setting the -xmx and -xms parameters in the startup scripts now has no effect on the node's memory. To set the memory for the node the property cloudnet.node.memory must be set in the launcher.cnl. The value in launcher.cnl is always set in MB for the xmx and xms parameters. The default value is 256MB.

You can add the following lines to your launcher.cnl to control the memory setting.

# This value sets the memory settings of the JVM for the cloudnet node.
# The value set here is to be specified in megabytes and describes -xmx as well as -xms.
#
# A change in the associated start files (e.g. start.sh) has no effect on the node and should therefore not be changed.
var cloudnet.node.memory 256

🔗 Links

Assets 3
Loading
0 Join discussion