Skip to content
This repository has been archived by the owner on Nov 14, 2021. It is now read-only.

Version 2.2.2
Compare
Choose a tag to compare
@derklaro derklaro released this 21 May 17:55
Version-2.2.2
8bf063d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

[*] Fixed all known bugs
[*] Improved ingame messages
[*] Improved the hole network system

[+] Complete rework of the permission system with a lot of new features
[+] Complete rework of proxy application
[+] Prefix/Suffix/Display/Color support per permission user and group
[+] Tab and Chat plugin extension for the permission system
[+] Kick message if the player is already connected to another proxy

🔴 Furthermore, we have done a lot of code updates and tested them as much as possible, we apologize, but if there are problems after the update please report them by opening an issue and we will take care of them as soon as possible!

⚠️ Important information for performing the update:

[*] Due to some considerations and updates of the network system some API functions have been removed. This is the Client Sync/Async api, as well as the Application sync/async api

Maven:

📌 ReformCloud is available in the central repository (no repository specification in pom.xml is needed)

General api (for all executors):

        <dependency>
            <groupId>systems.reformcloud.reformcloud2</groupId>
            <artifactId>reformcloud2-executor-api</artifactId>
            <version>2.2.2</version>
            <scope>provided</scope>
        </dependency>

Permission system (executor specific implemented):

        <dependency>
            <groupId>systems.reformcloud.reformcloud2</groupId>
            <artifactId>reformcloud2-default-application-permissions</artifactId>
            <version>2.2.2</version>
            <scope>provided</scope>
        </dependency>

Sign system (Executor specific implemented):

        <dependency>
            <groupId>systems.reformcloud.reformcloud2</groupId>
            <artifactId>reformcloud2-default-application-signs</artifactId>
            <version>2.2.2</version>
            <scope>provided</scope>
        </dependency>

🔗 The most important links:

➥ Download: https://dl.reformcloud.systems/latest/ReformCloud2.2.2.zip
➥ Addons: https://dl.reformcloud.systems/addonsv2/
➥ Plugins: https://dl.reformcloud.systems/plugins/
➥ SpigotMC: https://www.spigotmc.org/resources/reformcloud-v2.63950/

⚠️ Important information: ⚠️

🇺🇸
The intention at that time to add support for client/controller (master/wrapper) to the cloud in addition to the "new" node system was that this system was then much more common than clustering. As it turned out after many months of testing and working on the cloud, the client/controller system simply always represents a considerable additional effort, which is not worthwhile in the long run, because with clustering you can get much more potential for your network. Furthermore, there are more users of the node system as well as the controller/client system and also in the support and during the first setup of the cloud, the node system is always recommended directly.

Now it is time to remove the controller/client. For some networks this will mean that an upgrade is necessary which should be purchased to ensure the best possible functionality of the system (also from the team side). Therefore we are announcing the end-of-life for the controller/client system, and will remove it when we release version 2.X.

To all who use the client/controller system:
It is recommended to update from the client/controller system to the node system before updating to 2.X (which will be released in 1-2 months) to avoid stress when releasing the new version.

🇩🇪
Die damalige Intention neben dem "neuen" Node System auch Support für Client/Controller (Master/Wrapper) in die Cloud hinzuzufügen war die, dass dieses System damals sehr viel verbreiteter war als Clustering. Wie sich doch nach vielen Monaten der Tests und des Arbeitens an der Cloud herausgestellt hat, stellt das Client/Controller System einfach immer nur einen erheblich Mehraufwand dar, welcher sich auf dauer nicht lohnt da man mit clustern erheblich mehr Potenzial für sein Netzwerk herausholen kann. Des Weiteren gibt es mehr Nutzer des Node Systems wie des Controller/Client Systems und auch im Support und direkt beim ersten Setup der Cloud wird einem das Node System immer direkt empfohlen.

Nun ist es an der Zeit Controller/Client zu entfernen. Dies wird für einige Netzwerke bedeuten, dass ein Upgrade nötig ist welches jedoch in kauf genommen werden sollte um die bestmögliche Funktionalität des Systems sicherstellen zu können (auch von der Seite des Teams). Daher kündigen wir hiermit das End-Of-Life für das Controller/Client System an, und werden es beim Release der Version 2.X entfernen.

An alle die das Client/Controller System nutzen:
Es ist empfehlenswert bereits vor dem Update auf die 2.X (welche erst in 1-2 Monaten erscheinen wird) in Ruhe das Update vom Client/Controller System auf das Node System durchzuführen um beim Release der neuen Version nicht in Stress zu geraten.

Assets 3
Loading