You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are pleased to announce the third release candidate for CloudNet 4.0. This release includes some smaller fixes for reported issues and improvements. We urge all users to install the update, as we will no longer provide support for RC2. Users who want to switch from 3.4.X to 4.0 can find instructions in the release information for RC1.
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 a small issue causing the default Influx config to throw an exception when starting up (contribution by @robertschuck)
Fixed some issues that were introduced in the last release related to the switch to NPC-Lib v2. This includes some exceptions which can be thrown in specific scenarios, as well as the issue that hitting into the air wouldn't be imitated by spawned NPCs
Fixed an issue where installed components on a service might differ from the requested ones, causing issues when (for example) using the smart module. A new collection of all installed templates/inclusions/deployments is now available from a SpecificCloudServiceProvider for api users to see which requested components are actually installed
✨ Improvements
Tasks and Groups are now able to specify environment variables per service. For api developers that feature is accessible from the ServiceConfiguration (and builder).
Add a command which allows to remove all created NPCs, or all NPCs which are targeting a specific group
Aside from tasks rename it's now possible to rename groups using groups rename <OldName> <NewName> as well.
Small code cleanups and performance improvements were made when using Waterfall (or a fork of Waterfall) as the proxy software.
📦 Other
Removed the ProcessHandle from the CloudServicePostProcessStartEvent as some services might not have one available and are therefore unable to call the event (for example services running in Docker).
Added two new events which are called on the local node instance and can be used by modules to modify the service preparation cycle: CloudServicePrePrepareEvent and CloudServicePostPrepareEvent. Note that the pre event is called after some initial data was made available, for example determining the initial templates that should get installed onto the service
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Update 4.0.0-RC3 - Blizzard
We are pleased to announce the third release candidate for CloudNet 4.0. This release includes some smaller fixes for reported issues and improvements. We urge all users to install the update, as we will no longer provide support for RC2. Users who want to switch from 3.4.X to 4.0 can find instructions in the release information for RC1.
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
✨ Improvements
tasks rename
it's now possible to rename groups usinggroups rename <OldName> <NewName>
as well.📦 Other
CloudServicePostProcessStartEvent
as some services might not have one available and are therefore unable to call the event (for example services running in Docker).CloudServicePrePrepareEvent
andCloudServicePostPrepareEvent
. Note that the pre event is called after some initial data was made available, for example determining the initial templates that should get installed onto the service🔗 Links
This discussion was created from the release 4.0.0-RC3 - Blizzard.
Beta Was this translation helpful? Give feedback.
All reactions