By looking that you are here you most likely use Cardboard/Banner/some other weird bukkit + Fabric project (or just someone linked to it).
Don't do it, it will cause more harm/instabilities to your server than good. But let's start at the beginning.
Few definitions before we start:
- Bukkit - It means bukkit, spigot, paper and any forks of these,
- Cardboard - mod by IsaiahPatton that tries to port bukkit ecosystem to fabric.
- Banner - another mod trying to make plugins work with Fabric, similar to Cardboard.
- Fabric - a Minecraft modding platform, includes Fabric Loader and Fabric API, everything written in this gist also applies to Quilt.
- Mods - Mods designed for fabric and compatible platforms
- Plugins - Mods/plugins designed for bukkit/spigot/paper or their forks.
Mods being mods, they can modify game in substantial way. New blocks, items, mobs, etc. Possibilities are more or less endless as long as there is good enough programmer behind it. However, most mods still are kept compatible with each other, as they use tools designed for that (including Minecraft's internals, which allow for quite good compatibility) and having many gameplay mods is a norm.
Bukkit plugins on the other hand, while also normally compatible with each other, aren't really designed for custom blocks/items/etc. There are plugins that try to emulate mods with custom items/blocks/etc (for example Slimefun or ItemAdder), but they are mostly facade over vanilla items with some additional nbt. Because of that there are no issues most of the time (until other plugins don't try to use these items that is, as they see them as vanilla ones).
However, when you start mixing bukkit with fabric, bad things can easily happen. Fabric is close to Minecraft internal code (which has lots of nice and powerful stuff), while Bukkit is mostly an API which most of it's parts and design not being updated since 1.7. This means, you might need to make lots of conversions (with some not really possible without losing some functionality, for example messages in bukkit are just strings using legacy formatting, but mods use vanilla's more advanced json text for formatting). And if you start including things like non vanilla items, blocks and entities, it starts to break even more. Bukkit based server software is also known to break datapacks, which makes it even more likely to not work with mods (as a lot of them use and expend datapack funtionality).
Cardboards approach is more or less taking bukkit code and hitting it with a hammer until it starts to barely works. It uses lots of hacks, code overriding entire methods in Minecraft (breaks lots of mods mixing into them!) and breaking vanilla behaviour. It's also questionable license wise, as GPL isn't really compatible with Minecraft code (and for this reason spigot and others use workarounds to bypass it). Additionally, it needs to modify some plugin on runtime to make them work, which only shows how bukkit wasn't designed for that usage. This mod will never be in a state stable enough to work with more advanced plugins while also not causing other mods to break or straight up crash. Most of the time developers of incompatible mods and plugins won't support it anyway as these mixed environments were always hacky and problematic, so it's safer and stabler to just use fabric alternatives.
In similar way of cardboard, to support bukkit api and plugins using it, it needs to make a lot of invalive changes to make things work. Which will also break a lot of mods (and plugins). It also is known to modify/swap plugins to make them work, so it's not even doing it's job properly (see https://essentialsx.net/do-not-use-mohist.html)
This is more of my own opinion (through it's shared by many), that bukkit based plugins and servers should be thing of the past. Bukkit (or Spigot and Paper) never fully adapted to modern Minecraft, as their goal of forever backwards compatibility limited how they could evolve. Bukkit was originally created for early Minecraft Betas and it's api was kept mostly the same. It was extended with new functionality, but it never fully adapted to modern versions. Lack of nbt api's, lack of support for datapacks as parts of plugins (which both non-bukkit platforms have supported for long time), it limits what could be done with server mods. Nearly all plugins that do something more advanced, require usage of non-bukkit Vanilla classes, either via another library or own code (and a lot of reflections and jvm hacks). For bigger servers that want to extend gameplay in their own ways, it's more common to just fork Bukkit/Spigot/Paper instead and add things in same ways as modders do.
You should check out this list of server side fabric/quilt mods. There is lots of alternatives to pick, with even more being actively created!
If you are create mods or plugins you are also free to ask me about anything related, as I'm always happy to help people expand Fabirc/Quilt server side ecosystem :)
You should also checkout these server side communities:
- Fabric Server Side Development: https://discord.gg/atSzZ6zMHz
- Patbox's Discord: https://discord.gg/AbqPPppgrd
- Fabric/Quilt Server Tools: https://discord.gg/p56NJ6kp4u
Or modded ones in general:
- The Fabric Project: https://discord.gg/v6v4pMv
- The Quilt Community: https://discord.quiltmc.org/
You say this, but then previously you said:
...let me explain this to you so that a non-dev user will understand.
Forge MODIFIES the original Minecraft server. It injects a lot of new code for Events, particularly. Bukkit/Paper/etc. also do the same.
Forge and Bukkit can go "outside the API" via Mixins for example - this is where the REAL modding happens these days. But the problem here is that a dev for Forge and Bukkit is working against Forge and Bukkit proper, not Mohist. Mohist has additional changes to the Minecraft code that an individual Forge or Bukkit dev will likely not be aware of, because the dev themselves aren't working against Mohist (why would they bother).
Also, now that Forge is "dead" and essentially replaced with NeoForged, "coremodding" and Mixins are no longer naughty - so this problem is only going to get much worse for Mohist.
The latest server from the Paper team, Folia, touts itself as a fully-multithreaded version of Paper fork, but it can't even support datapacks IIRC, let alone have support for literally any custom content... the Bukkit-side has dug itself into the ground, giving the outward appearance of Minecraft "purists" as far as I'm concerned; and I think this is a self-destructive attitude to take considering that their community doesn't actively adopt newer Minecraft versions. It's like they're literally living in the past, refusing to adapt to the changing times.
As a dev myself, Fabric/Quilt honestly seems to be the way of the future.
As only a user, I am puzzled as to why you support Mohist when it literally gives you zero advantage. The official Minecraft server might not be open source, but it is free as in cost - so why does it matter to users?
Your claim that we are "full-on hating" can just as easily be countered with the claim that you are "full-on shilling" for Mohist, tbh, but I am not making that claim - don't get me wrong.
It's just that this article is geared for mod/plugin developers in a effort to get more to join the future in Fabric or Quilt, rather than wasting their talent on dead-end "we can do better than Mojang" type attitudes.
Sooooo many of these custom servers have come and gone in the past, and Mohist is like the 3rd OSS implementation I've seen over the years. Granted it's been more successful than the others have, but history has proven that these projects just cannot last because of how much technical debt they incur by trying to bridge two completely different philosophies of Minecraft content creation.
Mohist seems to have a very limited use case - people who want to make their own server but have zero development ability. I mean what is the actual point of it from a dev's PoV, considering how easy it is to port Bukkit plugins to Fabric or Forge?