shawiizz / mohistessentialsx

Do not blindly trust EssentialsX! The reasons why you shouldn't trust what EssentialsX says about Mohist are all explained on this README.

About the PSA written by EssentialsX

Why EssentialsX's PSA about Mohist shouldn't be trusted.

Before reading:

• I don't natively speak English, so this article may contain spelling errors, I'm sorry for that.
• A few months ago, the EssentialsX plugin was properly fixed into Mohist and the modified plugin isn't needed anymore.
• EssentialsX original page: https://essentialsx.net/do-not-use-mohist.html
• Mohist's organization: https://github.com/MohistMC
• "we" and "us" = The Mohist project or Mohist team.
• I'm writing this as a Mohist admin.

Context

Mohist is a Forge + Bukkit/Spigot/Paper hybrid which allows you to run mods and plugins at the same time. This software is currently in beta and may contain bugs. This README has been written to correct errors and misinformation disseminated in that PSA. Everything that is said in this README is proven and can be verified by yourself if you wish.

Know that you're free to not use or not support Mohist. This README just explains the errors made on the EssentialsX page.

Explanations

Let's start

Yes, Mohist can replace with your permission the EssentialsX plugin with a modified one made by us to temporarily fix an incompatibility between EssentialsX and Mohist until we find a proper way to fix it on our side. This modified plugin allows users to use EssentialsX on Mohist without incompatibilities. Also, this modified plugin source code is available on Github and it has always been the case. Plus, you're free to check its source code and what has been modified in the code, by looking at the commits. Note: The repository has been marked as archived, but it still contains the modified code so that you can check it if needed.

Bukkit and Forge compatibility

Yes, Bukkit and Forge aren't made to be compatible, but the aim of Mohist is to resolve this incompatibility with as few bugs as possible. Of course, it's not possible to make a Forge + Bukkit software without any bugs, and it's very hard to create hybrid server software as there is no way to properly implement the Bukkit API on top of Forge without modifying it. Also, know that we do our best to make Mohist a stable, bug-free, and cleanly coded software.

Mohist potential issues

The first issue (Injecting block/item types added by Forge into the Bukkit Material enum twice) doesn't exist anymore and has been fixed since the creation of Mohist 1.16.5.

The second issue exists, and it's how Forge works. Forge re-creates the player instance when a player dies and it's hard to change that without breaking Forge mods compatibility. But again, we are doing our best to think about a way to patch this problem without breaking mod compatibility. Of course, this issue can break some plugin compatibility, but keep in mind that Mohist is based on Forge and not Bukkit.

Plugin checker

The Mohist's plugin checker has been made to temporarily fix a plugin which doesn't work well with Mohist until we find a proper way to fix it. Of course, it always asks for your permission (and this has always been the case since its creation) before downloading a modified plugin.

We now know it, this text was not clear and we are sorry for that, it was not our intention. As you may know, our team does not contain any native English speakers, so it is difficult for us to write clear messages, even though we make every effort to make it as clear as possible to everyone. Fortunately, our community has been able to help us correct this problem.

Actually, this text doesn't mean the bug comes from EssentialsX. It means the plugin cannot work due to an incompatibility on Mohist's side and ask the user if he allows the Mohist software to download a modified version of this plugin (temporarily) to make it work fine with Mohist, and I insist on the fact that it requires the user's agreement and that it has always been the case. Also EssentialsX is properly fixed in Mohist and doesn't need the modified plugin anymore for a long time.

Secondly, Mohist never run any untrusted code as the code of modified plugins is always published on GitHub and shows what has been modified in the plugin's code. That message actually misses some information, like the repository URL, what has been changed and fixed, etc., and it has been fixed there. This is explained in our Discord server, but not everyone can go to our Discord server and we solved this problem by adding more details to that message, and we hope it is now clearer for everyone.

Plus, know that we never and will never use this plugin checker to download anything malicious. You are free to check what is downloaded with the plugin checker as Mohist is free and open source on GitHub, fixed plugins source code is always published in GitHub and you can also decide if you want to download the modified plugin or not. And to finish, you can even disable the plugin checker by setting disable_plugins_blacklist to true in mohist-config/mohist.yml.

More explanations

To conclude this README, making Forge and Bukkit API work together is really difficult and today no one achieved to do it without any bugs. The EssentialsX team doesn't know how hard is it to code a hybrid software, and we understand it.

But we also have a few things to say about EssentialsX and its team. They're often saying that we did things wrong and did not make any effort, but on their side, they did not make any effort either. Instead of coming to discuss with the Mohist team as any other team would have done as civilized people, they decided to try to destroy the reputation of our software, which is totally shameful and shows a deep lack of communication on their part. Not only does their PSA spread false ideas and information, but it is also a lie to their community, which poses a trust issue with their team. Moreover, their reasons for hating hybrids are not very well thought out. Yes, Forge and Bukkit are not made to work properly, but if we don't try to solve this problem, who will? We also know there are good people on their team, but unfortunately, the behaviour of some of them was not as we would have liked.

Again, we are really sorry if the plugin checker's message couldn't be understood correctly, and we hope this README will make everything clearer for everyone. Furthermore, even after these events, we have never and will never prevent users from using EssentialsX, as it is not our intention to do so. To finish with this article, know that we always care about the security of our users and that it's an important thing for us and above all our priority.