From 13e85c6e4e3f1596954a48489f02a16cc0becb41 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 30 Aug 2024 18:21:01 +0200
Subject: [PATCH 01/28] New translations en_us.properties (French) [ci skip]

---
 node/src/main/resources/lang/fr_FR.properties | 394 ++++++++++++++++++
 1 file changed, 394 insertions(+)
 create mode 100644 node/src/main/resources/lang/fr_FR.properties

diff --git a/node/src/main/resources/lang/fr_FR.properties b/node/src/main/resources/lang/fr_FR.properties
new file mode 100644
index 0000000000..a5aa3ebefc
--- /dev/null
+++ b/node/src/main/resources/lang/fr_FR.properties
@@ -0,0 +1,394 @@
+#
+# Copyright 2019-2024 CloudNetService team & contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+cloudnet-init-eula-not-accepted=If you don't accept the eula, you cannot run a minecraft server\!
+cloudnet-init-eula=Do you agree to the Mojang EULA (https\://aka.ms/MinecraftEULA)?
+cloudnet-init-setup-cluster-cluster-id=What is the id of your cluster? (you can find it in the config.json on of your nodes)
+cloudnet-init-setup-cluster-install=Is this node part of a cluster? (MultiRoot)
+cloudnet-init-setup-cluster-list-nodes=What are the names of your already existing nodes? (separated by ";")
+cloudnet-init-setup-cluster-node-host=What is the host and port of the node "{0$node$}"? (you can find it in the config.json at "listeners")
+cloudnet-init-setup-host-address=On which host should the services be started on? Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+cloudnet-init-setup-internal-host=On which host and port should CloudNet run on? (This is NOT your proxy host/port)
+cloudnet-init-setup-memory=How much memory (in MB) can the services running on this CloudNet node use?
+cloudnet-init-setup-node-id=What should the name of this CloudNet node be?
+cloudnet-init-setup-tasks-javacommand=What is the path to the Java executable?
+cloudnet-init-setup-tasks-proxy-environment=What should be the environment of the proxy?
+cloudnet-init-setup-tasks-proxy-version=Which ServiceVersion should be used on the proxies?
+cloudnet-init-setup-tasks-server-environment=What should be the environment of the services?
+cloudnet-init-setup-tasks-server-version=Which ServiceVersion should be used on the services?
+cloudnet-init-setup-tasks-should-install-proxy=Should a default proxy be created?
+cloudnet-init-setup-tasks-should-install-server=Should a default lobby be created?
+cloudnet-init-setup-web-host=On which host and port should CloudNet's WebServer run?
+cloudnet-init-default-modules=Which default modules should be installed? (separated by a space)
+#
+# Console animations
+#
+ca-question-list-cancel=You can always cancel the process by typing "cancel"\!
+ca-question-list-cancelled=The process has been cancelled\!
+ca-question-list-explain=Use the arrow keys to scroll through all possible values (if there are default values specified). If there is a recommended value available, it is in the command input line by default
+ca-question-list-invalid-default=Please provide a valid value\!
+ca-question-list-possible-answers-list=Possible answers\: {0$values$}
+ca-question-list-question-list=You have to provide one of the following\: {0$values$}
+#
+# Network
+#
+client-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] has closed the connection
+client-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] connected to the server
+server-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was closed
+server-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was connected
+network-listener-bound=Successfully bound a network listener to the address "{0$address$}"...
+network-listener-bound-exceptionally=Unable to bind network listener to "{0$address$}"\: {1$reason$}
+network-selected-transport=Network components are using {0$transport$} transport
+network-selected-dispatch-thread-type=Network dispatchers are using {0$type$} threads
+startup-failed-no-network-listener-bound=Unable to complete startup, no network listener was bound successfully\! CloudNet will stop in 5 seconds
+#
+# Application lifecycle
+#
+start-version-provider=Loaded {0$amount$} service versions...
+start-module-updater=Applying needed updates to installed modules...
+start-commands=Registered commands...
+start-node-connection-try=Trying to connect to node {0$name$}...
+start-node-connection-failure=Unable to connect to node {0$name$}\: {1$reason$}
+start-node-connection-waiting=Waiting for {0$amount$} node connections to establish...
+start-requesting-data=Requesting cluster sync from head node...
+start-connect-database=Using database {0$database$}...
+start-done=Startup done, starting tick loop (Took {0$starttime$}ms)
+stop-application=Stopping application...
+stop-node-connections=Closing connections to all nodes of the cluster...
+stop-providers=Closing providers...
+stop-network-components=Closing network components...
+stop-services=Stopping all running services...
+stop-delete-temp=Deleting temporary files...
+#
+# Services
+#
+cloudnet-service-jar-file-not-found-error=No application file found for CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}]\! Please check the availability of this file. Using the "version" command a version can be installed.
+cloudnet-service-manager-cpu-usage-to-high-error=The CPU load is too high to create a new service\! The system will try to start this service as soon as there are enough resources.
+cloudnet-service-manager-max-memory-error=The maximum allocatable memory has been reached (of CloudNet, other system resources might still be available)\! The limit has to be increased or other services need to be stopped.
+cloudnet-service-networking-connected=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] was successfully connected to the channel [serverAddress\={3$serverAddress$} clientAddress\={4$clientAddress$}]
+cloudnet-service-networking-disconnected=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] was closed by the channel [serverAddress\={3$serverAddress$} clientAddress\={4$clientAddress$}]
+cloudnet-service-post-delete-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been deleted
+cloudnet-service-post-prepared-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been prepared
+cloudnet-service-post-start-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been started
+cloudnet-service-post-stop-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been stopped
+cloudnet-service-post-start-message-different-node=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] is starting on node {3$node$}...
+cloudnet-service-post-stop-message-different-node=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] is stopped on node {3$node$}...
+#
+# Cluster
+#
+cluster-local-db-warning=CloudNet runs in a cluster, but a local embedded database is used\! This can cause big synchronization problems. Please consider switching to a central database (like MongoDB) that all nodes can connect to.
+cluster-server-soft-disconnect=Marking node [uniqueId\={0$id$}] temporarily as disconnected because it was idling for too long\! [lastUpdate\={1$time$}ms ago]
+cluster-server-hard-disconnect=Disconnecting node [uniqueId\={0$id$}] because it did not reconnect within {1$maxDisconnectTime$}ms\! [lastStateChange\={2$time$}ms ago]
+cluster-server-networking-authorization-failed=Authorization unfortunately failed to the node with the address {0$address$}
+cluster-server-networking-disconnected=The connection to the node [uniqueId\={0$id$}] was interrupted\!
+cluster-sync-accept-yours=Using and applying the local version to the cluster...
+cluster-sync-accepted-theirs=Applying the proposed change...
+cluster-sync-change-decision-question=Do you want to [1] accept the changes, [2] apply your version, [3] skip the change?
+cluster-sync-skip=Skipped applying of the current change
+#
+# Modules
+#
+cloudnet-load-modules-invalid-checksum=The checksum of the module {0$module$} does not match, aborting update
+cloudnet-install-modules-invalid-checksum=The checksum of the module {0$module$} does not match, aborting installation
+cloudnet-post-load-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was successfully loaded
+cloudnet-post-reload-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was reloaded successfully
+cloudnet-post-start-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was started successfully
+cloudnet-post-stop-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was stopped successfully
+cloudnet-post-unload-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was removed successfully
+#
+# Commands
+#
+command-no-description=No command description provided
+command-confirmation-no-requests=There are no commands to confirm
+command-confirmation-required=Please confirm executing the command by executing '&bconfirm&r' within 30s
+invalid-command-sender=This command cannot be executed by ''{0$source$}''
+invalid-command-syntax=Invalid syntax\! Use {0$syntax$}
+no-such-command=Command could not be found\! For help, use the command "help"
+argument-parse-failure-no-input-was-provided=No input provided
+argument-parse-failure-boolean=The given input {0$input$} is not a boolean
+argument-parse-failure-number=The given input {0$input$} is not a number
+argument-parse-failure-char=The given input {0$input$} is not a char
+argument-parse-failure-string=The given input {0$input$} is not a string
+argument-parse-failure-uuid=The given input {0$input$} is not an uuid
+argument-parse-failure-enum=The given input enum {0$input$} is not one of the following {1$values$}
+argument-parse-failure-regex=The given input &b{1$input$}&r does not match &b{0$regex$}
+argument-parse-failure-duration=The given input {0$input$} is not a duration
+argument-parse-failure-flag-unknown=The given flag {0$flag$} is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag {0$flag$} can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag {0$flag$}
+argument-parse-failure-flag-no-permission=You are not allowed to use this flag
+missing-command-permission=You are not allowed to execute this sub command
+#
+# General commands
+#
+command-general-group-does-not-exist=That group doesn't exist\!
+command-any-host-and-port-invalid=The given input {0$input$} is not a valid host and port. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+command-assignable-host-invalid=The given input {0$input$} is not an assignable host. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+command-any-host-invalid=The given input {0$input$} is not a valid host address. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+#
+# Command Help
+#
+commnad-help-description=Shows all commands and their description
+command-help-docs=Follow this url {0$url$} to get to the documentation for the {1$command$} command
+command-help-docs-no-url=The {0$command$} command has no documentation url
+#
+# Command Me
+#
+command-me-description=Displays all important information about this node and the running jvm
+#
+# Command clear
+#
+command-clear-description=Clears the entire console of the node to get a better overview
+#
+# Command Cluster
+#
+command-cluster-description=Manages the cluster and provides information about it
+command-cluster-add-node-success=Registered the new node ({0$name$}) to the cluster configuration
+command-cluster-node-not-found=That node doesn't exist
+command-cluster-node-set-drain=Draining is now {0, choice, 0\#disabled|1\#enabled$drain$} for node {1$node$}
+command-cluster-push-static-service-failed=Failed to deploy the static service to the cluster
+command-cluster-push-static-service-not-found=The static service was not found
+command-cluster-push-static-service-running=The static service is running. Stop the service to deploy it into the cluster
+command-cluster-push-static-service-starting=Starting the deployment of the static service...
+command-cluster-push-static-service-success=Successfully deployed the static service into the cluster
+command-cluster-push-static-service-existing=The received static service {0$service$} already exists, aborting deployment
+command-cluster-push-static-service-received-success=Successfully received the deployed static service {0$service$}
+command-cluster-push-static-service-running-remote=The received static service {0$service$} is running, aborting deployment
+command-cluster-push-template-compress=Compressing the template {0$template$}...
+command-cluster-push-template-failed=Failed to send the local template {0$template$} to the cluster
+command-cluster-push-template-success=The local template {0$template$} was successfully sent to all nodes
+command-cluster-remove-node-success=The node {0$node$} has been removed successfully
+command-cluster-start-sync=The cluster sync starts now
+#
+# Command Service
+#
+command-service-description=Manages all services in the cluster
+command-service-copy-no-default-template=The service you provided does not have a default template, use "copy {0$name$} template\=storage\:prefix/name" to provide a template you would like to copy to
+command-service-copy-success=The service {0$name$} was successfully copied to the template {1$template$}
+command-service-add-deployment-success=The deployment {0$deployment$} was successfully added to the waiting deployments
+command-service-deploy-deployment-success=The resources of the service were successfully deployed
+command-service-add-inclusion-success=The inclusion {0$inclusion$} was successfully added to the waiting integrations
+command-service-include-inclusion-success=All waiting inclusions were downloaded and installed to the service
+command-service-add-template-success=The template {0$template$} was successfully found and was added to the waiting templates
+command-service-include-templates-success=All waiting templates were copied to the service
+command-service-service-not-found=That service doesn't exist
+command-service-toggle-disabled=Disabled the automatic console logging for {0$service$}
+command-service-toggle-enabled=Enabled the automatic console logging for {0$service$}
+#
+# Command Create
+#
+command-create-description=Creates one or more new services based on a task or completely independent
+command-create-by-task-starting=Starting to create {1$amount$} services for {0$task$}
+command-create-by-task-failed=The services couldn't be created
+command-create-by-task-success=The services were created based on the task. They can be managed with the 'service' command
+#
+# Command Debug
+#
+command-debug-description=Toggle the global debug mode
+#
+# Command exit
+#
+command-exit-description=Stops the program and all managed subprocesses
+#
+# Command Migrate
+#
+command-migrate-description=Allows to migrate data known to CloudNet between different storages
+command-migrate-current-database=Migration of {0$db$} in progress...
+command-migrate-database-connection-failed=The connection to the database failed
+command-migrate-source-equals-target=Migrating data to the same database is not possible
+command-migrate-success=Migrating {0$source$} to {1$target$} was successful
+command-migrate-unknown-database-provider=This database type does not exist
+#
+# Command Modules
+#
+command-modules-description=Manages installed modules and allows to load local or install remote modules
+command-modules-install-missing-depend=The module {0$module$} requires these dependencies to run\: {1$dependencies$}
+command-modules-module-already-loaded=The module {0$module$} is already loaded
+command-modules-module-file-not-found=The file {0$path$} does not exist
+command-modules-module-not-a-file={0$path$} is not a file
+command-modules-module-installed=The module {0$module$} was successfully installed
+command-module-skipping-checksum-fail=The checksum of the official module {0$module$} did not match but the validation was skipped\!
+command-modules-checksum-validation-skippable=The module checksum of the official module {0$module$} did not match\! (most likely your module definition is outdated, restart CloudNet to auto update them) You can install the module by appending "--ncv" to the command (\! could lead to problems \!)
+command-modules-module-not-loaded=The module {0$module$} is not loaded
+command-modules-module-not-started=The module {0$module$} is not started
+command-modules-module-not-stopped=The module {0$module$} is not stopped
+command-modules-module-runtime-module=The module {0$module$} is not reloadable as it is a runtime module
+command-modules-no-such-installable-module=There is no module named {0$name$}
+command-modules-module-already-installed=The module {0$name$} is already installed. Updates of modules are performed automatically when CloudNet is restarted
+command-modules-module-uninstall=The module {0$module$} was successfully uninstalled
+command-modules-module-uninstall-failed=The module {0$module$} could not be uninstalled. Check the console log for further information
+#
+# Command Config
+#
+command-config-description=Administration of the cloudnet node configuration
+command-config-node-ip-alias-already-existing=The ip alias {0$alias$} already exists
+command-config-node-ip-alias-added=The host address {1$address$} aliased as {0$alias$} was added successfully
+command-config-node-ip-alias-remove=The ip alias {0$alias$} was removed
+command-config-node-add-ip-whitelist=The ip {0$ip$} was added to the ip whitelist
+command-config-node-remove-ip-whitelist=The ip address {0$ip$} was removed from the ip whitelist
+command-config-node-set-max-memory=The maximum memory for the node is now set to {0$memory$}
+command-config-node-set-java-command=The default java command for services is now set to {0$path$} using Java version {1$version$}
+command-config-node-reload-config=The node configuration was reloaded. Note\: Not all changes are applied without a restart
+command-config-reload-config=Reloaded the node, task, group and permission configurations. Note\: Not all changes are applied without a restart
+#
+# Command Groups
+#
+command-groups-description=Administers the configurations of all persistent groups
+command-groups-add-collection-property=The {0$property$} {1$value$} was successfully added to the group {2$group$}
+command-groups-remove-collection-property=The {0$property$} {1$value$} was successfully removed from the group {2$group$}
+command-groups-clear-property=The {0$property$} for the group {1$group$} were cleared successfully
+command-groups-delete-group=The group was successfully deleted
+command-groups-group-already-existing=The group {0$group$} already exists
+command-groups-reload-success=The group configurations have been reloaded
+command-groups-create-success=The group {0$name$} was successfully created
+command-groups-rename-success=The group {0$group$} was successfully renamed to {1$new$}. &cKeep in mind that you might need to change the name in other configurations e.g. tasks
+#
+# Tasks
+#
+cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 22
+#
+# Command Tasks
+#
+command-tasks-description=Administers the configurations of all persistent tasks
+command-tasks-create-task=The empty task was successfully created. Configure it via the command 'tasks' or in the configuration file
+command-tasks-delete-task=The task {0$name$} was successfully deleted
+command-tasks-node-not-found=That node doesn't exist\!
+command-tasks-runtime-not-found=The runtime {0$runtime$} does not exist\!
+command-tasks-inclusion-cache-strategy-not-found=The inclusion cache strategy {0$strategy$} does not exist\!
+command-tasks-reload-success=The ServiceTasks have been reloaded\!
+command-tasks-add-collection-property=The {0$property$} {2$value$} was successfully added to the task {1$task$}
+command-tasks-set-property-success=The {0$property$} of the task {1$task$} was changed to {2$value$}
+command-tasks-remove-collection-property=The {0$property$} {2$value$} was successfully removed from the task {1$task$}
+command-tasks-clear-property=The {0$property$} for the task {1$task$} were cleared successfully
+command-tasks-task-already-existing=The task {0$task$} already exists\!
+command-tasks-task-rename-success=The task {0$task$} was successfully renamed to {1$new$}. &cKeep in mind that you might need to change the name in other configurations e.g. groups
+command-tasks-task-not-found=That task doesn't exist\!
+command-tasks-unknown-host-address-or-alias=The host {0$host$} is neither an assignable host nor an ip alias of the node. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+#
+# Command Tasks (setup)
+#
+command-tasks-setup-create-success=The new task {0$name$} has been successfully created\!
+command-tasks-setup-question-application=Which service version should run on services of this task?
+command-tasks-setup-question-environment=What should be the environment of this task?
+command-tasks-setup-question-javacommand-invalid=The provided executable is not a valid java installation path
+command-tasks-setup-question-javacommand=What is the path to the Java executable?
+command-tasks-setup-question-maintenance=Should the task be in maintenance by default? (this prevents auto starting of the services)
+command-tasks-setup-question-memory=How much memory is each service of the task allowed to use? (in MB)
+command-tasks-setup-question-minservices=How many services of this task should be always online?
+command-tasks-setup-question-name-splitter=What should the name splitter of the new task be?
+command-tasks-setup-question-name=What should the name of the new task be?
+command-tasks-setup-question-startport=What should be the start port of the task?
+command-tasks-setup-question-host-address=What is the host address of the task?
+command-tasks-setup-question-static=Should the services of this task be static that their files are never deleted?
+#
+# Command Template
+#
+command-template-description=Manages local and remote templates
+command-template-copy-failed=Unable to prepare source template for deployment\! Does the source template exists?
+command-template-copy-same-source-and-target=The source and target templates cannot be the same
+command-template-copy-success=Successfully copied the template {0$sourceTemplate$} to the template {1$targetTemplate$}
+command-template-copy=Trying to copy the template {0$sourceTemplate$} to the template {1$targetTemplate$}...
+command-template-create-failed=Failed to prepare the template {0$template$} in the storage {1$storage$}
+command-template-create-success=The template {0$template$} was successfully created and prepared in the storage {1$storage$}
+command-template-create-template-already-exists=The template {0$template$} already exists in the storage {1$storage$}
+command-template-delete-success=The template {0$template$} was successfully removed from the storage {1$storage$}
+command-template-delete-template-not-found=The template {0$template$} doesn''t exist in the storage {1$storage$}
+command-template-invalid-version-type=That version type doesn't exist
+command-template-invalid-version=That version doesn't exist for that version type
+command-template-not-found=The template {0$template$} doesn''t exist
+command-template-not-valid=The given template name is not valid\!
+command-template-storage-not-found=That storage {0$storage$} doesn''t exist
+command-template-environment-not-found=The environment {0$env$} doesn''t exist
+#
+# Command Version
+#
+command-version-description=Manage service versions in templates or on static services
+command-version-static-service-invalid=The given service does not exist (maybe the service was never started before?)
+command-version-install-failed=Unable to install the requested service version\!
+command-version-install-success=The requested service version was successfully installed
+command-version-install-try=Trying to install the requested service version...
+command-version-install-wrong-java=The version {0$version$} is not compatible with your current java version {1$java$}
+#
+# Module Bridge
+#
+module-bridge-command-description=Management for the config of the bridge module
+module-bridge-player-command-description=Management for online and offline cloud players
+module-bridge-tasks-setup-default-fallback=Which fallback task should be used for this proxy? (Use none if you don't want to configure it now)
+module-bridge-plugin-message-sending-failed=Failed to send a message to the {0$channel$} channel
+module-bridge-command-create-entry-success=The bridge configuration entry has been created
+module-bridge-command-entry-already-exists=There already is a configuration entry for this group
+module-bridge-command-players-delete-player=The player {0$name$}\#{1$uniqueId$} will be deleted from the database
+module-bridge-command-players-kick-player-force=Notice that force disconnecting a player is not supported and should not be used when not necessary\!
+module-bridge-command-players-kick-player=The player {0$name$}\#{1$uniqueId$} will be kicked from the network with reason "{2$reason$}"...
+module-bridge-command-players-player-not-online=That player isn't online
+module-bridge-command-players-player-not-registered=That player isn't registered
+module-bridge-command-players-send-player-message=The message will be sent to the player {0$name$}\#{1$uniqueId$}...
+module-bridge-command-players-send-player-server-not-found=That service doesn't exist
+module-bridge-command-players-send-player-server=The player {0$name$}\#{1$uniqueId$} will be sent to the service...
+#
+# Module Cloudflare
+#
+module-cloudflare-create-dns-record-for-service=DNS Entry on domain {0$domain$} was created for service {1$service$} with the id {2$recordId$}
+module-cloudflare-delete-dns-record-for-service=DNS entry was deleted on domain {0$domain$} for service {1$service$} with the id {2$recordId$}
+#
+# Module NPC
+#
+module-npc-command-description=Administration of npc configurations
+module-npc-command-create-entry-success=The npc configuration entry has been created
+module-npc-tasks-setup-generate-default-config=Should the default NPC configuration entry be generated for this task?
+module-npc-command-create-entry-group-already-exists=The npc configuration entry already exists
+#
+# Module Report
+#
+module-report-command-description=Uploads useful data about the node and cluster to a paste server
+module-report-command-paste-failed=Failed to upload the data on {0$url$}
+module-report-command-paste-success=The data has been uploaded on {0$url$}
+module-report-command-service-not-found=The service {0$name$} is not registered
+module-report-command-paste-server-not-found=The paste service {0$name$} is not registered
+#
+# Module Signs
+#
+module-sign-command-description=Administration of sign configurations
+module-sign-command-create-entry-success=The sign configuration entry has been created
+module-sign-tasks-setup-generate-default-config=Should the default signs configuration entry be generated for this task?
+module-sign-command-create-entry-group-already-exists=The sign configuration entry already exists
+#
+# Module SyncProxy
+#
+module-syncproxy-command-description=Administration of all SyncProxy configurations
+module-syncproxy-command-add-whitelist-entry=The entry {0$name$} was added to the {1$group$} configuration whitelist
+module-syncproxy-command-create-entry-group-already-exists=There already is a configuration entry for this group
+module-syncproxy-command-create-entry-success=The SyncProxy configuration entry has been created
+module-syncproxy-command-remove-whitelist-entry=The entry {0$name$} was removed from the {1$group$} configuration whitelist
+module-syncproxy-command-set-maintenance=The maintenance mode of configuration {0$group$} is now {1, choice, 0\#disabled|1\#enabled$maintenance$}
+module-syncproxy-command-set-maxplayers=The player limit of configuration {0$group$} is now {1$count$}
+#
+# Module Smart
+#
+module-smart-command-description=Administration for the smart config of each task
+module-smart-command-task-no-entry=The task {0$task$} has no configured smart entry
+#
+# Module Docker Services
+#
+module-docker-command-description=Administration of the docker module configuration
+module-docker-command-set-success=The property {0$property$} was successfully changed to {1$value$}
+module-docker-command-remove-success=The property {0$property$} was successfully removed
+module-docker-command-add-collection-property=The {0$property$} {1$value$} was successfully added
+module-docker-command-clear-collection-property=The {0$property$} were successfully cleared
+module-docker-command-remove-collection-property=The {0$property$} {1$value$} was successfully removed
+#
+# version installer
+#
+versions-installer-deprecated-version=You are installing an unsupported version\! These versions may contain security vulnerabilities and may not work as expected with CloudNet. Use at your own risk\!

From e9ccbf1ee44178c38836fcfa48c9cfa3acd60150 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 30 Aug 2024 18:21:02 +0200
Subject: [PATCH 02/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index f9e27a8aa0..278a73c7c1 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -48,8 +48,6 @@ client-network-channel-close=Kanal [serverAddress\={0$serverAddress$} clientAddr
 client-network-channel-init=Kanal [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] wurde erfolgreich mit dem Server verbunden
 server-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] wurde geschlossen.
 server-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] wurde verbunden.
-http-listener-bound=Ein HTTP-Listener wurde erfolgreich an die Adresse "{0$address$}" gebunden...
-http-listener-bound-exceptionally=Ein HTTP Listener konnte nicht auf "{0$address$}" gebunden werden\: {1$reason$}
 network-listener-bound=Ein Netzwerk-Listener wurde erfolgreich an die Adresse "{0$address$}" gebunden...
 network-listener-bound-exceptionally=Ein Netzwerk Listener konnte nicht auf "{0$address$}" gebunden werden\: {1$reason$}
 network-selected-transport=Netzwerkkomponenten verwenden {0$transport$} Transport
@@ -268,6 +266,7 @@ command-tasks-create-task=Der leere Task wurde erfolgreich erstellt. Dieser kann
 command-tasks-delete-task=Der Task {0$name$} wurde erfolgreich gelöscht
 command-tasks-node-not-found=Diese Node existiert nicht\!
 command-tasks-runtime-not-found=Die Runtime {0$runtime$} existiert nicht\!
+command-tasks-inclusion-cache-strategy-not-found=The inclusion cache strategy {0$strategy$} does not exist\!
 command-tasks-reload-success=Die Tasks wurden neu geladen\!
 command-tasks-add-collection-property={0$property$} {2$value$} wurde erfolgreich dem Task {1$task$} hinzugefügt
 command-tasks-set-property-success={0$property$} von dem Task {1$task$} wurde zu {2$value$} geändert

From aee99903ecafff3f27fffca4129eaab95b7e7dba Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 30 Aug 2024 18:21:03 +0200
Subject: [PATCH 03/28] New translations en_us.properties (Russian) [ci skip]

---
 node/src/main/resources/lang/ru_RU.properties | 394 ++++++++++++++++++
 1 file changed, 394 insertions(+)
 create mode 100644 node/src/main/resources/lang/ru_RU.properties

diff --git a/node/src/main/resources/lang/ru_RU.properties b/node/src/main/resources/lang/ru_RU.properties
new file mode 100644
index 0000000000..a5aa3ebefc
--- /dev/null
+++ b/node/src/main/resources/lang/ru_RU.properties
@@ -0,0 +1,394 @@
+#
+# Copyright 2019-2024 CloudNetService team & contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+cloudnet-init-eula-not-accepted=If you don't accept the eula, you cannot run a minecraft server\!
+cloudnet-init-eula=Do you agree to the Mojang EULA (https\://aka.ms/MinecraftEULA)?
+cloudnet-init-setup-cluster-cluster-id=What is the id of your cluster? (you can find it in the config.json on of your nodes)
+cloudnet-init-setup-cluster-install=Is this node part of a cluster? (MultiRoot)
+cloudnet-init-setup-cluster-list-nodes=What are the names of your already existing nodes? (separated by ";")
+cloudnet-init-setup-cluster-node-host=What is the host and port of the node "{0$node$}"? (you can find it in the config.json at "listeners")
+cloudnet-init-setup-host-address=On which host should the services be started on? Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+cloudnet-init-setup-internal-host=On which host and port should CloudNet run on? (This is NOT your proxy host/port)
+cloudnet-init-setup-memory=How much memory (in MB) can the services running on this CloudNet node use?
+cloudnet-init-setup-node-id=What should the name of this CloudNet node be?
+cloudnet-init-setup-tasks-javacommand=What is the path to the Java executable?
+cloudnet-init-setup-tasks-proxy-environment=What should be the environment of the proxy?
+cloudnet-init-setup-tasks-proxy-version=Which ServiceVersion should be used on the proxies?
+cloudnet-init-setup-tasks-server-environment=What should be the environment of the services?
+cloudnet-init-setup-tasks-server-version=Which ServiceVersion should be used on the services?
+cloudnet-init-setup-tasks-should-install-proxy=Should a default proxy be created?
+cloudnet-init-setup-tasks-should-install-server=Should a default lobby be created?
+cloudnet-init-setup-web-host=On which host and port should CloudNet's WebServer run?
+cloudnet-init-default-modules=Which default modules should be installed? (separated by a space)
+#
+# Console animations
+#
+ca-question-list-cancel=You can always cancel the process by typing "cancel"\!
+ca-question-list-cancelled=The process has been cancelled\!
+ca-question-list-explain=Use the arrow keys to scroll through all possible values (if there are default values specified). If there is a recommended value available, it is in the command input line by default
+ca-question-list-invalid-default=Please provide a valid value\!
+ca-question-list-possible-answers-list=Possible answers\: {0$values$}
+ca-question-list-question-list=You have to provide one of the following\: {0$values$}
+#
+# Network
+#
+client-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] has closed the connection
+client-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] connected to the server
+server-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was closed
+server-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was connected
+network-listener-bound=Successfully bound a network listener to the address "{0$address$}"...
+network-listener-bound-exceptionally=Unable to bind network listener to "{0$address$}"\: {1$reason$}
+network-selected-transport=Network components are using {0$transport$} transport
+network-selected-dispatch-thread-type=Network dispatchers are using {0$type$} threads
+startup-failed-no-network-listener-bound=Unable to complete startup, no network listener was bound successfully\! CloudNet will stop in 5 seconds
+#
+# Application lifecycle
+#
+start-version-provider=Loaded {0$amount$} service versions...
+start-module-updater=Applying needed updates to installed modules...
+start-commands=Registered commands...
+start-node-connection-try=Trying to connect to node {0$name$}...
+start-node-connection-failure=Unable to connect to node {0$name$}\: {1$reason$}
+start-node-connection-waiting=Waiting for {0$amount$} node connections to establish...
+start-requesting-data=Requesting cluster sync from head node...
+start-connect-database=Using database {0$database$}...
+start-done=Startup done, starting tick loop (Took {0$starttime$}ms)
+stop-application=Stopping application...
+stop-node-connections=Closing connections to all nodes of the cluster...
+stop-providers=Closing providers...
+stop-network-components=Closing network components...
+stop-services=Stopping all running services...
+stop-delete-temp=Deleting temporary files...
+#
+# Services
+#
+cloudnet-service-jar-file-not-found-error=No application file found for CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}]\! Please check the availability of this file. Using the "version" command a version can be installed.
+cloudnet-service-manager-cpu-usage-to-high-error=The CPU load is too high to create a new service\! The system will try to start this service as soon as there are enough resources.
+cloudnet-service-manager-max-memory-error=The maximum allocatable memory has been reached (of CloudNet, other system resources might still be available)\! The limit has to be increased or other services need to be stopped.
+cloudnet-service-networking-connected=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] was successfully connected to the channel [serverAddress\={3$serverAddress$} clientAddress\={4$clientAddress$}]
+cloudnet-service-networking-disconnected=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] was closed by the channel [serverAddress\={3$serverAddress$} clientAddress\={4$clientAddress$}]
+cloudnet-service-post-delete-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been deleted
+cloudnet-service-post-prepared-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been prepared
+cloudnet-service-post-start-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been started
+cloudnet-service-post-stop-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been stopped
+cloudnet-service-post-start-message-different-node=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] is starting on node {3$node$}...
+cloudnet-service-post-stop-message-different-node=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] is stopped on node {3$node$}...
+#
+# Cluster
+#
+cluster-local-db-warning=CloudNet runs in a cluster, but a local embedded database is used\! This can cause big synchronization problems. Please consider switching to a central database (like MongoDB) that all nodes can connect to.
+cluster-server-soft-disconnect=Marking node [uniqueId\={0$id$}] temporarily as disconnected because it was idling for too long\! [lastUpdate\={1$time$}ms ago]
+cluster-server-hard-disconnect=Disconnecting node [uniqueId\={0$id$}] because it did not reconnect within {1$maxDisconnectTime$}ms\! [lastStateChange\={2$time$}ms ago]
+cluster-server-networking-authorization-failed=Authorization unfortunately failed to the node with the address {0$address$}
+cluster-server-networking-disconnected=The connection to the node [uniqueId\={0$id$}] was interrupted\!
+cluster-sync-accept-yours=Using and applying the local version to the cluster...
+cluster-sync-accepted-theirs=Applying the proposed change...
+cluster-sync-change-decision-question=Do you want to [1] accept the changes, [2] apply your version, [3] skip the change?
+cluster-sync-skip=Skipped applying of the current change
+#
+# Modules
+#
+cloudnet-load-modules-invalid-checksum=The checksum of the module {0$module$} does not match, aborting update
+cloudnet-install-modules-invalid-checksum=The checksum of the module {0$module$} does not match, aborting installation
+cloudnet-post-load-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was successfully loaded
+cloudnet-post-reload-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was reloaded successfully
+cloudnet-post-start-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was started successfully
+cloudnet-post-stop-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was stopped successfully
+cloudnet-post-unload-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was removed successfully
+#
+# Commands
+#
+command-no-description=No command description provided
+command-confirmation-no-requests=There are no commands to confirm
+command-confirmation-required=Please confirm executing the command by executing '&bconfirm&r' within 30s
+invalid-command-sender=This command cannot be executed by ''{0$source$}''
+invalid-command-syntax=Invalid syntax\! Use {0$syntax$}
+no-such-command=Command could not be found\! For help, use the command "help"
+argument-parse-failure-no-input-was-provided=No input provided
+argument-parse-failure-boolean=The given input {0$input$} is not a boolean
+argument-parse-failure-number=The given input {0$input$} is not a number
+argument-parse-failure-char=The given input {0$input$} is not a char
+argument-parse-failure-string=The given input {0$input$} is not a string
+argument-parse-failure-uuid=The given input {0$input$} is not an uuid
+argument-parse-failure-enum=The given input enum {0$input$} is not one of the following {1$values$}
+argument-parse-failure-regex=The given input &b{1$input$}&r does not match &b{0$regex$}
+argument-parse-failure-duration=The given input {0$input$} is not a duration
+argument-parse-failure-flag-unknown=The given flag {0$flag$} is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag {0$flag$} can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag {0$flag$}
+argument-parse-failure-flag-no-permission=You are not allowed to use this flag
+missing-command-permission=You are not allowed to execute this sub command
+#
+# General commands
+#
+command-general-group-does-not-exist=That group doesn't exist\!
+command-any-host-and-port-invalid=The given input {0$input$} is not a valid host and port. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+command-assignable-host-invalid=The given input {0$input$} is not an assignable host. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+command-any-host-invalid=The given input {0$input$} is not a valid host address. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+#
+# Command Help
+#
+commnad-help-description=Shows all commands and their description
+command-help-docs=Follow this url {0$url$} to get to the documentation for the {1$command$} command
+command-help-docs-no-url=The {0$command$} command has no documentation url
+#
+# Command Me
+#
+command-me-description=Displays all important information about this node and the running jvm
+#
+# Command clear
+#
+command-clear-description=Clears the entire console of the node to get a better overview
+#
+# Command Cluster
+#
+command-cluster-description=Manages the cluster and provides information about it
+command-cluster-add-node-success=Registered the new node ({0$name$}) to the cluster configuration
+command-cluster-node-not-found=That node doesn't exist
+command-cluster-node-set-drain=Draining is now {0, choice, 0\#disabled|1\#enabled$drain$} for node {1$node$}
+command-cluster-push-static-service-failed=Failed to deploy the static service to the cluster
+command-cluster-push-static-service-not-found=The static service was not found
+command-cluster-push-static-service-running=The static service is running. Stop the service to deploy it into the cluster
+command-cluster-push-static-service-starting=Starting the deployment of the static service...
+command-cluster-push-static-service-success=Successfully deployed the static service into the cluster
+command-cluster-push-static-service-existing=The received static service {0$service$} already exists, aborting deployment
+command-cluster-push-static-service-received-success=Successfully received the deployed static service {0$service$}
+command-cluster-push-static-service-running-remote=The received static service {0$service$} is running, aborting deployment
+command-cluster-push-template-compress=Compressing the template {0$template$}...
+command-cluster-push-template-failed=Failed to send the local template {0$template$} to the cluster
+command-cluster-push-template-success=The local template {0$template$} was successfully sent to all nodes
+command-cluster-remove-node-success=The node {0$node$} has been removed successfully
+command-cluster-start-sync=The cluster sync starts now
+#
+# Command Service
+#
+command-service-description=Manages all services in the cluster
+command-service-copy-no-default-template=The service you provided does not have a default template, use "copy {0$name$} template\=storage\:prefix/name" to provide a template you would like to copy to
+command-service-copy-success=The service {0$name$} was successfully copied to the template {1$template$}
+command-service-add-deployment-success=The deployment {0$deployment$} was successfully added to the waiting deployments
+command-service-deploy-deployment-success=The resources of the service were successfully deployed
+command-service-add-inclusion-success=The inclusion {0$inclusion$} was successfully added to the waiting integrations
+command-service-include-inclusion-success=All waiting inclusions were downloaded and installed to the service
+command-service-add-template-success=The template {0$template$} was successfully found and was added to the waiting templates
+command-service-include-templates-success=All waiting templates were copied to the service
+command-service-service-not-found=That service doesn't exist
+command-service-toggle-disabled=Disabled the automatic console logging for {0$service$}
+command-service-toggle-enabled=Enabled the automatic console logging for {0$service$}
+#
+# Command Create
+#
+command-create-description=Creates one or more new services based on a task or completely independent
+command-create-by-task-starting=Starting to create {1$amount$} services for {0$task$}
+command-create-by-task-failed=The services couldn't be created
+command-create-by-task-success=The services were created based on the task. They can be managed with the 'service' command
+#
+# Command Debug
+#
+command-debug-description=Toggle the global debug mode
+#
+# Command exit
+#
+command-exit-description=Stops the program and all managed subprocesses
+#
+# Command Migrate
+#
+command-migrate-description=Allows to migrate data known to CloudNet between different storages
+command-migrate-current-database=Migration of {0$db$} in progress...
+command-migrate-database-connection-failed=The connection to the database failed
+command-migrate-source-equals-target=Migrating data to the same database is not possible
+command-migrate-success=Migrating {0$source$} to {1$target$} was successful
+command-migrate-unknown-database-provider=This database type does not exist
+#
+# Command Modules
+#
+command-modules-description=Manages installed modules and allows to load local or install remote modules
+command-modules-install-missing-depend=The module {0$module$} requires these dependencies to run\: {1$dependencies$}
+command-modules-module-already-loaded=The module {0$module$} is already loaded
+command-modules-module-file-not-found=The file {0$path$} does not exist
+command-modules-module-not-a-file={0$path$} is not a file
+command-modules-module-installed=The module {0$module$} was successfully installed
+command-module-skipping-checksum-fail=The checksum of the official module {0$module$} did not match but the validation was skipped\!
+command-modules-checksum-validation-skippable=The module checksum of the official module {0$module$} did not match\! (most likely your module definition is outdated, restart CloudNet to auto update them) You can install the module by appending "--ncv" to the command (\! could lead to problems \!)
+command-modules-module-not-loaded=The module {0$module$} is not loaded
+command-modules-module-not-started=The module {0$module$} is not started
+command-modules-module-not-stopped=The module {0$module$} is not stopped
+command-modules-module-runtime-module=The module {0$module$} is not reloadable as it is a runtime module
+command-modules-no-such-installable-module=There is no module named {0$name$}
+command-modules-module-already-installed=The module {0$name$} is already installed. Updates of modules are performed automatically when CloudNet is restarted
+command-modules-module-uninstall=The module {0$module$} was successfully uninstalled
+command-modules-module-uninstall-failed=The module {0$module$} could not be uninstalled. Check the console log for further information
+#
+# Command Config
+#
+command-config-description=Administration of the cloudnet node configuration
+command-config-node-ip-alias-already-existing=The ip alias {0$alias$} already exists
+command-config-node-ip-alias-added=The host address {1$address$} aliased as {0$alias$} was added successfully
+command-config-node-ip-alias-remove=The ip alias {0$alias$} was removed
+command-config-node-add-ip-whitelist=The ip {0$ip$} was added to the ip whitelist
+command-config-node-remove-ip-whitelist=The ip address {0$ip$} was removed from the ip whitelist
+command-config-node-set-max-memory=The maximum memory for the node is now set to {0$memory$}
+command-config-node-set-java-command=The default java command for services is now set to {0$path$} using Java version {1$version$}
+command-config-node-reload-config=The node configuration was reloaded. Note\: Not all changes are applied without a restart
+command-config-reload-config=Reloaded the node, task, group and permission configurations. Note\: Not all changes are applied without a restart
+#
+# Command Groups
+#
+command-groups-description=Administers the configurations of all persistent groups
+command-groups-add-collection-property=The {0$property$} {1$value$} was successfully added to the group {2$group$}
+command-groups-remove-collection-property=The {0$property$} {1$value$} was successfully removed from the group {2$group$}
+command-groups-clear-property=The {0$property$} for the group {1$group$} were cleared successfully
+command-groups-delete-group=The group was successfully deleted
+command-groups-group-already-existing=The group {0$group$} already exists
+command-groups-reload-success=The group configurations have been reloaded
+command-groups-create-success=The group {0$name$} was successfully created
+command-groups-rename-success=The group {0$group$} was successfully renamed to {1$new$}. &cKeep in mind that you might need to change the name in other configurations e.g. tasks
+#
+# Tasks
+#
+cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 22
+#
+# Command Tasks
+#
+command-tasks-description=Administers the configurations of all persistent tasks
+command-tasks-create-task=The empty task was successfully created. Configure it via the command 'tasks' or in the configuration file
+command-tasks-delete-task=The task {0$name$} was successfully deleted
+command-tasks-node-not-found=That node doesn't exist\!
+command-tasks-runtime-not-found=The runtime {0$runtime$} does not exist\!
+command-tasks-inclusion-cache-strategy-not-found=The inclusion cache strategy {0$strategy$} does not exist\!
+command-tasks-reload-success=The ServiceTasks have been reloaded\!
+command-tasks-add-collection-property=The {0$property$} {2$value$} was successfully added to the task {1$task$}
+command-tasks-set-property-success=The {0$property$} of the task {1$task$} was changed to {2$value$}
+command-tasks-remove-collection-property=The {0$property$} {2$value$} was successfully removed from the task {1$task$}
+command-tasks-clear-property=The {0$property$} for the task {1$task$} were cleared successfully
+command-tasks-task-already-existing=The task {0$task$} already exists\!
+command-tasks-task-rename-success=The task {0$task$} was successfully renamed to {1$new$}. &cKeep in mind that you might need to change the name in other configurations e.g. groups
+command-tasks-task-not-found=That task doesn't exist\!
+command-tasks-unknown-host-address-or-alias=The host {0$host$} is neither an assignable host nor an ip alias of the node. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+#
+# Command Tasks (setup)
+#
+command-tasks-setup-create-success=The new task {0$name$} has been successfully created\!
+command-tasks-setup-question-application=Which service version should run on services of this task?
+command-tasks-setup-question-environment=What should be the environment of this task?
+command-tasks-setup-question-javacommand-invalid=The provided executable is not a valid java installation path
+command-tasks-setup-question-javacommand=What is the path to the Java executable?
+command-tasks-setup-question-maintenance=Should the task be in maintenance by default? (this prevents auto starting of the services)
+command-tasks-setup-question-memory=How much memory is each service of the task allowed to use? (in MB)
+command-tasks-setup-question-minservices=How many services of this task should be always online?
+command-tasks-setup-question-name-splitter=What should the name splitter of the new task be?
+command-tasks-setup-question-name=What should the name of the new task be?
+command-tasks-setup-question-startport=What should be the start port of the task?
+command-tasks-setup-question-host-address=What is the host address of the task?
+command-tasks-setup-question-static=Should the services of this task be static that their files are never deleted?
+#
+# Command Template
+#
+command-template-description=Manages local and remote templates
+command-template-copy-failed=Unable to prepare source template for deployment\! Does the source template exists?
+command-template-copy-same-source-and-target=The source and target templates cannot be the same
+command-template-copy-success=Successfully copied the template {0$sourceTemplate$} to the template {1$targetTemplate$}
+command-template-copy=Trying to copy the template {0$sourceTemplate$} to the template {1$targetTemplate$}...
+command-template-create-failed=Failed to prepare the template {0$template$} in the storage {1$storage$}
+command-template-create-success=The template {0$template$} was successfully created and prepared in the storage {1$storage$}
+command-template-create-template-already-exists=The template {0$template$} already exists in the storage {1$storage$}
+command-template-delete-success=The template {0$template$} was successfully removed from the storage {1$storage$}
+command-template-delete-template-not-found=The template {0$template$} doesn''t exist in the storage {1$storage$}
+command-template-invalid-version-type=That version type doesn't exist
+command-template-invalid-version=That version doesn't exist for that version type
+command-template-not-found=The template {0$template$} doesn''t exist
+command-template-not-valid=The given template name is not valid\!
+command-template-storage-not-found=That storage {0$storage$} doesn''t exist
+command-template-environment-not-found=The environment {0$env$} doesn''t exist
+#
+# Command Version
+#
+command-version-description=Manage service versions in templates or on static services
+command-version-static-service-invalid=The given service does not exist (maybe the service was never started before?)
+command-version-install-failed=Unable to install the requested service version\!
+command-version-install-success=The requested service version was successfully installed
+command-version-install-try=Trying to install the requested service version...
+command-version-install-wrong-java=The version {0$version$} is not compatible with your current java version {1$java$}
+#
+# Module Bridge
+#
+module-bridge-command-description=Management for the config of the bridge module
+module-bridge-player-command-description=Management for online and offline cloud players
+module-bridge-tasks-setup-default-fallback=Which fallback task should be used for this proxy? (Use none if you don't want to configure it now)
+module-bridge-plugin-message-sending-failed=Failed to send a message to the {0$channel$} channel
+module-bridge-command-create-entry-success=The bridge configuration entry has been created
+module-bridge-command-entry-already-exists=There already is a configuration entry for this group
+module-bridge-command-players-delete-player=The player {0$name$}\#{1$uniqueId$} will be deleted from the database
+module-bridge-command-players-kick-player-force=Notice that force disconnecting a player is not supported and should not be used when not necessary\!
+module-bridge-command-players-kick-player=The player {0$name$}\#{1$uniqueId$} will be kicked from the network with reason "{2$reason$}"...
+module-bridge-command-players-player-not-online=That player isn't online
+module-bridge-command-players-player-not-registered=That player isn't registered
+module-bridge-command-players-send-player-message=The message will be sent to the player {0$name$}\#{1$uniqueId$}...
+module-bridge-command-players-send-player-server-not-found=That service doesn't exist
+module-bridge-command-players-send-player-server=The player {0$name$}\#{1$uniqueId$} will be sent to the service...
+#
+# Module Cloudflare
+#
+module-cloudflare-create-dns-record-for-service=DNS Entry on domain {0$domain$} was created for service {1$service$} with the id {2$recordId$}
+module-cloudflare-delete-dns-record-for-service=DNS entry was deleted on domain {0$domain$} for service {1$service$} with the id {2$recordId$}
+#
+# Module NPC
+#
+module-npc-command-description=Administration of npc configurations
+module-npc-command-create-entry-success=The npc configuration entry has been created
+module-npc-tasks-setup-generate-default-config=Should the default NPC configuration entry be generated for this task?
+module-npc-command-create-entry-group-already-exists=The npc configuration entry already exists
+#
+# Module Report
+#
+module-report-command-description=Uploads useful data about the node and cluster to a paste server
+module-report-command-paste-failed=Failed to upload the data on {0$url$}
+module-report-command-paste-success=The data has been uploaded on {0$url$}
+module-report-command-service-not-found=The service {0$name$} is not registered
+module-report-command-paste-server-not-found=The paste service {0$name$} is not registered
+#
+# Module Signs
+#
+module-sign-command-description=Administration of sign configurations
+module-sign-command-create-entry-success=The sign configuration entry has been created
+module-sign-tasks-setup-generate-default-config=Should the default signs configuration entry be generated for this task?
+module-sign-command-create-entry-group-already-exists=The sign configuration entry already exists
+#
+# Module SyncProxy
+#
+module-syncproxy-command-description=Administration of all SyncProxy configurations
+module-syncproxy-command-add-whitelist-entry=The entry {0$name$} was added to the {1$group$} configuration whitelist
+module-syncproxy-command-create-entry-group-already-exists=There already is a configuration entry for this group
+module-syncproxy-command-create-entry-success=The SyncProxy configuration entry has been created
+module-syncproxy-command-remove-whitelist-entry=The entry {0$name$} was removed from the {1$group$} configuration whitelist
+module-syncproxy-command-set-maintenance=The maintenance mode of configuration {0$group$} is now {1, choice, 0\#disabled|1\#enabled$maintenance$}
+module-syncproxy-command-set-maxplayers=The player limit of configuration {0$group$} is now {1$count$}
+#
+# Module Smart
+#
+module-smart-command-description=Administration for the smart config of each task
+module-smart-command-task-no-entry=The task {0$task$} has no configured smart entry
+#
+# Module Docker Services
+#
+module-docker-command-description=Administration of the docker module configuration
+module-docker-command-set-success=The property {0$property$} was successfully changed to {1$value$}
+module-docker-command-remove-success=The property {0$property$} was successfully removed
+module-docker-command-add-collection-property=The {0$property$} {1$value$} was successfully added
+module-docker-command-clear-collection-property=The {0$property$} were successfully cleared
+module-docker-command-remove-collection-property=The {0$property$} {1$value$} was successfully removed
+#
+# version installer
+#
+versions-installer-deprecated-version=You are installing an unsupported version\! These versions may contain security vulnerabilities and may not work as expected with CloudNet. Use at your own risk\!

From ceb1b00ea6cb18a0d7c4496b6f0960b8c6fb8915 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 30 Aug 2024 18:21:03 +0200
Subject: [PATCH 04/28] New translations en_us.properties (Luxembourgish) [ci
 skip]

---
 node/src/main/resources/lang/lb_LU.properties | 394 ++++++++++++++++++
 1 file changed, 394 insertions(+)
 create mode 100644 node/src/main/resources/lang/lb_LU.properties

diff --git a/node/src/main/resources/lang/lb_LU.properties b/node/src/main/resources/lang/lb_LU.properties
new file mode 100644
index 0000000000..a5aa3ebefc
--- /dev/null
+++ b/node/src/main/resources/lang/lb_LU.properties
@@ -0,0 +1,394 @@
+#
+# Copyright 2019-2024 CloudNetService team & contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+cloudnet-init-eula-not-accepted=If you don't accept the eula, you cannot run a minecraft server\!
+cloudnet-init-eula=Do you agree to the Mojang EULA (https\://aka.ms/MinecraftEULA)?
+cloudnet-init-setup-cluster-cluster-id=What is the id of your cluster? (you can find it in the config.json on of your nodes)
+cloudnet-init-setup-cluster-install=Is this node part of a cluster? (MultiRoot)
+cloudnet-init-setup-cluster-list-nodes=What are the names of your already existing nodes? (separated by ";")
+cloudnet-init-setup-cluster-node-host=What is the host and port of the node "{0$node$}"? (you can find it in the config.json at "listeners")
+cloudnet-init-setup-host-address=On which host should the services be started on? Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+cloudnet-init-setup-internal-host=On which host and port should CloudNet run on? (This is NOT your proxy host/port)
+cloudnet-init-setup-memory=How much memory (in MB) can the services running on this CloudNet node use?
+cloudnet-init-setup-node-id=What should the name of this CloudNet node be?
+cloudnet-init-setup-tasks-javacommand=What is the path to the Java executable?
+cloudnet-init-setup-tasks-proxy-environment=What should be the environment of the proxy?
+cloudnet-init-setup-tasks-proxy-version=Which ServiceVersion should be used on the proxies?
+cloudnet-init-setup-tasks-server-environment=What should be the environment of the services?
+cloudnet-init-setup-tasks-server-version=Which ServiceVersion should be used on the services?
+cloudnet-init-setup-tasks-should-install-proxy=Should a default proxy be created?
+cloudnet-init-setup-tasks-should-install-server=Should a default lobby be created?
+cloudnet-init-setup-web-host=On which host and port should CloudNet's WebServer run?
+cloudnet-init-default-modules=Which default modules should be installed? (separated by a space)
+#
+# Console animations
+#
+ca-question-list-cancel=You can always cancel the process by typing "cancel"\!
+ca-question-list-cancelled=The process has been cancelled\!
+ca-question-list-explain=Use the arrow keys to scroll through all possible values (if there are default values specified). If there is a recommended value available, it is in the command input line by default
+ca-question-list-invalid-default=Please provide a valid value\!
+ca-question-list-possible-answers-list=Possible answers\: {0$values$}
+ca-question-list-question-list=You have to provide one of the following\: {0$values$}
+#
+# Network
+#
+client-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] has closed the connection
+client-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] connected to the server
+server-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was closed
+server-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was connected
+network-listener-bound=Successfully bound a network listener to the address "{0$address$}"...
+network-listener-bound-exceptionally=Unable to bind network listener to "{0$address$}"\: {1$reason$}
+network-selected-transport=Network components are using {0$transport$} transport
+network-selected-dispatch-thread-type=Network dispatchers are using {0$type$} threads
+startup-failed-no-network-listener-bound=Unable to complete startup, no network listener was bound successfully\! CloudNet will stop in 5 seconds
+#
+# Application lifecycle
+#
+start-version-provider=Loaded {0$amount$} service versions...
+start-module-updater=Applying needed updates to installed modules...
+start-commands=Registered commands...
+start-node-connection-try=Trying to connect to node {0$name$}...
+start-node-connection-failure=Unable to connect to node {0$name$}\: {1$reason$}
+start-node-connection-waiting=Waiting for {0$amount$} node connections to establish...
+start-requesting-data=Requesting cluster sync from head node...
+start-connect-database=Using database {0$database$}...
+start-done=Startup done, starting tick loop (Took {0$starttime$}ms)
+stop-application=Stopping application...
+stop-node-connections=Closing connections to all nodes of the cluster...
+stop-providers=Closing providers...
+stop-network-components=Closing network components...
+stop-services=Stopping all running services...
+stop-delete-temp=Deleting temporary files...
+#
+# Services
+#
+cloudnet-service-jar-file-not-found-error=No application file found for CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}]\! Please check the availability of this file. Using the "version" command a version can be installed.
+cloudnet-service-manager-cpu-usage-to-high-error=The CPU load is too high to create a new service\! The system will try to start this service as soon as there are enough resources.
+cloudnet-service-manager-max-memory-error=The maximum allocatable memory has been reached (of CloudNet, other system resources might still be available)\! The limit has to be increased or other services need to be stopped.
+cloudnet-service-networking-connected=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] was successfully connected to the channel [serverAddress\={3$serverAddress$} clientAddress\={4$clientAddress$}]
+cloudnet-service-networking-disconnected=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] was closed by the channel [serverAddress\={3$serverAddress$} clientAddress\={4$clientAddress$}]
+cloudnet-service-post-delete-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been deleted
+cloudnet-service-post-prepared-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been prepared
+cloudnet-service-post-start-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been started
+cloudnet-service-post-stop-message=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] has been stopped
+cloudnet-service-post-start-message-different-node=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] is starting on node {3$node$}...
+cloudnet-service-post-stop-message-different-node=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] is stopped on node {3$node$}...
+#
+# Cluster
+#
+cluster-local-db-warning=CloudNet runs in a cluster, but a local embedded database is used\! This can cause big synchronization problems. Please consider switching to a central database (like MongoDB) that all nodes can connect to.
+cluster-server-soft-disconnect=Marking node [uniqueId\={0$id$}] temporarily as disconnected because it was idling for too long\! [lastUpdate\={1$time$}ms ago]
+cluster-server-hard-disconnect=Disconnecting node [uniqueId\={0$id$}] because it did not reconnect within {1$maxDisconnectTime$}ms\! [lastStateChange\={2$time$}ms ago]
+cluster-server-networking-authorization-failed=Authorization unfortunately failed to the node with the address {0$address$}
+cluster-server-networking-disconnected=The connection to the node [uniqueId\={0$id$}] was interrupted\!
+cluster-sync-accept-yours=Using and applying the local version to the cluster...
+cluster-sync-accepted-theirs=Applying the proposed change...
+cluster-sync-change-decision-question=Do you want to [1] accept the changes, [2] apply your version, [3] skip the change?
+cluster-sync-skip=Skipped applying of the current change
+#
+# Modules
+#
+cloudnet-load-modules-invalid-checksum=The checksum of the module {0$module$} does not match, aborting update
+cloudnet-install-modules-invalid-checksum=The checksum of the module {0$module$} does not match, aborting installation
+cloudnet-post-load-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was successfully loaded
+cloudnet-post-reload-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was reloaded successfully
+cloudnet-post-start-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was started successfully
+cloudnet-post-stop-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was stopped successfully
+cloudnet-post-unload-module=Module {0$module_group$}\:{1$module_name$}\:{2$module_version$} was removed successfully
+#
+# Commands
+#
+command-no-description=No command description provided
+command-confirmation-no-requests=There are no commands to confirm
+command-confirmation-required=Please confirm executing the command by executing '&bconfirm&r' within 30s
+invalid-command-sender=This command cannot be executed by ''{0$source$}''
+invalid-command-syntax=Invalid syntax\! Use {0$syntax$}
+no-such-command=Command could not be found\! For help, use the command "help"
+argument-parse-failure-no-input-was-provided=No input provided
+argument-parse-failure-boolean=The given input {0$input$} is not a boolean
+argument-parse-failure-number=The given input {0$input$} is not a number
+argument-parse-failure-char=The given input {0$input$} is not a char
+argument-parse-failure-string=The given input {0$input$} is not a string
+argument-parse-failure-uuid=The given input {0$input$} is not an uuid
+argument-parse-failure-enum=The given input enum {0$input$} is not one of the following {1$values$}
+argument-parse-failure-regex=The given input &b{1$input$}&r does not match &b{0$regex$}
+argument-parse-failure-duration=The given input {0$input$} is not a duration
+argument-parse-failure-flag-unknown=The given flag {0$flag$} is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag {0$flag$} can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag {0$flag$}
+argument-parse-failure-flag-no-permission=You are not allowed to use this flag
+missing-command-permission=You are not allowed to execute this sub command
+#
+# General commands
+#
+command-general-group-does-not-exist=That group doesn't exist\!
+command-any-host-and-port-invalid=The given input {0$input$} is not a valid host and port. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+command-assignable-host-invalid=The given input {0$input$} is not an assignable host. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+command-any-host-invalid=The given input {0$input$} is not a valid host address. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+#
+# Command Help
+#
+commnad-help-description=Shows all commands and their description
+command-help-docs=Follow this url {0$url$} to get to the documentation for the {1$command$} command
+command-help-docs-no-url=The {0$command$} command has no documentation url
+#
+# Command Me
+#
+command-me-description=Displays all important information about this node and the running jvm
+#
+# Command clear
+#
+command-clear-description=Clears the entire console of the node to get a better overview
+#
+# Command Cluster
+#
+command-cluster-description=Manages the cluster and provides information about it
+command-cluster-add-node-success=Registered the new node ({0$name$}) to the cluster configuration
+command-cluster-node-not-found=That node doesn't exist
+command-cluster-node-set-drain=Draining is now {0, choice, 0\#disabled|1\#enabled$drain$} for node {1$node$}
+command-cluster-push-static-service-failed=Failed to deploy the static service to the cluster
+command-cluster-push-static-service-not-found=The static service was not found
+command-cluster-push-static-service-running=The static service is running. Stop the service to deploy it into the cluster
+command-cluster-push-static-service-starting=Starting the deployment of the static service...
+command-cluster-push-static-service-success=Successfully deployed the static service into the cluster
+command-cluster-push-static-service-existing=The received static service {0$service$} already exists, aborting deployment
+command-cluster-push-static-service-received-success=Successfully received the deployed static service {0$service$}
+command-cluster-push-static-service-running-remote=The received static service {0$service$} is running, aborting deployment
+command-cluster-push-template-compress=Compressing the template {0$template$}...
+command-cluster-push-template-failed=Failed to send the local template {0$template$} to the cluster
+command-cluster-push-template-success=The local template {0$template$} was successfully sent to all nodes
+command-cluster-remove-node-success=The node {0$node$} has been removed successfully
+command-cluster-start-sync=The cluster sync starts now
+#
+# Command Service
+#
+command-service-description=Manages all services in the cluster
+command-service-copy-no-default-template=The service you provided does not have a default template, use "copy {0$name$} template\=storage\:prefix/name" to provide a template you would like to copy to
+command-service-copy-success=The service {0$name$} was successfully copied to the template {1$template$}
+command-service-add-deployment-success=The deployment {0$deployment$} was successfully added to the waiting deployments
+command-service-deploy-deployment-success=The resources of the service were successfully deployed
+command-service-add-inclusion-success=The inclusion {0$inclusion$} was successfully added to the waiting integrations
+command-service-include-inclusion-success=All waiting inclusions were downloaded and installed to the service
+command-service-add-template-success=The template {0$template$} was successfully found and was added to the waiting templates
+command-service-include-templates-success=All waiting templates were copied to the service
+command-service-service-not-found=That service doesn't exist
+command-service-toggle-disabled=Disabled the automatic console logging for {0$service$}
+command-service-toggle-enabled=Enabled the automatic console logging for {0$service$}
+#
+# Command Create
+#
+command-create-description=Creates one or more new services based on a task or completely independent
+command-create-by-task-starting=Starting to create {1$amount$} services for {0$task$}
+command-create-by-task-failed=The services couldn't be created
+command-create-by-task-success=The services were created based on the task. They can be managed with the 'service' command
+#
+# Command Debug
+#
+command-debug-description=Toggle the global debug mode
+#
+# Command exit
+#
+command-exit-description=Stops the program and all managed subprocesses
+#
+# Command Migrate
+#
+command-migrate-description=Allows to migrate data known to CloudNet between different storages
+command-migrate-current-database=Migration of {0$db$} in progress...
+command-migrate-database-connection-failed=The connection to the database failed
+command-migrate-source-equals-target=Migrating data to the same database is not possible
+command-migrate-success=Migrating {0$source$} to {1$target$} was successful
+command-migrate-unknown-database-provider=This database type does not exist
+#
+# Command Modules
+#
+command-modules-description=Manages installed modules and allows to load local or install remote modules
+command-modules-install-missing-depend=The module {0$module$} requires these dependencies to run\: {1$dependencies$}
+command-modules-module-already-loaded=The module {0$module$} is already loaded
+command-modules-module-file-not-found=The file {0$path$} does not exist
+command-modules-module-not-a-file={0$path$} is not a file
+command-modules-module-installed=The module {0$module$} was successfully installed
+command-module-skipping-checksum-fail=The checksum of the official module {0$module$} did not match but the validation was skipped\!
+command-modules-checksum-validation-skippable=The module checksum of the official module {0$module$} did not match\! (most likely your module definition is outdated, restart CloudNet to auto update them) You can install the module by appending "--ncv" to the command (\! could lead to problems \!)
+command-modules-module-not-loaded=The module {0$module$} is not loaded
+command-modules-module-not-started=The module {0$module$} is not started
+command-modules-module-not-stopped=The module {0$module$} is not stopped
+command-modules-module-runtime-module=The module {0$module$} is not reloadable as it is a runtime module
+command-modules-no-such-installable-module=There is no module named {0$name$}
+command-modules-module-already-installed=The module {0$name$} is already installed. Updates of modules are performed automatically when CloudNet is restarted
+command-modules-module-uninstall=The module {0$module$} was successfully uninstalled
+command-modules-module-uninstall-failed=The module {0$module$} could not be uninstalled. Check the console log for further information
+#
+# Command Config
+#
+command-config-description=Administration of the cloudnet node configuration
+command-config-node-ip-alias-already-existing=The ip alias {0$alias$} already exists
+command-config-node-ip-alias-added=The host address {1$address$} aliased as {0$alias$} was added successfully
+command-config-node-ip-alias-remove=The ip alias {0$alias$} was removed
+command-config-node-add-ip-whitelist=The ip {0$ip$} was added to the ip whitelist
+command-config-node-remove-ip-whitelist=The ip address {0$ip$} was removed from the ip whitelist
+command-config-node-set-max-memory=The maximum memory for the node is now set to {0$memory$}
+command-config-node-set-java-command=The default java command for services is now set to {0$path$} using Java version {1$version$}
+command-config-node-reload-config=The node configuration was reloaded. Note\: Not all changes are applied without a restart
+command-config-reload-config=Reloaded the node, task, group and permission configurations. Note\: Not all changes are applied without a restart
+#
+# Command Groups
+#
+command-groups-description=Administers the configurations of all persistent groups
+command-groups-add-collection-property=The {0$property$} {1$value$} was successfully added to the group {2$group$}
+command-groups-remove-collection-property=The {0$property$} {1$value$} was successfully removed from the group {2$group$}
+command-groups-clear-property=The {0$property$} for the group {1$group$} were cleared successfully
+command-groups-delete-group=The group was successfully deleted
+command-groups-group-already-existing=The group {0$group$} already exists
+command-groups-reload-success=The group configurations have been reloaded
+command-groups-create-success=The group {0$name$} was successfully created
+command-groups-rename-success=The group {0$group$} was successfully renamed to {1$new$}. &cKeep in mind that you might need to change the name in other configurations e.g. tasks
+#
+# Tasks
+#
+cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 22
+#
+# Command Tasks
+#
+command-tasks-description=Administers the configurations of all persistent tasks
+command-tasks-create-task=The empty task was successfully created. Configure it via the command 'tasks' or in the configuration file
+command-tasks-delete-task=The task {0$name$} was successfully deleted
+command-tasks-node-not-found=That node doesn't exist\!
+command-tasks-runtime-not-found=The runtime {0$runtime$} does not exist\!
+command-tasks-inclusion-cache-strategy-not-found=The inclusion cache strategy {0$strategy$} does not exist\!
+command-tasks-reload-success=The ServiceTasks have been reloaded\!
+command-tasks-add-collection-property=The {0$property$} {2$value$} was successfully added to the task {1$task$}
+command-tasks-set-property-success=The {0$property$} of the task {1$task$} was changed to {2$value$}
+command-tasks-remove-collection-property=The {0$property$} {2$value$} was successfully removed from the task {1$task$}
+command-tasks-clear-property=The {0$property$} for the task {1$task$} were cleared successfully
+command-tasks-task-already-existing=The task {0$task$} already exists\!
+command-tasks-task-rename-success=The task {0$task$} was successfully renamed to {1$new$}. &cKeep in mind that you might need to change the name in other configurations e.g. groups
+command-tasks-task-not-found=That task doesn't exist\!
+command-tasks-unknown-host-address-or-alias=The host {0$host$} is neither an assignable host nor an ip alias of the node. Note\: Wildcard addresses (like 0.0.0.0) are not allowed
+#
+# Command Tasks (setup)
+#
+command-tasks-setup-create-success=The new task {0$name$} has been successfully created\!
+command-tasks-setup-question-application=Which service version should run on services of this task?
+command-tasks-setup-question-environment=What should be the environment of this task?
+command-tasks-setup-question-javacommand-invalid=The provided executable is not a valid java installation path
+command-tasks-setup-question-javacommand=What is the path to the Java executable?
+command-tasks-setup-question-maintenance=Should the task be in maintenance by default? (this prevents auto starting of the services)
+command-tasks-setup-question-memory=How much memory is each service of the task allowed to use? (in MB)
+command-tasks-setup-question-minservices=How many services of this task should be always online?
+command-tasks-setup-question-name-splitter=What should the name splitter of the new task be?
+command-tasks-setup-question-name=What should the name of the new task be?
+command-tasks-setup-question-startport=What should be the start port of the task?
+command-tasks-setup-question-host-address=What is the host address of the task?
+command-tasks-setup-question-static=Should the services of this task be static that their files are never deleted?
+#
+# Command Template
+#
+command-template-description=Manages local and remote templates
+command-template-copy-failed=Unable to prepare source template for deployment\! Does the source template exists?
+command-template-copy-same-source-and-target=The source and target templates cannot be the same
+command-template-copy-success=Successfully copied the template {0$sourceTemplate$} to the template {1$targetTemplate$}
+command-template-copy=Trying to copy the template {0$sourceTemplate$} to the template {1$targetTemplate$}...
+command-template-create-failed=Failed to prepare the template {0$template$} in the storage {1$storage$}
+command-template-create-success=The template {0$template$} was successfully created and prepared in the storage {1$storage$}
+command-template-create-template-already-exists=The template {0$template$} already exists in the storage {1$storage$}
+command-template-delete-success=The template {0$template$} was successfully removed from the storage {1$storage$}
+command-template-delete-template-not-found=The template {0$template$} doesn''t exist in the storage {1$storage$}
+command-template-invalid-version-type=That version type doesn't exist
+command-template-invalid-version=That version doesn't exist for that version type
+command-template-not-found=The template {0$template$} doesn''t exist
+command-template-not-valid=The given template name is not valid\!
+command-template-storage-not-found=That storage {0$storage$} doesn''t exist
+command-template-environment-not-found=The environment {0$env$} doesn''t exist
+#
+# Command Version
+#
+command-version-description=Manage service versions in templates or on static services
+command-version-static-service-invalid=The given service does not exist (maybe the service was never started before?)
+command-version-install-failed=Unable to install the requested service version\!
+command-version-install-success=The requested service version was successfully installed
+command-version-install-try=Trying to install the requested service version...
+command-version-install-wrong-java=The version {0$version$} is not compatible with your current java version {1$java$}
+#
+# Module Bridge
+#
+module-bridge-command-description=Management for the config of the bridge module
+module-bridge-player-command-description=Management for online and offline cloud players
+module-bridge-tasks-setup-default-fallback=Which fallback task should be used for this proxy? (Use none if you don't want to configure it now)
+module-bridge-plugin-message-sending-failed=Failed to send a message to the {0$channel$} channel
+module-bridge-command-create-entry-success=The bridge configuration entry has been created
+module-bridge-command-entry-already-exists=There already is a configuration entry for this group
+module-bridge-command-players-delete-player=The player {0$name$}\#{1$uniqueId$} will be deleted from the database
+module-bridge-command-players-kick-player-force=Notice that force disconnecting a player is not supported and should not be used when not necessary\!
+module-bridge-command-players-kick-player=The player {0$name$}\#{1$uniqueId$} will be kicked from the network with reason "{2$reason$}"...
+module-bridge-command-players-player-not-online=That player isn't online
+module-bridge-command-players-player-not-registered=That player isn't registered
+module-bridge-command-players-send-player-message=The message will be sent to the player {0$name$}\#{1$uniqueId$}...
+module-bridge-command-players-send-player-server-not-found=That service doesn't exist
+module-bridge-command-players-send-player-server=The player {0$name$}\#{1$uniqueId$} will be sent to the service...
+#
+# Module Cloudflare
+#
+module-cloudflare-create-dns-record-for-service=DNS Entry on domain {0$domain$} was created for service {1$service$} with the id {2$recordId$}
+module-cloudflare-delete-dns-record-for-service=DNS entry was deleted on domain {0$domain$} for service {1$service$} with the id {2$recordId$}
+#
+# Module NPC
+#
+module-npc-command-description=Administration of npc configurations
+module-npc-command-create-entry-success=The npc configuration entry has been created
+module-npc-tasks-setup-generate-default-config=Should the default NPC configuration entry be generated for this task?
+module-npc-command-create-entry-group-already-exists=The npc configuration entry already exists
+#
+# Module Report
+#
+module-report-command-description=Uploads useful data about the node and cluster to a paste server
+module-report-command-paste-failed=Failed to upload the data on {0$url$}
+module-report-command-paste-success=The data has been uploaded on {0$url$}
+module-report-command-service-not-found=The service {0$name$} is not registered
+module-report-command-paste-server-not-found=The paste service {0$name$} is not registered
+#
+# Module Signs
+#
+module-sign-command-description=Administration of sign configurations
+module-sign-command-create-entry-success=The sign configuration entry has been created
+module-sign-tasks-setup-generate-default-config=Should the default signs configuration entry be generated for this task?
+module-sign-command-create-entry-group-already-exists=The sign configuration entry already exists
+#
+# Module SyncProxy
+#
+module-syncproxy-command-description=Administration of all SyncProxy configurations
+module-syncproxy-command-add-whitelist-entry=The entry {0$name$} was added to the {1$group$} configuration whitelist
+module-syncproxy-command-create-entry-group-already-exists=There already is a configuration entry for this group
+module-syncproxy-command-create-entry-success=The SyncProxy configuration entry has been created
+module-syncproxy-command-remove-whitelist-entry=The entry {0$name$} was removed from the {1$group$} configuration whitelist
+module-syncproxy-command-set-maintenance=The maintenance mode of configuration {0$group$} is now {1, choice, 0\#disabled|1\#enabled$maintenance$}
+module-syncproxy-command-set-maxplayers=The player limit of configuration {0$group$} is now {1$count$}
+#
+# Module Smart
+#
+module-smart-command-description=Administration for the smart config of each task
+module-smart-command-task-no-entry=The task {0$task$} has no configured smart entry
+#
+# Module Docker Services
+#
+module-docker-command-description=Administration of the docker module configuration
+module-docker-command-set-success=The property {0$property$} was successfully changed to {1$value$}
+module-docker-command-remove-success=The property {0$property$} was successfully removed
+module-docker-command-add-collection-property=The {0$property$} {1$value$} was successfully added
+module-docker-command-clear-collection-property=The {0$property$} were successfully cleared
+module-docker-command-remove-collection-property=The {0$property$} {1$value$} was successfully removed
+#
+# version installer
+#
+versions-installer-deprecated-version=You are installing an unsupported version\! These versions may contain security vulnerabilities and may not work as expected with CloudNet. Use at your own risk\!

From 9684943d803bcb78b0f5e06c50917f84194c4cd1 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 30 Aug 2024 23:09:28 +0200
Subject: [PATCH 05/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index 278a73c7c1..73d6d7c8e3 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -266,7 +266,7 @@ command-tasks-create-task=Der leere Task wurde erfolgreich erstellt. Dieser kann
 command-tasks-delete-task=Der Task {0$name$} wurde erfolgreich gelöscht
 command-tasks-node-not-found=Diese Node existiert nicht\!
 command-tasks-runtime-not-found=Die Runtime {0$runtime$} existiert nicht\!
-command-tasks-inclusion-cache-strategy-not-found=The inclusion cache strategy {0$strategy$} does not exist\!
+command-tasks-inclusion-cache-strategy-not-found=Die Inclusions Cache Strategie {0$strategy$} existiert nicht\!
 command-tasks-reload-success=Die Tasks wurden neu geladen\!
 command-tasks-add-collection-property={0$property$} {2$value$} wurde erfolgreich dem Task {1$task$} hinzugefügt
 command-tasks-set-property-success={0$property$} von dem Task {1$task$} wurde zu {2$value$} geändert

From 0551146af35ed33c00e7c372c4a297d00620e053 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 9 Sep 2024 19:59:29 +0200
Subject: [PATCH 06/28] New translations en_us.properties (Russian) [ci skip]

---
 node/src/main/resources/lang/ru_RU.properties | 296 +++++++++---------
 1 file changed, 148 insertions(+), 148 deletions(-)

diff --git a/node/src/main/resources/lang/ru_RU.properties b/node/src/main/resources/lang/ru_RU.properties
index a5aa3ebefc..3613eb5c00 100644
--- a/node/src/main/resources/lang/ru_RU.properties
+++ b/node/src/main/resources/lang/ru_RU.properties
@@ -13,68 +13,68 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 #
-cloudnet-init-eula-not-accepted=If you don't accept the eula, you cannot run a minecraft server\!
-cloudnet-init-eula=Do you agree to the Mojang EULA (https\://aka.ms/MinecraftEULA)?
-cloudnet-init-setup-cluster-cluster-id=What is the id of your cluster? (you can find it in the config.json on of your nodes)
-cloudnet-init-setup-cluster-install=Is this node part of a cluster? (MultiRoot)
-cloudnet-init-setup-cluster-list-nodes=What are the names of your already existing nodes? (separated by ";")
-cloudnet-init-setup-cluster-node-host=What is the host and port of the node "{0$node$}"? (you can find it in the config.json at "listeners")
-cloudnet-init-setup-host-address=On which host should the services be started on? Note\: Wildcard addresses (like 0.0.0.0) are not allowed
-cloudnet-init-setup-internal-host=On which host and port should CloudNet run on? (This is NOT your proxy host/port)
-cloudnet-init-setup-memory=How much memory (in MB) can the services running on this CloudNet node use?
-cloudnet-init-setup-node-id=What should the name of this CloudNet node be?
-cloudnet-init-setup-tasks-javacommand=What is the path to the Java executable?
-cloudnet-init-setup-tasks-proxy-environment=What should be the environment of the proxy?
-cloudnet-init-setup-tasks-proxy-version=Which ServiceVersion should be used on the proxies?
-cloudnet-init-setup-tasks-server-environment=What should be the environment of the services?
-cloudnet-init-setup-tasks-server-version=Which ServiceVersion should be used on the services?
-cloudnet-init-setup-tasks-should-install-proxy=Should a default proxy be created?
-cloudnet-init-setup-tasks-should-install-server=Should a default lobby be created?
-cloudnet-init-setup-web-host=On which host and port should CloudNet's WebServer run?
-cloudnet-init-default-modules=Which default modules should be installed? (separated by a space)
+cloudnet-init-eula-not-accepted=Если вы не принимаете лицензионное соглашение, вы не сможете запустить сервер Minecraft\!
+cloudnet-init-eula=Согласны ли вы с лицензией Mojang (https\://aka.ms/MinecraftEULA)?
+cloudnet-init-setup-cluster-cluster-id=Какой идентификатор вашего кластера? (вы можете найти его в config.json на одном из ваших узлов)
+cloudnet-init-setup-cluster-install=Является ли этот узел частью кластера? (MultiRoot)
+cloudnet-init-setup-cluster-list-nodes=Как называются ваши уже существующие узлы? (разделенные ";")
+cloudnet-init-setup-cluster-node-host=Какой хост и порт узла "{0$node$}"? (вы можете найти его в config.json в разделе "listeners")
+cloudnet-init-setup-host-address=На каком хосте должны быть запущены сервисы? Примечание\: адреса типа (например, 0.0.0.0) не допускаются
+cloudnet-init-setup-internal-host=На каком хосте и порту должен работать CloudNet? (Это НЕ ваш прокси хост/порт)
+cloudnet-init-setup-memory=Сколько памяти (в МБ) могут использовать сервисы, работающие на этом узле CloudNet?
+cloudnet-init-setup-node-id=Как должен называться этот узел CloudNet?
+cloudnet-init-setup-tasks-javacommand=Какой путь к исполняемому файлу Java?
+cloudnet-init-setup-tasks-proxy-environment=Какой прокси вы хотите использовать?
+cloudnet-init-setup-tasks-proxy-version=Какая версия ServiceVersion должна использоваться на прокси-серверах?
+cloudnet-init-setup-tasks-server-environment=Каким должно быть окружение сервисов?
+cloudnet-init-setup-tasks-server-version=Какая версия ServiceVersion должна использоваться на сервисах?
+cloudnet-init-setup-tasks-should-install-proxy=Должен ли быть создан стандартный прокси?
+cloudnet-init-setup-tasks-should-install-server=Должен ли быть создан стандартный лобби?
+cloudnet-init-setup-web-host=На каком хосте и порту должен работать веб-сервер CloudNet?
+cloudnet-init-default-modules=Какие стандартные модули должны быть установлены? (разделенные пробелом)
 #
 # Console animations
 #
-ca-question-list-cancel=You can always cancel the process by typing "cancel"\!
-ca-question-list-cancelled=The process has been cancelled\!
-ca-question-list-explain=Use the arrow keys to scroll through all possible values (if there are default values specified). If there is a recommended value available, it is in the command input line by default
-ca-question-list-invalid-default=Please provide a valid value\!
-ca-question-list-possible-answers-list=Possible answers\: {0$values$}
-ca-question-list-question-list=You have to provide one of the following\: {0$values$}
+ca-question-list-cancel=Вы всегда можете отменить процесс, набрав "cancel"\!
+ca-question-list-cancelled=Процесс был отменен\!
+ca-question-list-explain=Используйте стрелки для прокрутки всех возможных значений (если указаны значения по умолчанию). Если есть рекомендованное значение, оно будет автоматически введено в строке ввода команды
+ca-question-list-invalid-default=Пожалуйста, укажите допустимое значение\!
+ca-question-list-possible-answers-list=Возможные ответы\: {0$values$}
+ca-question-list-question-list=Вы должны указать одно из следующих значений\: {0$values$}
 #
 # Network
 #
-client-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] has closed the connection
-client-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] connected to the server
-server-network-channel-close=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was closed
-server-network-channel-init=Channel [serverAddress\={0$serverAddress$} clientAddress\={1$clientAddress$}] was connected
-network-listener-bound=Successfully bound a network listener to the address "{0$address$}"...
-network-listener-bound-exceptionally=Unable to bind network listener to "{0$address$}"\: {1$reason$}
-network-selected-transport=Network components are using {0$transport$} transport
-network-selected-dispatch-thread-type=Network dispatchers are using {0$type$} threads
-startup-failed-no-network-listener-bound=Unable to complete startup, no network listener was bound successfully\! CloudNet will stop in 5 seconds
+client-network-channel-close=Канал [адрес сервера\={0$serverAddress$} адрес клиента\={1$clientAddress$}] закрыл соединение
+client-network-channel-init=Канал [адрес сервера\={0$serverAddress$} адрес клиента\={1$clientAddress$}] подключился к серверу
+server-network-channel-close=Канал [адрес сервера\={0$serverAddress$} адрес клиента\={1$clientAddress$}] был закрыт
+server-network-channel-init=Канал [адрес сервера\={0$serverAddress$} адрес клиента\={1$clientAddress$}] был подключен
+network-listener-bound=Сетевой слушатель успешно привязан к адресу "{0$address$}"...
+network-listener-bound-exceptionally=Не удалось привязать сетевой слушатель к "{0$address$}"\: {1$reason$}
+network-selected-transport=Сетевые компоненты используют транспорт {0$transport$}
+network-selected-dispatch-thread-type=Диспетчеры сети используют потоки {0$type$}
+startup-failed-no-network-listener-bound=Невозможно завершить запуск, не удалось успешно привязать сетевой слушатель\! CloudNet остановится через 5 секунд
 #
 # Application lifecycle
 #
-start-version-provider=Loaded {0$amount$} service versions...
-start-module-updater=Applying needed updates to installed modules...
-start-commands=Registered commands...
-start-node-connection-try=Trying to connect to node {0$name$}...
-start-node-connection-failure=Unable to connect to node {0$name$}\: {1$reason$}
-start-node-connection-waiting=Waiting for {0$amount$} node connections to establish...
-start-requesting-data=Requesting cluster sync from head node...
-start-connect-database=Using database {0$database$}...
-start-done=Startup done, starting tick loop (Took {0$starttime$}ms)
-stop-application=Stopping application...
-stop-node-connections=Closing connections to all nodes of the cluster...
-stop-providers=Closing providers...
-stop-network-components=Closing network components...
-stop-services=Stopping all running services...
-stop-delete-temp=Deleting temporary files...
+start-version-provider=Загружено {0$amount$} версий сервисов...
+start-module-updater=Применение необходимых обновлений к установленным модулям...
+start-commands=Регистрация команд...
+start-node-connection-try=Попытка подключения к узлу {0$name$}...
+start-node-connection-failure=Не удалось подключиться к узлу {0$name$}\: {1$reason$}
+start-node-connection-waiting=Ожидается {0$amount$} подключений к узлам...
+start-requesting-data=Запрос синхронизации кластера от главного узла...
+start-connect-database=Использование базы данных {0$database$}...
+start-done=Запуск завершен, запуск цикла тиков (Заняло {0$starttime$}мс)
+stop-application=Остановка приложения...
+stop-node-connections=Закрытие соединений со всеми узлами кластера...
+stop-providers=Закрытие провайдеров...
+stop-network-components=Закрытие сетевых компонентов...
+stop-services=Остановка всех запущенных сервисов...
+stop-delete-temp=Удаление временных файлов...
 #
 # Services
 #
-cloudnet-service-jar-file-not-found-error=No application file found for CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}]\! Please check the availability of this file. Using the "version" command a version can be installed.
+cloudnet-service-jar-file-not-found-error=Не найден файл приложения для CloudService [ИД\={0$id$} задача\={1$task$} имя\={2$name$}]\! Пожалуйста, проверьте доступность этого файла. С помощью команды "version" можно установить версию.
 cloudnet-service-manager-cpu-usage-to-high-error=The CPU load is too high to create a new service\! The system will try to start this service as soon as there are enough resources.
 cloudnet-service-manager-max-memory-error=The maximum allocatable memory has been reached (of CloudNet, other system resources might still be available)\! The limit has to be increased or other services need to be stopped.
 cloudnet-service-networking-connected=CloudService [uniqueId\={0$id$} task\={1$task$} name\={2$name$}] was successfully connected to the channel [serverAddress\={3$serverAddress$} clientAddress\={4$clientAddress$}]
@@ -140,82 +140,82 @@ command-any-host-invalid=The given input {0$input$} is not a valid host address.
 #
 # Command Help
 #
-commnad-help-description=Shows all commands and their description
-command-help-docs=Follow this url {0$url$} to get to the documentation for the {1$command$} command
-command-help-docs-no-url=The {0$command$} command has no documentation url
+commnad-help-description=Показывает все команды и их описание
+command-help-docs=Перейдите по этому URL {0$url$}, чтобы получить документацию для команды {1$command$}
+command-help-docs-no-url=У команды {0$command$} нет URL-адреса документации
 #
 # Command Me
 #
-command-me-description=Displays all important information about this node and the running jvm
+command-me-description=Отображает всю важную информацию об этом узле и работающей виртуальной машине
 #
 # Command clear
 #
-command-clear-description=Clears the entire console of the node to get a better overview
+command-clear-description=Очищает всю консоль текущего узла
 #
 # Command Cluster
 #
-command-cluster-description=Manages the cluster and provides information about it
-command-cluster-add-node-success=Registered the new node ({0$name$}) to the cluster configuration
-command-cluster-node-not-found=That node doesn't exist
-command-cluster-node-set-drain=Draining is now {0, choice, 0\#disabled|1\#enabled$drain$} for node {1$node$}
-command-cluster-push-static-service-failed=Failed to deploy the static service to the cluster
-command-cluster-push-static-service-not-found=The static service was not found
-command-cluster-push-static-service-running=The static service is running. Stop the service to deploy it into the cluster
-command-cluster-push-static-service-starting=Starting the deployment of the static service...
-command-cluster-push-static-service-success=Successfully deployed the static service into the cluster
-command-cluster-push-static-service-existing=The received static service {0$service$} already exists, aborting deployment
-command-cluster-push-static-service-received-success=Successfully received the deployed static service {0$service$}
-command-cluster-push-static-service-running-remote=The received static service {0$service$} is running, aborting deployment
-command-cluster-push-template-compress=Compressing the template {0$template$}...
-command-cluster-push-template-failed=Failed to send the local template {0$template$} to the cluster
-command-cluster-push-template-success=The local template {0$template$} was successfully sent to all nodes
-command-cluster-remove-node-success=The node {0$node$} has been removed successfully
-command-cluster-start-sync=The cluster sync starts now
+command-cluster-description=Управляет кластером и предоставляет информацию о нем
+command-cluster-add-node-success=Зарегистрирован новый узел ({0$name$}) в конфигурации кластера
+command-cluster-node-not-found=Этот узел не существует
+command-cluster-node-set-drain=Дренирование теперь {0, choice, 0\#отключено|1\#включено$drain$} для узла {1$node$}
+command-cluster-push-static-service-failed=Не удалось развернуть статический сервис в кластере
+command-cluster-push-static-service-not-found=Статический сервис не найден
+command-cluster-push-static-service-running=Статический сервис работает. Остановите сервис, чтобы развернуть ее в кластере
+command-cluster-push-static-service-starting=Начало развертывания статического сервиса...
+command-cluster-push-static-service-success=Статический сервис успешно развернут в кластере
+command-cluster-push-static-service-existing=Полученный статический сервис {0$service$} уже существует, остановка развертывания
+command-cluster-push-static-service-received-success=Статический сервис {0$service$} успешно развернут
+command-cluster-push-static-service-running-remote=Статический сервис {0$service$} уже запущен, остановка развертывания
+command-cluster-push-template-compress=Сжатие шаблона {0$template$}...
+command-cluster-push-template-failed=Не удалось отправить локальный шаблон {0$template$} в кластер
+command-cluster-push-template-success=Локальный шаблон {0$template$} успешно отправлен на все узлы
+command-cluster-remove-node-success=Узел {0$node$} успешно удален
+command-cluster-start-sync=Синхронизация кластера начинается сейчас
 #
 # Command Service
 #
-command-service-description=Manages all services in the cluster
-command-service-copy-no-default-template=The service you provided does not have a default template, use "copy {0$name$} template\=storage\:prefix/name" to provide a template you would like to copy to
-command-service-copy-success=The service {0$name$} was successfully copied to the template {1$template$}
-command-service-add-deployment-success=The deployment {0$deployment$} was successfully added to the waiting deployments
-command-service-deploy-deployment-success=The resources of the service were successfully deployed
-command-service-add-inclusion-success=The inclusion {0$inclusion$} was successfully added to the waiting integrations
-command-service-include-inclusion-success=All waiting inclusions were downloaded and installed to the service
-command-service-add-template-success=The template {0$template$} was successfully found and was added to the waiting templates
-command-service-include-templates-success=All waiting templates were copied to the service
-command-service-service-not-found=That service doesn't exist
-command-service-toggle-disabled=Disabled the automatic console logging for {0$service$}
-command-service-toggle-enabled=Enabled the automatic console logging for {0$service$}
+command-service-description=Управляет всеми сервисами в кластере
+command-service-copy-no-default-template=У сервисов, которую вы предоставили, нет шаблона по умолчанию, используйте "copy {0$name$} template\=storage\:prefix/name" для указания шаблона, который вы хотели бы скопировать
+command-service-copy-success=Сервис {0$name$} успешно скопирован в шаблон {1$template$}
+command-service-add-deployment-success=Развертывание {0$deployment$} успешно добавлено в ожидающие развертывания
+command-service-deploy-deployment-success=Ресурсы сервиса успешно развернуты
+command-service-add-inclusion-success=Включение {0$inclusion$} успешно добавлено в ожидающие интеграции
+command-service-include-inclusion-success=Все ожидающие включения были загружены и установлены для сервисов
+command-service-add-template-success=Шаблон {0$template$} успешно найден и добавлен в ожидающие шаблоны
+command-service-include-templates-success=Все ожидающие шаблоны были скопированы в сервис
+command-service-service-not-found=Такой сервис не существует
+command-service-toggle-disabled=Отключено автоматическое логирование консоли для {0$service$}
+command-service-toggle-enabled=Включено автоматическое логирование консоли для {0$service$}
 #
 # Command Create
 #
-command-create-description=Creates one or more new services based on a task or completely independent
-command-create-by-task-starting=Starting to create {1$amount$} services for {0$task$}
-command-create-by-task-failed=The services couldn't be created
-command-create-by-task-success=The services were created based on the task. They can be managed with the 'service' command
+command-create-description=Создает один или несколько новых сервисов на основе задачи или полностью независимых
+command-create-by-task-starting=Начало создания {1$amount$} сервисов для {0$task$}
+command-create-by-task-failed=Не удалось создать сервисы
+command-create-by-task-success=Сервисы были созданы на основе задачи. Ими можно управлять с помощью команды 'service'
 #
 # Command Debug
 #
-command-debug-description=Toggle the global debug mode
+command-debug-description=Переключает глобальный режим отладки
 #
 # Command exit
 #
-command-exit-description=Stops the program and all managed subprocesses
+command-exit-description=Останавливает программу и все управляемые дочерние процессы
 #
 # Command Migrate
 #
-command-migrate-description=Allows to migrate data known to CloudNet between different storages
-command-migrate-current-database=Migration of {0$db$} in progress...
-command-migrate-database-connection-failed=The connection to the database failed
-command-migrate-source-equals-target=Migrating data to the same database is not possible
-command-migrate-success=Migrating {0$source$} to {1$target$} was successful
-command-migrate-unknown-database-provider=This database type does not exist
+command-migrate-description=Позволяет мигрировать данные, известные CloudNet, между различными хранилищами
+command-migrate-current-database=Миграция {0$db$} в процессе...
+command-migrate-database-connection-failed=Не удалось подключиться к базе данных
+command-migrate-source-equals-target=Миграция данных в ту же базу данных невозможна
+command-migrate-success=Миграция {0$source$} в {1$target$} прошла успешно
+command-migrate-unknown-database-provider=Этот тип базы данных не существует
 #
 # Command Modules
 #
-command-modules-description=Manages installed modules and allows to load local or install remote modules
-command-modules-install-missing-depend=The module {0$module$} requires these dependencies to run\: {1$dependencies$}
-command-modules-module-already-loaded=The module {0$module$} is already loaded
+command-modules-description=Управляет модулями и позволяет загружать локальные или удаленные модули
+command-modules-install-missing-depend=Модуль {0$module$} требует эти зависимости для запуска\: {1$dependencies$}
+command-modules-module-already-loaded=Модуль {0$module$} уже загружен
 command-modules-module-file-not-found=The file {0$path$} does not exist
 command-modules-module-not-a-file={0$path$} is not a file
 command-modules-module-installed=The module {0$module$} was successfully installed
@@ -283,71 +283,71 @@ command-tasks-setup-create-success=The new task {0$name$} has been successfully
 command-tasks-setup-question-application=Which service version should run on services of this task?
 command-tasks-setup-question-environment=What should be the environment of this task?
 command-tasks-setup-question-javacommand-invalid=The provided executable is not a valid java installation path
-command-tasks-setup-question-javacommand=What is the path to the Java executable?
-command-tasks-setup-question-maintenance=Should the task be in maintenance by default? (this prevents auto starting of the services)
-command-tasks-setup-question-memory=How much memory is each service of the task allowed to use? (in MB)
-command-tasks-setup-question-minservices=How many services of this task should be always online?
-command-tasks-setup-question-name-splitter=What should the name splitter of the new task be?
-command-tasks-setup-question-name=What should the name of the new task be?
-command-tasks-setup-question-startport=What should be the start port of the task?
-command-tasks-setup-question-host-address=What is the host address of the task?
-command-tasks-setup-question-static=Should the services of this task be static that their files are never deleted?
+command-tasks-setup-question-javacommand=Какой путь к исполняемому файлу Java?
+command-tasks-setup-question-maintenance=Должна ли задача по умолчанию находиться в режиме обслуживания? (это предотвращает автоматический запуск сервисов)
+command-tasks-setup-question-memory=Сколько памяти каждый сервис задачи может использовать? (в МБ)
+command-tasks-setup-question-minservices=Сколько сервисов этой задачи должно всегда быть в сети?
+command-tasks-setup-question-name-splitter=Каким должно быть разделение задачи? (Например "-")
+command-tasks-setup-question-name=Как должна называться новая задача?
+command-tasks-setup-question-startport=Какой должен быть стартовый порт задачи?
+command-tasks-setup-question-host-address=Каков адрес хоста для задачи?
+command-tasks-setup-question-static=Должны ли сервисы этой задачи быть статическими, чтобы их файлы никогда не удалялись?
 #
 # Command Template
 #
-command-template-description=Manages local and remote templates
-command-template-copy-failed=Unable to prepare source template for deployment\! Does the source template exists?
-command-template-copy-same-source-and-target=The source and target templates cannot be the same
-command-template-copy-success=Successfully copied the template {0$sourceTemplate$} to the template {1$targetTemplate$}
-command-template-copy=Trying to copy the template {0$sourceTemplate$} to the template {1$targetTemplate$}...
-command-template-create-failed=Failed to prepare the template {0$template$} in the storage {1$storage$}
-command-template-create-success=The template {0$template$} was successfully created and prepared in the storage {1$storage$}
-command-template-create-template-already-exists=The template {0$template$} already exists in the storage {1$storage$}
-command-template-delete-success=The template {0$template$} was successfully removed from the storage {1$storage$}
-command-template-delete-template-not-found=The template {0$template$} doesn''t exist in the storage {1$storage$}
-command-template-invalid-version-type=That version type doesn't exist
-command-template-invalid-version=That version doesn't exist for that version type
-command-template-not-found=The template {0$template$} doesn''t exist
-command-template-not-valid=The given template name is not valid\!
-command-template-storage-not-found=That storage {0$storage$} doesn''t exist
-command-template-environment-not-found=The environment {0$env$} doesn''t exist
+command-template-description=Управляет локальными и удаленными шаблонами
+command-template-copy-failed=Не удалось подготовить исходный шаблон для развертывания\! Существует исходный шаблон?
+command-template-copy-same-source-and-target=Исходный и выбранный шаблоны не могут быть одинаковыми
+command-template-copy-success=Шаблон {0$sourceTemplate$} успешно скопирован в шаблон {1$targetTemplate$}
+command-template-copy=Попытка копирования шаблона {0$sourceTemplate$} в шаблон {1$targetTemplate$}...
+command-template-create-failed=Не удалось подготовить шаблон {0$template$} в хранилище {1$storage$}
+command-template-create-success=Шаблон {0$template$} успешно создан и подготовлен в хранилище {1$storage$}
+command-template-create-template-already-exists=Шаблон {0$template$} уже существует в хранилище {1$storage$}
+command-template-delete-success=Шаблон {0$template$} успешно удален из хранилища {1$storage$}
+command-template-delete-template-not-found=Шаблон {0$template$} не существует в хранилище {1$storage$}
+command-template-invalid-version-type=Этот тип версии не существует
+command-template-invalid-version=Эта версия не существует для этого типа версии
+command-template-not-found=Шаблон {0$template$} не существует
+command-template-not-valid=Указанное имя шаблона недопустимо\!
+command-template-storage-not-found=Это хранилище {0$storage$} не существует
+command-template-environment-not-found=Среда {0$env$} не существует
 #
 # Command Version
 #
-command-version-description=Manage service versions in templates or on static services
-command-version-static-service-invalid=The given service does not exist (maybe the service was never started before?)
-command-version-install-failed=Unable to install the requested service version\!
-command-version-install-success=The requested service version was successfully installed
-command-version-install-try=Trying to install the requested service version...
-command-version-install-wrong-java=The version {0$version$} is not compatible with your current java version {1$java$}
+command-version-description=Управление версиями сервисов в шаблонах или статических сервисах
+command-version-static-service-invalid=Указанный сервис не существует (возможно, сервис никогда не запускался ранее?)
+command-version-install-failed=Не удалось установить запрошенную версию сервиса\!
+command-version-install-success=Запрошенная версия сервиса успешно установлена
+command-version-install-try=Попытка установки запрошенной версии сервиса...
+command-version-install-wrong-java=Версия {0$version$} не совместима с вашей текущей версией Java {1$java$}
 #
 # Module Bridge
 #
-module-bridge-command-description=Management for the config of the bridge module
-module-bridge-player-command-description=Management for online and offline cloud players
-module-bridge-tasks-setup-default-fallback=Which fallback task should be used for this proxy? (Use none if you don't want to configure it now)
+module-bridge-command-description=Управление конфигурацией модуля моста
+module-bridge-player-command-description=Управление онлайн и оффлайн-игроками
+module-bridge-tasks-setup-default-fallback=Какая резервная задача должна использоваться для этого прокси? (Оставьте пустым, если вы не хотите настраивать это сейчас)
 module-bridge-plugin-message-sending-failed=Failed to send a message to the {0$channel$} channel
-module-bridge-command-create-entry-success=The bridge configuration entry has been created
-module-bridge-command-entry-already-exists=There already is a configuration entry for this group
-module-bridge-command-players-delete-player=The player {0$name$}\#{1$uniqueId$} will be deleted from the database
-module-bridge-command-players-kick-player-force=Notice that force disconnecting a player is not supported and should not be used when not necessary\!
-module-bridge-command-players-kick-player=The player {0$name$}\#{1$uniqueId$} will be kicked from the network with reason "{2$reason$}"...
-module-bridge-command-players-player-not-online=That player isn't online
-module-bridge-command-players-player-not-registered=That player isn't registered
-module-bridge-command-players-send-player-message=The message will be sent to the player {0$name$}\#{1$uniqueId$}...
-module-bridge-command-players-send-player-server-not-found=That service doesn't exist
-module-bridge-command-players-send-player-server=The player {0$name$}\#{1$uniqueId$} will be sent to the service...
+module-bridge-command-create-entry-success=Конфигурационная запись для Bridge была создана
+module-bridge-command-entry-already-exists=Для этой группы уже существует конфигурационная запись
+module-bridge-command-players-delete-player=Игрок {0$name$}\#{1$uniqueId$} будет удален из базы данных
+module-bridge-command-players-kick-player-force=Обратите внимание, что принудительное отключение игрока не поддерживается и не следует использовать без необходимости\!
+module-bridge-command-players-kick-player=Игрок {0$name$}\#{1$uniqueId$} будет отключен от сети с причиной "{2$reason$}"...
+module-bridge-command-players-player-not-online=Этот игрок не в сети
+module-bridge-command-players-player-not-registered=Этот игрок не зарегистрирован
+module-bridge-command-players-send-player-message=Сообщение будет отправлено игроку {0$name$}\#{1$uniqueId$}...
+module-bridge-command-players-send-player-server-not-found=Этот сервис не существует
+module-bridge-command-players-send-player-server=Игрок {0$name$}\#{1$uniqueId$} будет отправлен на сервис...
 #
 # Module Cloudflare
 #
-module-cloudflare-create-dns-record-for-service=DNS Entry on domain {0$domain$} was created for service {1$service$} with the id {2$recordId$}
-module-cloudflare-delete-dns-record-for-service=DNS entry was deleted on domain {0$domain$} for service {1$service$} with the id {2$recordId$}
+module-cloudflare-create-dns-record-for-service=Запись DNS на домене {0$domain$} была создана для сервиса {1$service$} с идентификатором {2$recordId$}
+module-cloudflare-delete-dns-record-for-service=Запись DNS на домене {0$domain$} была удалена для сервиса {1$service$} с идентификатором {2$recordId$}
 #
 # Module NPC
 #
-module-npc-command-description=Administration of npc configurations
-module-npc-command-create-entry-success=The npc configuration entry has been created
-module-npc-tasks-setup-generate-default-config=Should the default NPC configuration entry be generated for this task?
+module-npc-command-description=Управление конфигураций NPC
+module-npc-command-create-entry-success=Конфигурационная запись NPC была создана
+module-npc-tasks-setup-generate-default-config=Следует ли создать конфигурацию NPC по умолчанию для этой задачи?
 module-npc-command-create-entry-group-already-exists=The npc configuration entry already exists
 #
 # Module Report

From 28f0fde4b70e0db8bcbc03ef56c198a42185c1a0 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 9 Sep 2024 21:03:14 +0200
Subject: [PATCH 07/28] Update source file en_US.properties [ci skip]

---
 node/src/main/resources/lang/en_US.properties | 22 +++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/node/src/main/resources/lang/en_US.properties b/node/src/main/resources/lang/en_US.properties
index caf5829190..7e76a65918 100644
--- a/node/src/main/resources/lang/en_US.properties
+++ b/node/src/main/resources/lang/en_US.properties
@@ -117,17 +117,17 @@ invalid-command-sender=This command cannot be executed by ''{0$source$}''
 invalid-command-syntax=Invalid syntax! Use {0$syntax$}
 no-such-command=Command could not be found! For help, use the command "help"
 argument-parse-failure-no-input-was-provided=No input provided
-argument-parse-failure-boolean=The given input {0$input$} is not a boolean
-argument-parse-failure-number=The given input {0$input$} is not a number
-argument-parse-failure-char=The given input {0$input$} is not a char
-argument-parse-failure-string=The given input {0$input$} is not a string
-argument-parse-failure-uuid=The given input {0$input$} is not an uuid
-argument-parse-failure-enum=The given input enum {0$input$} is not one of the following {1$values$}
-argument-parse-failure-regex=The given input &b{1$input$}&r does not match &b{0$regex$}
-argument-parse-failure-duration=The given input {0$input$} is not a duration
-argument-parse-failure-flag-unknown=The given flag {0$flag$} is unknown
-argument-parse-failure-flag-duplicate-flag=The given flag {0$flag$} can only be used once
-argument-parse-failure-flag-missing-argument=Missing argument for flag {0$flag$}
+argument-parse-failure-boolean=The given input &b{0$input$}&r is not a boolean
+argument-parse-failure-number=The given input &b{0$input$}&r is not a number
+argument-parse-failure-char=The given input &b{0$input$}&r is not a char
+argument-parse-failure-string=The given input &b{0$input$}&r is not a string
+argument-parse-failure-uuid=The given input &b{0$input$}&r is not an uuid
+argument-parse-failure-enum=The given input enum &b{0$input$}&r is not one of the following &b{1$values$}
+argument-parse-failure-regex=The given input &b{0$input$}&r does not match &b{1$regex$}
+argument-parse-failure-duration=The given input &b{0$input$}&r is not a duration
+argument-parse-failure-flag-unknown=The given flag &b{0$flag$}&r is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag &b{0$flag$}&r can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag &b{0$flag$}
 argument-parse-failure-flag-no-permission=You are not allowed to use this flag
 missing-command-permission=You are not allowed to execute this sub command
 #

From 553b14d815697b03e94384cc9b8be79e0ad944f5 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 9 Sep 2024 21:03:16 +0200
Subject: [PATCH 08/28] New translations en_us.properties (French) [ci skip]

---
 node/src/main/resources/lang/fr_FR.properties | 22 +++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/node/src/main/resources/lang/fr_FR.properties b/node/src/main/resources/lang/fr_FR.properties
index a5aa3ebefc..99956f7779 100644
--- a/node/src/main/resources/lang/fr_FR.properties
+++ b/node/src/main/resources/lang/fr_FR.properties
@@ -117,17 +117,17 @@ invalid-command-sender=This command cannot be executed by ''{0$source$}''
 invalid-command-syntax=Invalid syntax\! Use {0$syntax$}
 no-such-command=Command could not be found\! For help, use the command "help"
 argument-parse-failure-no-input-was-provided=No input provided
-argument-parse-failure-boolean=The given input {0$input$} is not a boolean
-argument-parse-failure-number=The given input {0$input$} is not a number
-argument-parse-failure-char=The given input {0$input$} is not a char
-argument-parse-failure-string=The given input {0$input$} is not a string
-argument-parse-failure-uuid=The given input {0$input$} is not an uuid
-argument-parse-failure-enum=The given input enum {0$input$} is not one of the following {1$values$}
-argument-parse-failure-regex=The given input &b{1$input$}&r does not match &b{0$regex$}
-argument-parse-failure-duration=The given input {0$input$} is not a duration
-argument-parse-failure-flag-unknown=The given flag {0$flag$} is unknown
-argument-parse-failure-flag-duplicate-flag=The given flag {0$flag$} can only be used once
-argument-parse-failure-flag-missing-argument=Missing argument for flag {0$flag$}
+argument-parse-failure-boolean=The given input &b{0$input$}&r is not a boolean
+argument-parse-failure-number=The given input &b{0$input$}&r is not a number
+argument-parse-failure-char=The given input &b{0$input$}&r is not a char
+argument-parse-failure-string=The given input &b{0$input$}&r is not a string
+argument-parse-failure-uuid=The given input &b{0$input$}&r is not an uuid
+argument-parse-failure-enum=The given input enum &b{0$input$}&r is not one of the following &b{1$values$}
+argument-parse-failure-regex=The given input &b{0$input$}&r does not match &b{1$regex$}
+argument-parse-failure-duration=The given input &b{0$input$}&r is not a duration
+argument-parse-failure-flag-unknown=The given flag &b{0$flag$}&r is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag &b{0$flag$}&r can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag &b{0$flag$}
 argument-parse-failure-flag-no-permission=You are not allowed to use this flag
 missing-command-permission=You are not allowed to execute this sub command
 #

From b20e1750de762e9c4eca00b9942b11ab59bc9310 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 9 Sep 2024 21:03:17 +0200
Subject: [PATCH 09/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 22 +++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index 73d6d7c8e3..756d250352 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -117,17 +117,17 @@ invalid-command-sender=Dieser Befehl kann nicht von ''{0$source$}'' ausgeführt
 invalid-command-syntax=Ungültige Syntax\! Verwende {0$syntax$}
 no-such-command=Der Befehl konnte nicht gefunden werden\! Für Hilfe verwende den Befehl "help"
 argument-parse-failure-no-input-was-provided=Es wurde keine Eingabe gemacht
-argument-parse-failure-boolean=Die Eingabe {0$input$} ist kein boolescher Wert
-argument-parse-failure-number=Die Eingabe {0$input$} ist keine Zahl
-argument-parse-failure-char=Die Eingabe {0$input$} ist kein Zeichen
-argument-parse-failure-string=Die Eingabe {0$input$} ist kein Text
-argument-parse-failure-uuid=Die Eingabe {0$input$} ist keine eindeutige Id
-argument-parse-failure-enum=Die Eingabe {0$input$} entspricht nicht einem der folgenden {1$values$}
-argument-parse-failure-regex=Die Eingabe &b{1$input$}&r entspricht nicht dem Pattern &b{0$regex$}
-argument-parse-failure-duration=Die Eingabe {0$input$} ist keine Zeitspanne
-argument-parse-failure-flag-unknown=Die gegebene Flag {0$flag$} ist unbekannt
-argument-parse-failure-flag-duplicate-flag=Die gegebene Flag {0$flag$} kann nur einmal genutzt werden
-argument-parse-failure-flag-missing-argument=Das Argument für die Flag {0$flag$} fehlt
+argument-parse-failure-boolean=The given input &b{0$input$}&r is not a boolean
+argument-parse-failure-number=The given input &b{0$input$}&r is not a number
+argument-parse-failure-char=The given input &b{0$input$}&r is not a char
+argument-parse-failure-string=The given input &b{0$input$}&r is not a string
+argument-parse-failure-uuid=The given input &b{0$input$}&r is not an uuid
+argument-parse-failure-enum=The given input enum &b{0$input$}&r is not one of the following &b{1$values$}
+argument-parse-failure-regex=The given input &b{0$input$}&r does not match &b{1$regex$}
+argument-parse-failure-duration=The given input &b{0$input$}&r is not a duration
+argument-parse-failure-flag-unknown=The given flag &b{0$flag$}&r is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag &b{0$flag$}&r can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag &b{0$flag$}
 argument-parse-failure-flag-no-permission=Es ist dir nicht gestattet die Flag zu verwenden
 missing-command-permission=Es ist dir nicht gestattet diesen Sub-Befehl auszuführen
 #

From 4c81b74677a96f9dc25f510c436731a77f33f64a Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 9 Sep 2024 21:03:18 +0200
Subject: [PATCH 10/28] New translations en_us.properties (Russian) [ci skip]

---
 node/src/main/resources/lang/ru_RU.properties | 22 +++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/node/src/main/resources/lang/ru_RU.properties b/node/src/main/resources/lang/ru_RU.properties
index 3613eb5c00..11022eb8aa 100644
--- a/node/src/main/resources/lang/ru_RU.properties
+++ b/node/src/main/resources/lang/ru_RU.properties
@@ -117,17 +117,17 @@ invalid-command-sender=This command cannot be executed by ''{0$source$}''
 invalid-command-syntax=Invalid syntax\! Use {0$syntax$}
 no-such-command=Command could not be found\! For help, use the command "help"
 argument-parse-failure-no-input-was-provided=No input provided
-argument-parse-failure-boolean=The given input {0$input$} is not a boolean
-argument-parse-failure-number=The given input {0$input$} is not a number
-argument-parse-failure-char=The given input {0$input$} is not a char
-argument-parse-failure-string=The given input {0$input$} is not a string
-argument-parse-failure-uuid=The given input {0$input$} is not an uuid
-argument-parse-failure-enum=The given input enum {0$input$} is not one of the following {1$values$}
-argument-parse-failure-regex=The given input &b{1$input$}&r does not match &b{0$regex$}
-argument-parse-failure-duration=The given input {0$input$} is not a duration
-argument-parse-failure-flag-unknown=The given flag {0$flag$} is unknown
-argument-parse-failure-flag-duplicate-flag=The given flag {0$flag$} can only be used once
-argument-parse-failure-flag-missing-argument=Missing argument for flag {0$flag$}
+argument-parse-failure-boolean=The given input &b{0$input$}&r is not a boolean
+argument-parse-failure-number=The given input &b{0$input$}&r is not a number
+argument-parse-failure-char=The given input &b{0$input$}&r is not a char
+argument-parse-failure-string=The given input &b{0$input$}&r is not a string
+argument-parse-failure-uuid=The given input &b{0$input$}&r is not an uuid
+argument-parse-failure-enum=The given input enum &b{0$input$}&r is not one of the following &b{1$values$}
+argument-parse-failure-regex=The given input &b{0$input$}&r does not match &b{1$regex$}
+argument-parse-failure-duration=The given input &b{0$input$}&r is not a duration
+argument-parse-failure-flag-unknown=The given flag &b{0$flag$}&r is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag &b{0$flag$}&r can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag &b{0$flag$}
 argument-parse-failure-flag-no-permission=You are not allowed to use this flag
 missing-command-permission=You are not allowed to execute this sub command
 #

From 096b0c2997af6acead8dfff07926d72357e15de9 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 9 Sep 2024 21:03:19 +0200
Subject: [PATCH 11/28] New translations en_us.properties (Luxembourgish) [ci
 skip]

---
 node/src/main/resources/lang/lb_LU.properties | 22 +++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/node/src/main/resources/lang/lb_LU.properties b/node/src/main/resources/lang/lb_LU.properties
index a5aa3ebefc..99956f7779 100644
--- a/node/src/main/resources/lang/lb_LU.properties
+++ b/node/src/main/resources/lang/lb_LU.properties
@@ -117,17 +117,17 @@ invalid-command-sender=This command cannot be executed by ''{0$source$}''
 invalid-command-syntax=Invalid syntax\! Use {0$syntax$}
 no-such-command=Command could not be found\! For help, use the command "help"
 argument-parse-failure-no-input-was-provided=No input provided
-argument-parse-failure-boolean=The given input {0$input$} is not a boolean
-argument-parse-failure-number=The given input {0$input$} is not a number
-argument-parse-failure-char=The given input {0$input$} is not a char
-argument-parse-failure-string=The given input {0$input$} is not a string
-argument-parse-failure-uuid=The given input {0$input$} is not an uuid
-argument-parse-failure-enum=The given input enum {0$input$} is not one of the following {1$values$}
-argument-parse-failure-regex=The given input &b{1$input$}&r does not match &b{0$regex$}
-argument-parse-failure-duration=The given input {0$input$} is not a duration
-argument-parse-failure-flag-unknown=The given flag {0$flag$} is unknown
-argument-parse-failure-flag-duplicate-flag=The given flag {0$flag$} can only be used once
-argument-parse-failure-flag-missing-argument=Missing argument for flag {0$flag$}
+argument-parse-failure-boolean=The given input &b{0$input$}&r is not a boolean
+argument-parse-failure-number=The given input &b{0$input$}&r is not a number
+argument-parse-failure-char=The given input &b{0$input$}&r is not a char
+argument-parse-failure-string=The given input &b{0$input$}&r is not a string
+argument-parse-failure-uuid=The given input &b{0$input$}&r is not an uuid
+argument-parse-failure-enum=The given input enum &b{0$input$}&r is not one of the following &b{1$values$}
+argument-parse-failure-regex=The given input &b{0$input$}&r does not match &b{1$regex$}
+argument-parse-failure-duration=The given input &b{0$input$}&r is not a duration
+argument-parse-failure-flag-unknown=The given flag &b{0$flag$}&r is unknown
+argument-parse-failure-flag-duplicate-flag=The given flag &b{0$flag$}&r can only be used once
+argument-parse-failure-flag-missing-argument=Missing argument for flag &b{0$flag$}
 argument-parse-failure-flag-no-permission=You are not allowed to use this flag
 missing-command-permission=You are not allowed to execute this sub command
 #

From 6cb5088f45ff6de9f8f9d3e1e6af44491b946ed8 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 23 Sep 2024 15:11:20 +0200
Subject: [PATCH 12/28] New translations en_us.properties (French) [ci skip]

---
 node/src/main/resources/lang/fr_FR.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/fr_FR.properties b/node/src/main/resources/lang/fr_FR.properties
index 99956f7779..c99f7dbe89 100644
--- a/node/src/main/resources/lang/fr_FR.properties
+++ b/node/src/main/resources/lang/fr_FR.properties
@@ -140,7 +140,7 @@ command-any-host-invalid=The given input {0$input$} is not a valid host address.
 #
 # Command Help
 #
-commnad-help-description=Shows all commands and their description
+command-help-description=Shows all commands and their description
 command-help-docs=Follow this url {0$url$} to get to the documentation for the {1$command$} command
 command-help-docs-no-url=The {0$command$} command has no documentation url
 #

From 66a695e72cfb5dcfb34ed4594563e41c79671ac4 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 23 Sep 2024 15:11:21 +0200
Subject: [PATCH 13/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 22 +++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index 756d250352..a8554db12c 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -117,17 +117,17 @@ invalid-command-sender=Dieser Befehl kann nicht von ''{0$source$}'' ausgeführt
 invalid-command-syntax=Ungültige Syntax\! Verwende {0$syntax$}
 no-such-command=Der Befehl konnte nicht gefunden werden\! Für Hilfe verwende den Befehl "help"
 argument-parse-failure-no-input-was-provided=Es wurde keine Eingabe gemacht
-argument-parse-failure-boolean=The given input &b{0$input$}&r is not a boolean
-argument-parse-failure-number=The given input &b{0$input$}&r is not a number
-argument-parse-failure-char=The given input &b{0$input$}&r is not a char
-argument-parse-failure-string=The given input &b{0$input$}&r is not a string
-argument-parse-failure-uuid=The given input &b{0$input$}&r is not an uuid
-argument-parse-failure-enum=The given input enum &b{0$input$}&r is not one of the following &b{1$values$}
+argument-parse-failure-boolean=Die Eingabe {0$input$} ist kein boolescher Wert
+argument-parse-failure-number=Die Eingabe {0$input$} ist keine Zahl
+argument-parse-failure-char=Die Eingabe {0$input$} ist kein Zeichen
+argument-parse-failure-string=Die Eingabe {0$input$} ist kein Text
+argument-parse-failure-uuid=Die Eingabe {0$input$} ist keine eindeutige Id
+argument-parse-failure-enum=Die Eingabe {0$input$} entspricht nicht einem der folgenden {1$values$}
 argument-parse-failure-regex=The given input &b{0$input$}&r does not match &b{1$regex$}
-argument-parse-failure-duration=The given input &b{0$input$}&r is not a duration
-argument-parse-failure-flag-unknown=The given flag &b{0$flag$}&r is unknown
-argument-parse-failure-flag-duplicate-flag=The given flag &b{0$flag$}&r can only be used once
-argument-parse-failure-flag-missing-argument=Missing argument for flag &b{0$flag$}
+argument-parse-failure-duration=Die Eingabe {0$input$} ist keine Zeitspanne
+argument-parse-failure-flag-unknown=Die gegebene Flag {0$flag$} ist unbekannt
+argument-parse-failure-flag-duplicate-flag=Die gegebene Flag {0$flag$} kann nur einmal genutzt werden
+argument-parse-failure-flag-missing-argument=Das Argument für die Flag {0$flag$} fehlt
 argument-parse-failure-flag-no-permission=Es ist dir nicht gestattet die Flag zu verwenden
 missing-command-permission=Es ist dir nicht gestattet diesen Sub-Befehl auszuführen
 #
@@ -140,7 +140,7 @@ command-any-host-invalid=Die Eingabe {0$input$} ist keine gültige Host-Adresse.
 #
 # Command Help
 #
-commnad-help-description=Zeigt alle Befehle und ihre Beschreibung an
+command-help-description=Zeigt alle Befehle und ihre Beschreibung an
 command-help-docs=Folge der Url {0$url$} um zur Dokumentation für den Befehl {1$command$} zu kommen
 command-help-docs-no-url=Der Befehl {0$command$} hat keine Dokumentations-Url
 #

From ff9667155962b05992d1034b5d65444ff931c8e2 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 23 Sep 2024 15:11:23 +0200
Subject: [PATCH 14/28] New translations en_us.properties (Russian) [ci skip]

---
 node/src/main/resources/lang/ru_RU.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/ru_RU.properties b/node/src/main/resources/lang/ru_RU.properties
index 11022eb8aa..e0c613d30a 100644
--- a/node/src/main/resources/lang/ru_RU.properties
+++ b/node/src/main/resources/lang/ru_RU.properties
@@ -140,7 +140,7 @@ command-any-host-invalid=The given input {0$input$} is not a valid host address.
 #
 # Command Help
 #
-commnad-help-description=Показывает все команды и их описание
+command-help-description=Shows all commands and their description
 command-help-docs=Перейдите по этому URL {0$url$}, чтобы получить документацию для команды {1$command$}
 command-help-docs-no-url=У команды {0$command$} нет URL-адреса документации
 #

From f61844c01f74c04cf6ac1d68a7abfb543f105fc2 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 23 Sep 2024 15:11:24 +0200
Subject: [PATCH 15/28] New translations en_us.properties (Luxembourgish) [ci
 skip]

---
 node/src/main/resources/lang/lb_LU.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/lb_LU.properties b/node/src/main/resources/lang/lb_LU.properties
index 99956f7779..c99f7dbe89 100644
--- a/node/src/main/resources/lang/lb_LU.properties
+++ b/node/src/main/resources/lang/lb_LU.properties
@@ -140,7 +140,7 @@ command-any-host-invalid=The given input {0$input$} is not a valid host address.
 #
 # Command Help
 #
-commnad-help-description=Shows all commands and their description
+command-help-description=Shows all commands and their description
 command-help-docs=Follow this url {0$url$} to get to the documentation for the {1$command$} command
 command-help-docs-no-url=The {0$command$} command has no documentation url
 #

From 2858a05e3b2ff4629bddcf219bc9c60d511cf9af Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 23 Sep 2024 16:15:28 +0200
Subject: [PATCH 16/28] Update source file en_US.properties [ci skip]

---
 node/src/main/resources/lang/en_US.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/en_US.properties b/node/src/main/resources/lang/en_US.properties
index 7e76a65918..b83795f33b 100644
--- a/node/src/main/resources/lang/en_US.properties
+++ b/node/src/main/resources/lang/en_US.properties
@@ -140,7 +140,7 @@ command-any-host-invalid=The given input {0$input$} is not a valid host address.
 #
 # Command Help
 #
-commnad-help-description=Shows all commands and their description
+command-help-description=Shows all commands and their description
 command-help-docs=Follow this url {0$url$} to get to the documentation for the {1$command$} command
 command-help-docs-no-url=The {0$command$} command has no documentation url
 #

From 42ac8581c43f96455554f82219b1dd68011796b5 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Sat, 28 Sep 2024 21:23:34 +0200
Subject: [PATCH 17/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index a8554db12c..2c0c263e36 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -123,7 +123,7 @@ argument-parse-failure-char=Die Eingabe {0$input$} ist kein Zeichen
 argument-parse-failure-string=Die Eingabe {0$input$} ist kein Text
 argument-parse-failure-uuid=Die Eingabe {0$input$} ist keine eindeutige Id
 argument-parse-failure-enum=Die Eingabe {0$input$} entspricht nicht einem der folgenden {1$values$}
-argument-parse-failure-regex=The given input &b{0$input$}&r does not match &b{1$regex$}
+argument-parse-failure-regex=Die Eingabe &b{0$input$}&r entspricht nicht dem Pattern &b{1$regex$}
 argument-parse-failure-duration=Die Eingabe {0$input$} ist keine Zeitspanne
 argument-parse-failure-flag-unknown=Die gegebene Flag {0$flag$} ist unbekannt
 argument-parse-failure-flag-duplicate-flag=Die gegebene Flag {0$flag$} kann nur einmal genutzt werden

From cc946c2556aa650615f74f11397182bc37c610ab Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Sun, 13 Oct 2024 17:14:50 +0200
Subject: [PATCH 18/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index 2c0c263e36..a890e026fe 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -117,17 +117,17 @@ invalid-command-sender=Dieser Befehl kann nicht von ''{0$source$}'' ausgeführt
 invalid-command-syntax=Ungültige Syntax\! Verwende {0$syntax$}
 no-such-command=Der Befehl konnte nicht gefunden werden\! Für Hilfe verwende den Befehl "help"
 argument-parse-failure-no-input-was-provided=Es wurde keine Eingabe gemacht
-argument-parse-failure-boolean=Die Eingabe {0$input$} ist kein boolescher Wert
-argument-parse-failure-number=Die Eingabe {0$input$} ist keine Zahl
-argument-parse-failure-char=Die Eingabe {0$input$} ist kein Zeichen
-argument-parse-failure-string=Die Eingabe {0$input$} ist kein Text
-argument-parse-failure-uuid=Die Eingabe {0$input$} ist keine eindeutige Id
-argument-parse-failure-enum=Die Eingabe {0$input$} entspricht nicht einem der folgenden {1$values$}
+argument-parse-failure-boolean=Die Eingabe &b{0$input$}&r ist kein boolescher Wert
+argument-parse-failure-number=Die Eingabe &b{0$input$}&r ist keine Zahl
+argument-parse-failure-char=Die Eingabe &b{0$input$}&r ist kein Zeichen
+argument-parse-failure-string=Die Eingabe &b{0$input$}&r ist kein Text
+argument-parse-failure-uuid=Die Eingabe &b{0$input$}&r ist keine eindeutige Id
+argument-parse-failure-enum=Die Eingabe &b{0$input$}&r entspricht nicht einem der folgenden {1$values$}
 argument-parse-failure-regex=Die Eingabe &b{0$input$}&r entspricht nicht dem Pattern &b{1$regex$}
-argument-parse-failure-duration=Die Eingabe {0$input$} ist keine Zeitspanne
-argument-parse-failure-flag-unknown=Die gegebene Flag {0$flag$} ist unbekannt
-argument-parse-failure-flag-duplicate-flag=Die gegebene Flag {0$flag$} kann nur einmal genutzt werden
-argument-parse-failure-flag-missing-argument=Das Argument für die Flag {0$flag$} fehlt
+argument-parse-failure-duration=Die Eingabe &b{0$input$}&r ist keine Zeitspanne
+argument-parse-failure-flag-unknown=Die gegebene Flag &b{0$flag$}&r ist unbekannt
+argument-parse-failure-flag-duplicate-flag=Die gegebene Flag &b{0$flag$}&r kann nur einmal genutzt werden
+argument-parse-failure-flag-missing-argument=Das Argument für die Flag &b{0$flag$}&r fehlt
 argument-parse-failure-flag-no-permission=Es ist dir nicht gestattet die Flag zu verwenden
 missing-command-permission=Es ist dir nicht gestattet diesen Sub-Befehl auszuführen
 #

From 2e6c646a908156e56948efd10e3ea3c438eafb35 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 21 Oct 2024 20:40:33 +0200
Subject: [PATCH 19/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index a890e026fe..5218127da1 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -257,7 +257,7 @@ command-groups-rename-success=Die Gruppe {0$group$} wurde erfolgreich zu {1$new$
 #
 # Tasks
 #
-cloudnet-load-task-unsupported-java-version=Der Java Befehl wird von Task {0$task$} entfernt da er keine valide Java-Installation ist oder nicht kompatibel mit Java 22 ist
+cloudnet-load-task-unsupported-java-version=Der Java Befehl wird von Task {0$task$} entfernt da er keine valide Java-Installation ist oder nicht kompatibel mit Java 23 ist
 #
 # Command Tasks
 #

From d48b82c4998f8002764a2cc51332d92e628e337a Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 21 Oct 2024 20:40:34 +0200
Subject: [PATCH 20/28] New translations en_us.properties (French) [ci skip]

---
 node/src/main/resources/lang/fr_FR.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/fr_FR.properties b/node/src/main/resources/lang/fr_FR.properties
index c99f7dbe89..44d9f4d9fd 100644
--- a/node/src/main/resources/lang/fr_FR.properties
+++ b/node/src/main/resources/lang/fr_FR.properties
@@ -257,7 +257,7 @@ command-groups-rename-success=The group {0$group$} was successfully renamed to {
 #
 # Tasks
 #
-cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 22
+cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 23
 #
 # Command Tasks
 #

From a5e6c16300165d5cbaa2e394865856ab227c55cd Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 21 Oct 2024 20:40:35 +0200
Subject: [PATCH 21/28] New translations en_us.properties (Russian) [ci skip]

---
 node/src/main/resources/lang/ru_RU.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/ru_RU.properties b/node/src/main/resources/lang/ru_RU.properties
index e0c613d30a..e3b192fce1 100644
--- a/node/src/main/resources/lang/ru_RU.properties
+++ b/node/src/main/resources/lang/ru_RU.properties
@@ -257,7 +257,7 @@ command-groups-rename-success=The group {0$group$} was successfully renamed to {
 #
 # Tasks
 #
-cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 22
+cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 23
 #
 # Command Tasks
 #

From adda00b2421268c2eae3200a3e73c249f40b413f Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 21 Oct 2024 20:40:36 +0200
Subject: [PATCH 22/28] New translations en_us.properties (Luxembourgish) [ci
 skip]

---
 node/src/main/resources/lang/lb_LU.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/lb_LU.properties b/node/src/main/resources/lang/lb_LU.properties
index c99f7dbe89..44d9f4d9fd 100644
--- a/node/src/main/resources/lang/lb_LU.properties
+++ b/node/src/main/resources/lang/lb_LU.properties
@@ -257,7 +257,7 @@ command-groups-rename-success=The group {0$group$} was successfully renamed to {
 #
 # Tasks
 #
-cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 22
+cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn''t a valid java installation or incompatible with Java 23
 #
 # Command Tasks
 #

From 6608994630973048d29159a90a4c8e13625a74a9 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Mon, 21 Oct 2024 21:35:48 +0200
Subject: [PATCH 23/28] Update source file en_US.properties [ci skip]

---
 node/src/main/resources/lang/en_US.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/en_US.properties b/node/src/main/resources/lang/en_US.properties
index b83795f33b..a32309620b 100644
--- a/node/src/main/resources/lang/en_US.properties
+++ b/node/src/main/resources/lang/en_US.properties
@@ -257,7 +257,7 @@ command-groups-rename-success=The group {0$group$} was successfully renamed to {
 #
 # Tasks
 #
-cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn't a valid java installation or incompatible with Java 22
+cloudnet-load-task-unsupported-java-version=Removing java command from {0$task$} because it isn't a valid java installation or incompatible with Java 23
 #
 # Command Tasks
 #

From 6fa44608c98dd2a735acbc40e78af44a90effc48 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 20 Dec 2024 21:28:40 +0100
Subject: [PATCH 24/28] Update source file en_US.properties [ci skip]

---
 node/src/main/resources/lang/en_US.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/en_US.properties b/node/src/main/resources/lang/en_US.properties
index a32309620b..1f40c3ee4d 100644
--- a/node/src/main/resources/lang/en_US.properties
+++ b/node/src/main/resources/lang/en_US.properties
@@ -175,7 +175,7 @@ command-cluster-start-sync=The cluster sync starts now
 # Command Service
 #
 command-service-description=Manages all services in the cluster
-command-service-copy-no-default-template=The service you provided does not have a default template, use "copy {0$name$} template=storage:prefix/name" to provide a template you would like to copy to
+command-service-copy-no-default-template=The provided service does not have a default template. To specify a template "service {0$name$} copy --template storage:prefix/name" can be used
 command-service-copy-success=The service {0$name$} was successfully copied to the template {1$template$}
 command-service-add-deployment-success=The deployment {0$deployment$} was successfully added to the waiting deployments
 command-service-deploy-deployment-success=The resources of the service were successfully deployed

From 0cc1facd3391e26add183ee080c9ca6a4fbb2b5f Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 20 Dec 2024 21:28:41 +0100
Subject: [PATCH 25/28] New translations en_us.properties (French) [ci skip]

---
 node/src/main/resources/lang/fr_FR.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/fr_FR.properties b/node/src/main/resources/lang/fr_FR.properties
index 44d9f4d9fd..4349184b96 100644
--- a/node/src/main/resources/lang/fr_FR.properties
+++ b/node/src/main/resources/lang/fr_FR.properties
@@ -175,7 +175,7 @@ command-cluster-start-sync=The cluster sync starts now
 # Command Service
 #
 command-service-description=Manages all services in the cluster
-command-service-copy-no-default-template=The service you provided does not have a default template, use "copy {0$name$} template\=storage\:prefix/name" to provide a template you would like to copy to
+command-service-copy-no-default-template=The provided service does not have a default template. To specify a template "service {0$name$} copy --template storage\:prefix/name" can be used
 command-service-copy-success=The service {0$name$} was successfully copied to the template {1$template$}
 command-service-add-deployment-success=The deployment {0$deployment$} was successfully added to the waiting deployments
 command-service-deploy-deployment-success=The resources of the service were successfully deployed

From 8cd0569c55bb13bb4629e9fa0591a518c19ae460 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 20 Dec 2024 21:28:43 +0100
Subject: [PATCH 26/28] New translations en_us.properties (German) [ci skip]

---
 node/src/main/resources/lang/de_DE.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/de_DE.properties b/node/src/main/resources/lang/de_DE.properties
index 5218127da1..adf8dc9dc2 100644
--- a/node/src/main/resources/lang/de_DE.properties
+++ b/node/src/main/resources/lang/de_DE.properties
@@ -175,7 +175,7 @@ command-cluster-start-sync=Die Cluster Synchronisation wird gestartet
 # Command Service
 #
 command-service-description=Verwaltet alle Services in dem Cluster
-command-service-copy-no-default-template=Der von Dir angegebene Service hat keine default Template. Benutze "copy {0$name$} template\=storage\:prefix/name" um ein Template anzugeben, in das du kopieren möchtest
+command-service-copy-no-default-template=Der angegebene Service hat kein default Template. Um ein Template anzugeben kann "service {0$name$} copy --template storage\:prefix/name" verwendet werden
 command-service-copy-success=Der Service {0$name$} wurde erfolgreich in das Template {1$template$} kopiert
 command-service-add-deployment-success=Das Deployment {0$deployment$} wurde erfolgreich zu der Warteschlange hinzugefügt
 command-service-deploy-deployment-success=Die Ressourcen des Services wurden erfolgreich deployed

From acd327494edeb95852252e99e93c9d048b42c1a4 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 20 Dec 2024 21:28:44 +0100
Subject: [PATCH 27/28] New translations en_us.properties (Russian) [ci skip]

---
 node/src/main/resources/lang/ru_RU.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/ru_RU.properties b/node/src/main/resources/lang/ru_RU.properties
index e3b192fce1..cbe0ababf5 100644
--- a/node/src/main/resources/lang/ru_RU.properties
+++ b/node/src/main/resources/lang/ru_RU.properties
@@ -175,7 +175,7 @@ command-cluster-start-sync=Синхронизация кластера начи
 # Command Service
 #
 command-service-description=Управляет всеми сервисами в кластере
-command-service-copy-no-default-template=У сервисов, которую вы предоставили, нет шаблона по умолчанию, используйте "copy {0$name$} template\=storage\:prefix/name" для указания шаблона, который вы хотели бы скопировать
+command-service-copy-no-default-template=The provided service does not have a default template. To specify a template "service {0$name$} copy --template storage\:prefix/name" can be used
 command-service-copy-success=Сервис {0$name$} успешно скопирован в шаблон {1$template$}
 command-service-add-deployment-success=Развертывание {0$deployment$} успешно добавлено в ожидающие развертывания
 command-service-deploy-deployment-success=Ресурсы сервиса успешно развернуты

From cfe63ea21bc669443f1310f472732e9af64d3ec6 Mon Sep 17 00:00:00 2001
From: CloudNetService Automation <github@cloudnetservice.eu>
Date: Fri, 20 Dec 2024 21:28:45 +0100
Subject: [PATCH 28/28] New translations en_us.properties (Luxembourgish) [ci
 skip]

---
 node/src/main/resources/lang/lb_LU.properties | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/node/src/main/resources/lang/lb_LU.properties b/node/src/main/resources/lang/lb_LU.properties
index 44d9f4d9fd..4349184b96 100644
--- a/node/src/main/resources/lang/lb_LU.properties
+++ b/node/src/main/resources/lang/lb_LU.properties
@@ -175,7 +175,7 @@ command-cluster-start-sync=The cluster sync starts now
 # Command Service
 #
 command-service-description=Manages all services in the cluster
-command-service-copy-no-default-template=The service you provided does not have a default template, use "copy {0$name$} template\=storage\:prefix/name" to provide a template you would like to copy to
+command-service-copy-no-default-template=The provided service does not have a default template. To specify a template "service {0$name$} copy --template storage\:prefix/name" can be used
 command-service-copy-success=The service {0$name$} was successfully copied to the template {1$template$}
 command-service-add-deployment-success=The deployment {0$deployment$} was successfully added to the waiting deployments
 command-service-deploy-deployment-success=The resources of the service were successfully deployed