Crafters.one prioritizes a vanilla gameplay experience, however to preserve a stable and functional multiplayer environment, the server implements select modifications to vanilla game mechanics. While these changes are typically subtle and minimally affect gameplay, they are fully documented here. Each entry includes the change details, technical implementation, gameplay impact, and the rationale behind the modification.
Non-Vanilla Game Mechanics
Below is a complete list of all server-side mechanics that differ from standard Minecraft.
Each section outlines what changed, how it works, and why it exists.
100% Explosion Block Drop Chance
| Category
|
Game Rules
|
| Affected Version(s)
|
1.16+
|
| Status
|
✔ Active
|
| Summary
|
All explosions (TNT, Creeper, etc.) will result in all destroyed blocks being dropped as items (unless the block does not normally drop an item).
|
| Implementation
|
Utilizes the vanilla Game Rule to set the explosion block drop chance to 100%.
|
| Rationale
|
Allows creeper holes to be easily repaired, and prevents unintentional griefing of builds by creepers/ghasts, by allowing the player to repair it with the dropped blocks.
|
Fire Spread Disabled
| Category
|
Game Rules
|
| Affected Version(s)
|
1.18+
|
| Status
|
✔ Active
|
| Summary
|
Fire Spread is disabled in all dimensions, to prevent intentional or unintentional griefing of flammable builds.
|
| Implementation
|
Utilizes the vanilla Game Rule to disable the mechanic.
|
| Gameplay Effects
|
Fire will not naturally burn out on any block, however it will not remove any blocks that it is burning on or near, regardless of flammability. Lava will not spread fire.
|
| Rationale
|
Many builds are made of flammable material for decorative/appearance purposes. Given the level of experience of most players, fire spread acts as more of an inconvenience than a challenge.
|
Locator Bar Disabled
| Category
|
Game Rules
|
| Affected Version(s)
|
1.21.7+
|
| Status
|
✔ Active
|
| Summary
|
The Locator Bar is disabled, to maintain privacy of players' locations.
|
| Implementation
|
Utilizes the vanilla Game Rule to disable the feature.
|
| Rationale
|
It is unnecessary and exposes players' locations without their consent.
|
Converted Drowned spawn with Tridents
| Category
|
Mobs
|
| Affected Version(s)
|
1.17-1.18
|
| Status
|
✘ Removed
|
| Summary
|
Zombies that drown to convert into Drowned occasionally spawn with Tridents.
|
| Implementation
|
Utilized a datapack.
|
| Rationale
|
Drowned spawning was considered to be too rare and inconvenient.
|
| Removal
|
Removed to restore vanilla behavior; this modification was deemed unnecessary.
|
Paper Server Software Note
Crafters.one utilizes the Paper server software, which contains "optimizations" to server peformance that changes certain vanilla mechanics. This may be evident in complex redstone contraptions or machines that rely on specific entity ticking mechanics. These specific changes are unable to be listed here, due to their frequent changes and inconsistencies. If you encounter an issue with a machine that works properly in Vanilla, it is likely that Paper may be causing issues with it. If you believe there is a configuration change or patch/plugin that may restore vanilla functions without major downsides, feel free to open a ticket. Please note, however, you must determine the specific solution (config change, plugin, patch) yourself; the volunteer team and game masters are unable to research issues with Paper on your behalf if your contraption isn't working. You must determine the root cause within Paper via your own testing on a local Paper server by trying different config settings, or potentially by reviewing Paper source code to identify the patch or line(s) of code causing the issue. This can require advanced knowledge of server software/programming so it is recommended to instead opt for a different machine/contraption that uses more common mechanics. (It is understood this is not ideal, but there are currently no sufficient alternatives to the Paper server software and plugins for Crafters.one's use case.)