4.0.0-RC9 - Blizzard

[byRoadrunner]

Update 4.0.0-RC9 - Blizzard

We are pleased to announce the nineth 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 (fix: properly order console tab suggestions #1152)
• Fixed that some buffers were not closed resulting in memory leaks (fix: properly close buffers to prevent memory leaks #1146)
• Fixed an issue with the service create rest api which had request method assigned (fix: added missing methods = "POST" in V2HttpHandlerService inside the Rest Module #1166)
• Fixed an issue that resulted in assigning default templates on both the group and the task when using the task setup (Removed that the task template is configured in the group configuration #1175)
• Fixed an issue with opaque URIs causing exceptions in the rest api (fix: ignore http requests with an opaque uri #1181)
• Fixed that http header in service inclusions were required instead of optional (fix: headers in service inclusions should be optional #1188)
• Fixed that exceptions in the sign module are not printed (fix: log throwable catched when ticking signs #1219)
• Fixed an issue where http handlers were called in reversed order (fix: reverse http handler calling 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 (fix: do not set ssl explicitly to false and use mariadb 11.1.1-rc in tests #1256)
• Fixed an issue that would result in npcs not spawning at all due to the fact that chunks were already loaded (fix: spawn all npcs in already loaded chunks on start #1255)
• Fixed an issue where setting the floating npc item to AIR would break the armorstands settings (fix: set the floating item to null if the material is air #1249)
• Fixed an issue with http session handlers having the wrong http method (fix: Switch HTTP-Methods for Session Rest-Handler from GET to POST #1269)
• Fixed an issue where module dependencies are loaded from repositories first instead of the url if given (fix: Load module dependency first by URL to inline behaviors with jup… #1259)
• Fixed an issue with syncproxy placeholders overlapping with some bridge placeholders (fix: correctly replace placeholders in syncproxy tablist #1254)
• Fixed that the memory applied to the cloudnet launcher affected the memory of the node too (fix: the launchers memory should not effect the node memory #1221)

✨ Improvements

• The jvmOptions of a task or a group are repeatable now (fix: allow repetition of jvm options and command line arguments #1163)
• The document api was rewritten allowing for custom document types (chore: rewrite document api #1178)
• Updated the openapi spec according to changes in the ServiceConfiguration (chore: update openapi specs due to recent ServiceConfiguration changes #1218)
• The cloud now warns about missing manifests and main classes in jars it is trying to start (feat: warn about missing manifests and main classes #1217)
• Improved the look of the default signs layout (chore: improve the default signs layout #1230)
• Added a new @Service annotation to integrate the service registry into dependency injection (feat: enable injection of services from the service registry #1232)
• Added a placeholder to the syncproxy tablist to display the name of the player (chore: add %player_name% placeholder to syncproxy tablist #1235)
• Minecraft 1.20(.1) is now fully supported (feat: support minecraft 1.20 #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

• Support Discord: https://discord.cloudnetservice.eu/
• Javadocs: https://cloudnetservice.eu/cloudnet/docs/4.0.0-RC9/
• Maven Dependencies: https://central.sonatype.com/search?q=eu.cloudnetservice.cloudnet
• If you found any issue, please report it on our issue tracker: https://github.com/CloudNetService/CloudNet-v3/issues

---

This discussion was created from the release 4.0.0-RC9 - Blizzard.