Plugins
Understand why SoulFire plugins are Fabric mods and what that means for compatibility and extension.
SoulFire 2.0: Built on Fabric
SoulFire 2.0 was a complete rewrite that transformed SoulFire into a special Fabric mod running the official Minecraft client code. SoulFire plugins are Fabric mods and are loaded using the standard Fabric mod loader.
This architectural choice changes how you should think about extending SoulFire.
Why Fabric?
- Perfect vanilla parity: SoulFire bots use the exact same code as the official Minecraft client, so they behave identically to real players on the server side
- Accurate physics and movement: Bot movement, action prediction, and collision detection are 100% accurate since they use Minecraft's actual physics code
- Protocol parity: Network communication matches the real client exactly, making bots effectively undetectable by anticheats
- Faster version updates: Supporting new Minecraft versions is significantly easier and faster since the Minecraft code is already present
- Rapid feature development: New features can be implemented quickly by building on top of existing Minecraft code
- Third-party mod support: Some existing Fabric mods can work with SoulFire out of the box
Plugins are Fabric mods
Important: SoulFire plugins are now standard Fabric mods. They are loaded by the Fabric mod loader just like any other Fabric mod.
Since SoulFire plugins are Fabric mods:
- Plugins follow the standard Fabric mod structure (
fabric.mod.json, entrypoints, etc.) - Plugins are loaded from the
minecraft/modsdirectory by the Fabric mod loader - Plugins can use Mixins to modify both Minecraft and SoulFire code
- Plugins have full access to the Minecraft codebase and Fabric APIs
- Some existing Fabric mods may be compatible with SoulFire without modification
This power is meant for advanced users. If visual automation is enough, stay in Scripting. Move to Development when you need Mixins, packet hooks, custom settings pages, or direct access to Minecraft and SoulFire internals.
Built-in plugins vs community plugins
- Built-in plugins ship with SoulFire and can be enabled or disabled per instance.
- Community plugins are external Fabric mods that you add yourself.
- Both use the same underlying Fabric loading model.
For the current built-in list, see Built-in Plugins.
Compatibility expectations
Some Fabric mods work with SoulFire without modification, but compatibility is not universal.
- Mods that depend on rendering, audio, or other client-only features usually do not work.
- Mods that change gameplay logic, networking, inventory behavior, or automation are more likely to work.
- Mixins can touch both Minecraft code and SoulFire code, so plugin power comes with plugin risk.
Writing plugins
Any questions regarding how SoulFire works and how to write a plugin can be asked in the Discord.
The short version:
- Start from the official SoulFirePluginExample template
- Add the current SoulFire dependencies from CodeMC Maven
- Register your plugin with
SoulFireAPI.registerServerExtension(...) - Build a standard Fabric mod jar and place it in
minecraft/mods
For the real developer workflow, use the new Development section. It covers environment setup, Gradle, settings pages, the event system, bot control, Mixins, access wideners, internal architecture, and the current Javadocs and source references.
Related pages
- Development for the full plugin-authoring documentation
- Install Plugins for the practical install steps
- Built-in Plugins for the built-in list
- Resources for community plugins and scripts
How is this page?
Last updated on