Skip to content

4.0.0-RC10 - Blizzard

Pre-release
Pre-release
Compare
Choose a tag to compare
@0utplay 0utplay released this 01 Apr 15:07
· 153 commits to beta since this release
887ad7c

Update 4.0.0-RC10 - Blizzard

We are pleased to announce the tenth 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 RC9. 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 that npc inventories might exceed 54 slots and cause errors (#1306)
  • Fixed that services started by the smart module ignored the allowed nodes option (#1315)
  • Fixed that parent directories might not be created when using a sftp storage (#1225)
  • Fixed that the node would not start services if the exact memory limit was reached (#1322)
  • Fixed that npcs and info lines are not removed on static services (#1349)
  • Fixed that group configurations are not converted correctly due to nullabilty (#1274)

✨ Improvements

  • Minecraft 1.20.4 is now fully supported (#1351)
  • The adventure component format is now supported in npc info lines (#1321)
  • The LabyMod module was updated to the standard of LabyMod 4 (#1309)
  • Added support for all kind of java time serialization to the databuf (#1285)
  • The syncproxy module checks permissions now later in the login process (#1308)
  • When creating velocity templates the forwarding secret file is generated automatically by cloudnet (#1355)
  • Non-existant signs are ignored when a new sign is choosen (#1371)
Dependencies
artifact id usage
driver When developing plugins or modules, available on all platforms.
node When developing a module which needs more specific access to node functions than the driver can offer.
wrapper-jvm When developing plugins which need some more specific access to the service api than the driver can offer.
bridge When trying to catch player events and/or interacting with players regardless where they are on the network.
bom When you want to import all dependencies with the same version based on the imported bill of materials.

To add the CloudNet dependency using gradle:

repositories {
  // ensure maven central is added
  mavenCentral()
}

dependencies {
  // optional - you can also specify versions directly
  implementation platform('eu.cloudnetservice.cloudnet:bom:4.0.0-RC10')
  compileOnly 'eu.cloudnetservice.cloudnet:driver'

  // without bom
  compileOnly 'eu.cloudnetservice.cloudnet:driver:4.0.0-RC10'
}

To add the CloudNet dependency using maven:

<!-- optional - you can also specify versions directly -->
<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>eu.cloudnetservice.cloudnet</groupId>
      <artifactId>bom</artifactId>
      <version>4.0.0-RC10</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

<dependencies>
  <dependency>
    <groupId>eu.cloudnetservice.cloudnet</groupId>
    <artifactId>driver</artifactId>
    <version>4.0.0-RC10</version> <!-- only needed when bom is not used -->
    <scope>provided</scope>
  </dependency>
</dependencies>

🔗 Links