MaxLananasMods, plugins and Axiom addons: where my tools run
On this page
A Minecraft tool can have a familiar-looking interface while running in a completely different place from another tool. Before downloading a JAR, work out whether it belongs on your client, on the server, or inside the environment of another mod. This guide uses projects from my portfolio to make those boundaries concrete.
A quick comparison
| Project | Runs in | Important boundary |
|---|---|---|
| HomeGUI | Fabric client | The server still owns the home commands and permissions. |
| TraceBTE | Paper server | The tutorial needs the documented server tools. |
| Railway Tools | Fabric client with Axiom | Axiom is a separate required dependency. |
| BTE calculator | Browser | Projection inputs and model state affect interpretation. |
| Riptide | Browser (server-side conversion) | Conversion remaps blocks; read the equivalence report before using the result. |
A client mod can organize information without owning the server feature
HomeGUI is a useful example. It reads a server’s response to /homes and makes the destinations searchable in a client interface. Its installation belongs in a matching Fabric setup, but the underlying teleportation behavior belongs to the server.
The practical question before installing: does your server already provide the command this interface organizes? If it does not, a client mod cannot add it, and a server-side plugin or a different server configuration is the right layer.
A server plugin changes the shared server environment
TraceBTE runs inside a Paper server and guides builders through a tracing sequence with server commands. Everyone connected to that server experiences the tutorial, and the server owner controls installation, permissions and versions.
Server-side also means server-side responsibilities: Java and FastAsyncWorldEdit versions, restarts after installation and compatibility with the rest of the plugin list are part of the documented setup.
An addon depends on the host tool it extends
Railway Tools for Axiom is neither a standalone mod nor a server plugin: it extends Axiom’s builder environment with a rail-path tool. Axiom remains a separate required dependency with its own installation and permissions.
When comparing tools, name the host environment explicitly. An addon’s requirements include the host mod’s version, which is why the project page lists Fabric, Fabric API and Axiom together.
Some building tools do not run inside Minecraft at all
The BTE Distorsion Calculator runs in a browser and explores projection scale with geographic inputs. BuildersUtilities-style server plugins, PineappleUI’s transpiler and other repository tools each live in their own runtime.
Keeping those boundaries visible prevents the most common installation mistake: placing a file in a mods or plugins directory when the project documents a different environment entirely.
Before installing or reporting a problem
- Identify where the project runs: client, server, host addon or browser.
- Check its current Minecraft, Java, loader and dependency requirements.
- Distinguish the tool’s interface from permissions and services controlled elsewhere.
- Test a small, reproducible case and include version information in an issue.
- Read the project’s source and license, including upstream credits for a fork.
These are distinctions supported by the linked project documentation, not compatibility guarantees for future releases. Start from the development catalogue and follow the current repository links for installation details.