Chore: Paper migration

[Quentixx]

Context

The Minestom library ultimately does not meet our needs from a maintainability point of view.
After some consideration, @Distractic, @bananasmoothii and I agreed to migrate the library to PaperMC which is a fork of the Spigot project.

Benefits

• Maintainability of the project over time
• Development team already at ease with the library
• Basic server behaviors required
• Stability

Disadvantages compared to Minestom

• Loss of performance
• Unit Tests
• Packet handling
• Not fully open-source

Objective of the PR

• Adapt the code initially designed under Minestom to PaperMC
• Review the tests

[bananasmoothii]

Maybe we can make some parts with minestom and some other parts with paper and like both with a proxy (velocity for instance) because minestom is much cheaper when it comes to hosting as it requires less performance

[Quentixx]

It's an interesting idea but it requires redesigning the API to handle PaperMC and Minestom.

It should be clarified in which use cases Minestom is preferable:

• Hub - Minestom
  • 👍 Because the hub server by design does not affect pvp
  • 👍 The scoreboard is very cool to handle
  • 👍 The food supporting is not necessary

  ---

  • 👎 Currently, the mount system is bugged (move + jump) https://github.com/Rushyverse/hub/blob/feat/mount/src/main/kotlin/fr/rushy/hub/command/PigCommand.kt
  • 👎 For the Guild system, I want to do a banner customizable system (pattern + colors), I did not find how to do this under Minestom

---

• Pvpbox - Paper
  • 👍 The current dev of this project (@cizetux) is more comfortable with Bukkit based environnement
  • 👍 Not necessary to add any PvpExtension

  ---

  • 👎 Need to cancel some events (FoodLevelChange, WeatherChangeEvent, ...) while Minestom saves us from doing this

---

• GameIdea1 - Paper/Minestom ❓
  • 📦 I think It depends if the game concept is built around interactions between players (stability & user experience is important)

---

I haven't thought of all cases, tell me what do you think @bananasmoothii

[bananasmoothii]

Yes, that is probably a good way. The connection between servers could be made via redis

[Distractic]

Having two types of server (Minestom and Spigot) is a real challenge and requires a lot of work. Because when you have to implement a feature on one, you will probably have to implement it on the other. This will require having two APIs to maintain.

Concerning the communication between the servers, whatever the type, the servers will be able to communicate between them using the proxy and to send messages to each other using redis

[Quentixx]

In conclusion, we will therefore stick to our choice to migrate to full PaperMC, to avoid a substantial workload.

To our keyboards!

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

61.3% Coverage
0.3% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint