Modifyworld-Reloaded

Modifyworld-Reloaded

A modern continuation of Modifyworld for Paper, controlling player actions with permissions that can vary by group and world.

Features

• Allow everyd``ay building while restricting TNT placement, lava buckets or ignition tools.
• Control crafting, item pickup and dropping, and which items players can put into or take from containers.
• Give groups different abilities in each world through permission contexts.
• Diagnose action permissions for online players with /modifyworld check.
• Customizable denial messages with seven bundled languages.

Requirements and compatibility

• Paper 26.2 and Java 25. Newer Paper versions are unverified; Spigot and Folia are unsupported targets.
• LuckPerms is recommended, not required; checks use Bukkit permissions.
• WorldGuard is optional for region protection; install its dependencies separately.
• See the release notes for version and validation details.

Installation and updates

Stop the server and place Modifyworld.jar in plugins/, replacing any older copy. Start it to create plugins/Modifyworld/config.yml, assign permissions, review settings and restart. Before updates, back up worlds, configuration and permissions; follow the release-specific instructions.

Configuration changes require a restart. Use /mw reloadmessages for edits to the active language file; it does not reload config.yml. Permission changes apply on subsequent checks. Verify rules with a non-OP account in each world.

Commands and permissions

Reload applies denial, help and diagnostic messages; invalid files leave the previous messages active. Configuration changes still require a restart. Help shows permitted commands. Tab completion suggests online players and action permissions; custom action nodes can also be typed directly.

Console must name the player. /mw is enabled by default; set command-alias-mw: false and restart to disable it. /modifyworld remains available. Command details.

Example of how permissions work

Give builders access to ordinary materials while reserving TNT for a trusted group, or let players build in survival while keeping spawn interaction-only. LuckPerms world contexts let the same group have different permissions in each world.

Permissions describe individual actions, so you can control placing TNT separately from crafting it or taking it out of a chest:

For example, a Player group can receive general survival access with a specific restriction on TNT placement. Run in the server console after creating the group:

lp group player permission set modifyworld.* true world=survival
lp group player permission set modifyworld.command.check.others false world=survival
lp group player permission set modifyworld.command.reloadmessages false world=survival
lp group player permission set modifyworld.blocks.place.tnt false world=survival

Replace survival with your actual world name. This grants survival access and own permission checks while denying TNT placement, checks of other players and message reload. TNT crafting, transfers and ignition remain separate permissions. Existing assignments and inheritance can affect the result.

Assign grants as well as denials: unlisted actions are not automatically allowed. LuckPerms resolves inheritance, wildcards, explicit denials and contexts; world=<world-name> scopes a rule to that actual world. Material names are lowercase without underscores, such as lavabucket and flintandsteel, rather than legacy numeric IDs. There is no universal per-item permission.

• op-bypass: false (default): OPs need assigned or inherited action permissions; implicit OP grants alone are insufficient.
• op-bypass: true: OPs bypass Modifyworld checks, including explicit denials.
• Unknown inventory actions are an exception: modifyworld.items.allowunknownaction.<item> defaults to allowed. Explicit denials apply unless OP bypass is active; known-action checks are unaffected.

Building, items, and inventories

Permission segments use lowercase names without underscores. <item> and <block> refer to materials; <inventory> is a type such as chest, barrel or furnace. Bucket <content> names include lava, water and other supported contents.

Item-use checks replace ordinary block/entity interaction checks when enabled. Opening a chest with an empty hand then checks modifyworld.items.use.air.on.block.chest; taking or putting items is checked separately. Container checks cover clicks, shift-clicks, dragging, hotbar/offhand swaps and double-click collection; a swap needs both take and put permission.

Other permissions

<entity> includes category prefixes, such as monster.creeper or animal.wolf; spawn-egg <type> uses the unprefixed entity type. <cause> identifies a damage cause.

See the complete action reference and LuckPerms world examples for setup and inventory edge cases.

Permission diagnostics

For example: /modifyworld check modifyworld.blocks.place.tnt. Use a concrete action node, without wildcards; checks use the online target's current world. The result diagnoses Modifyworld permissions, not whether other plugins allow the event. Output interpretation.

Configuration

Settings in plugins/Modifyworld/config.yml control item checks, OP bypass, language and admission checks. item-restrictions can remove denied items when inventories are checked. Review the settings and defaults before enabling restrictions.

Updates preserve settings and custom messages. Changed files are backed up; version-only updates create no backup. Do not edit config-version. Conflicting legacy messages require manual merging. Upgrade details.

check-for-updates checks GitHub at startup and links to Hangar without downloading files. Set it to false and restart to disable it. Update-check details.

Messages and languages

Choose en, de, es, fr, pt_br, pl or tr. For custom messages, edit lang/own.yml, select language: own, keep messages: {} and restart. Later text edits can be applied with /mw reloadmessages; changing the selected language still requires a restart. Place color resets after highlighted placeholders, e.g. &a$1&4 and &a$3&4, so following text keeps its sentence color. Missing custom entries use English fallback; material/entity names remain English. See formatting and language details.

Migrating permissions from legacy Modifyworld

Legacy numeric IDs, metadata entries and PEX world rules need manual conversion; configuration migration does not convert permissions. Follow the migration guide and verify effective grants and denials.

Troubleshooting and limitations

Invalid configuration/language files disable the plugin while the server continues: protection is inactive until errors are corrected and the server restarted.

WorldGuard owns region protection; Modifyworld respects existing event cancellations. OP bypass does not override other plugins. Automation, natural fire spread and redstone/TNT chain reactions are outside the general player-permission model. Placement, ignition and explosion protection are separate concerns. Checks do not provide a blanket ban on an item's existence or recursively restrict container contents. Custom inventories, creative actions and plugin-driven paths need server-specific verification. See scope and interactions.

License and credits

Original Modifyworld by t3hk0d3 and the contributors to PEXPlugins/Modifyworld; community port maintained by yippieyaray. GNU GPL version 2 or later (GPL-2.0-or-later). See LICENSE and NOTICE for retained attribution and provenance.