Understanding the FallingOverride Plugin
Minecraft’s sand duplication mechanic has been a staple of technical gameplay for years. Using clever setups with end portals, players could duplicate sand, gravel, concrete powder, anvils, and even dragon eggs. This wasn’t just a quirky exploit — it became an essential resource-gathering method for ambitious builders and redstone engineers. However, many modern server forks like Paper and Spigot patched this behavior to improve performance and prevent unintended item generation, leaving players without a legitimate way to duplicate falling blocks. The FallingOverride plugin steps in to restore that functionality in a controlled, configurable manner.
What FallingOverride Does
FallingOverride is a lightweight server plugin designed specifically for Spigot, Paper, and similar forks where vanilla falling block duplication has been disabled. Instead of altering core game code, it listens for falling block entities that land near an end portal and, when conditions are right, spawns a corresponding item entity that falls into the portal. This effectively mimics the vanilla duplication outcome without re-enabling the original bug. The plugin is intended exclusively for servers where the duplication mechanic is patched; using it on a vanilla server or one that already allows duplication will cause double-duping, so caution is advised.
Why Use FallingOverride?
Many technical players rely on sand duplication for concrete production, glass, and TNT in large-scale projects. When server software removes this feature, it can disrupt long-established workflows and force players to manually mine vast amounts of sand, gravel, or other falling blocks. FallingOverride bridges the gap between server stability and player convenience. It allows server owners to keep the performance benefits of Paper or Spigot while giving their community the familiar duplication mechanics they expect. The plugin is also highly configurable, letting operators enable or disable duplication for specific block categories.
Commands and Configuration
Server operators can manage the plugin with a simple command. The syntax is:
/falling [block type] [enable/disable]
Running /falling without arguments displays the current status of all block types. The permission node falling.cheat is required to use the command, ensuring only trusted staff can adjust settings.
Block Type Categories
The plugin groups falling blocks into four distinct types, each independently toggleable:
- sand – includes regular sand and red sand
- anvil – covers anvil, chipped anvil, and damaged anvil
- dragon egg – the dragon egg only
- decorative – all other falling blocks: gravel, concrete powder (all colors), and similar
By default, sand and decorative types are enabled, while anvil and dragon egg are disabled. This default setup reflects common server preferences — sand duplication is widely accepted, but anvil and dragon egg duplication can be seen as too powerful or economy-breaking. Operators can easily flip these defaults to match their server’s style.
How the Duplication Mechanic Works
The plugin’s logic is straightforward. It monitors falling block entities (like sand entities) that are moving toward an end portal block. When such an entity lands adjacent to the portal, FallingOverride checks if that block type is enabled. If all requirements are met, it creates an item entity of the same material and applies a velocity that sends it into the portal, just as the original duplication would. The item then travels through the portal to the designated dimension (usually the End or Overworld), where it can be collected by a hopper or player.
This approach has been tested with popular duplicator designs, including RaysWorks’ sand duplicator and Shulkercraft’s dragon egg duplicator. The plugin works seamlessly with these builds on Paper servers. For version 1.18.2, a minor adjustment to the RaysWorks design is needed — details can be found in the video description of the original tutorial. The 1.17 version of FallingOverride remains functional on 1.18 servers, while the 1.18 release offers only cosmetic updates and has been verified on the latest Paper 1.18.2 build.
Installation and Compatibility
Adding FallingOverride to your server is as simple as dropping the .jar file into the plugins folder and restarting (or using a plugin manager to reload). It requires no additional dependencies and works out of the box. For players who enjoy modded or plugin-enhanced experiences, managing such additions can be streamlined with a modern launcher. For instance, the foxygame.net launcher offers a convenient way to browse and install mods directly from its menu, making it easy to keep your client in sync with server-side plugins like FallingOverride. This flexibility is especially useful when switching between different servers that may have unique plugin setups.
Important Notes and Warnings
Before deploying FallingOverride, server admins must understand its intended use. The plugin is designed solely for servers where falling block duplication is patched. Installing it on a vanilla server, or any fork that still permits the vanilla duplication, will result in double-duping — each falling block will produce two items instead of one. This can quickly unbalance a server’s economy and create item floods. Always verify your server software’s behavior before enabling the plugin.
Additionally, while the plugin restores duplication, it does not alter the underlying game code. It simply adds a listener that spawns items under specific conditions. This means it is safe for server performance and won’t introduce lag spikes. The author, longbread, has kept the code minimal and focused, ensuring compatibility with future Paper/Spigot updates as long as the falling block entity behavior remains unchanged.
Community Feedback and Future Improvements
FallingOverride was built with community input in mind. The developer welcomes suggestions on how to refine the plugin, whether it’s adding new block categories, improving detection logic, or offering per-player permissions. The current version already covers the most requested falling blocks, but niche cases like custom falling block entities from other plugins could be considered in future updates. Server owners who adopt FallingOverride often find it becomes an invisible but essential part of their technical ecosystem, quietly enabling creativity without compromising server integrity.
Conclusion
FallingOverride elegantly solves a common frustration on patched Minecraft servers. By restoring sand, gravel, and other falling block duplication in a controlled way, it lets players continue their large-scale projects while server admins retain the performance and stability benefits of Paper or Spigot. The plugin’s simple command interface, per-block-type configuration, and compatibility with well-known duplicator designs make it a must-have for any technical server that has lost vanilla duplication. Just remember to use it only where the original mechanic is disabled, and you’ll have a seamless, balanced experience that honors the spirit of vanilla Minecraft.