GOLD RestrictedCreative [1.17+] 3.0.0-ALPHA-2

Give your players access to creative mode - safely - without jeopardising survival experience! RestrictedCreative is light on CPU and extremely customizable. It covers all basic creative limiting functions: separate inventories, block placement tracking, disabling interactions with inventories etc. Furthermore, it includes several new useful features such as providing customizable commands for changing gamemodes, forcing distinguishable colorful armor and disabling interaction with touch holograms. With this plugin you have your creative players under control, because they have no way to pass items from creative to survival mode!

Not sure whether to buy this plugin? Take a look at the 30+ 5-star reviews posted over the years.

Note about purchasing: in addition to PayPal I also accept most cryptocurrencies (send me a PM). If paying in any way isn't possible for you, send me a PM and maybe there's something you can do for me to earn my plugin.

RC v2 is for Spigot 1.13-1.16 only, and won't receive new features after Minecraft 1.17 is released. Version 1.x (for Spigot 1.8-1.12) will continue to receive bugfixes until MC 1.17 arrives. RC v3 is coming for Spigot 1.17+.

• Extremely lightweight - best performanceof any similar plugins
  • all interactions with database are handled asynchronously
  • millions of tracked blocks won't affect performance more than a couple of blocks - only loading times will increase on startup (still async)
    Example from my personal server:
    Code (Text):
    [10:33:39 INFO]: Creative > Loading data from database...
    [10:33:56 INFO]: Creative > Loaded 1748556 blocks from database!
    [10:33:56 INFO]: Creative > Done! Took 17008ms
• Fully customizable
  • most of the features can be configured
  • every message can be changed (or disabled)
  • command's aliases and description can be changed
  • has a simple API to check block's/entity's creative status and add/remove them to/from creative list
• Permissions to bypass any of the restrictions
• Adds/removes certain permissions to/from players in creative mode
  • supports Vault, but can work without it
• Supports MySQL and SQLite
  • delete all plugin data with one command
• Supports block-loggers (CoreProtect, Prism etc.) using BlocksHub
• Can be disabled per world
• WorldGuardregion support
  • limit creative usage to certain regions
  • limit creative usage to player's own regions (also works for GriefPrevention and TownyAdvanced)
• Separates creative inventory (with XP and potion effects)
  • restores survival inventory when switching back
• Saves inventories to the database or switches back to default gamemode before logout
• Forces creative players to wear distinguishable armor
• Tracksplaced blocks/items
  • tracks pushing/pulling with pistons
  • tracks falling blocks
  • tracks placed boats, minecarts, item frames, paintings and armor stands
  • tracks items inserted into item frames
  • tracks armor put on armor stands
  • tracks blocks edited with WorldEdit and FAWE (//set, //replace etc)
  • removes drops on break/destory
  • doesn't track blocks/items in whitelist
• Disables interactingwith inventories and entities
  • can't open chests, villager shops, chest minecarts etc
  • can't rotate items in item frames etc
• Disables animal breeding
• Disables copying chests' contents with middle-click
• Removes invalid items(with custom NBT) spawned with hacked clients
  • Also removes items with specific name or lore
• Disables dropping and picking upitems
  • removes drops on creative player's death
• Disables specific commands (with powerful RegEx)
• Disables PVP and PVE
• Disables using/placing/breaking certain blocks/items
• Disables throwing/shooting items
• Disables creating Withers, Snow Golems and Iron Golems
  • Even players in survival mode can't create them if even a single block was placed in creative mode

• Building competitions in survival servers
• Safe and convenient creative mode for builders, owners and other staff members
• Sell creative mode for in-game money without ruining survival experience for others

Listed on the Wiki page!

Spoiler: For v1.x
Listed on the Wiki page!



Listed on the Wiki page!

Spoiler: For v1.x
Listed on the Wiki page!



Available on GitHub!



Default config & explanation on the Wiki page!

Default messages & info on the Wiki page!
Translations on the Wiki page!

Spoiler: For v1.x

Default config on GitHub!

Config explanation on the Wiki page!

Italian translation by GiulioTopLad (@giulio248).



Video by @THC1442 [RO]:

Spoiler: For v1.x
Video by @BranstonProject [EN]:

Video by @TheIntelloBox [FR]:


Would YOU like to make one? Let me know!



This plugin requires Java 8+ and Bukkit/Spigot/Paper 1.13+.

Spoiler: CoreProtect
If you want creative-placed blocks to be logged properly by your block-logger plugin, use ParamnesticCure.
Spoiler: Slimefun
If you want bug-free experience with Slimefun, then it's recommended to:

• set "EXPLOSIVE_PICKAXE.call-explosion-event" and "EXPLOSIVE_SHOVEL.call-explosion-event" to "true" in Slimefun's Items.yml file;
• tweak "confiscate.items" (in RC config) to prevent Slimefun items from being used in creative mode.

Spoiler: ProtocolLib
If you have "confiscate.invalid-items" enabled (defaults to true) and want to also check for invalid NBT, you need ProtocolLib.
Spoiler: Vault
If you have "creative.permissions.enabled" set to "true" (defaults to false) and want to use Vault for permission handling, you need Vault.
Spoiler: WorldGuard/GriefPrevention/TownyAdvanced
If you have "limit.regions.owner-based.enabled" set to "true" (defaults to false), you need WorldGuard and/or GriefPrevention and/or TownyAdvanced.

If you have "limit.regions.whitelist.enabled" or "limit.regions.owner-based.allow-members" set to "true" (defaults to false), you need WorldGuard.
Spoiler: WorldEdit/FAWE/AWE
If you have "tracking.worldedit.enabled" set to "true" (defaults to false), you need WorldEdit.

If you use FAWE instead, you also need to enable RestrictedCreative in FAWE's config.yml:
Code (Text):
extent:
allowed-plugins:
- "RestrictedCreative"
Spoiler: Multiverse-Inventories
If you use Multiverse-Inventories and have two worlds with separate inventories and different forced gamemodes, set

• "tracking.inventory.enabled" to "false" in the RC config and
• "settings.use_game_mode_profiles" to "true" in the MV-Inventories config

to prevent switching between three inventories and thus leaking items into survival mode.
Spoiler: Chest Commands GUI, CustomGUI etc.
If your creative players can't use commands that open inventories, it is because you have "limit.interact.inventories" enabled in your config. What you can do is a) disable that setting or b) give the permission "rc.bypass.limit.interact.inventories.<InventoryType enum>" to all players, where InventoryType is a value from this list, depending on which InventoryType your GUI plugin is using. Either way you probably just made a hole in the wall between creative and survival. To patch it up again, you'll have to find all blocks and commands which open any inventories that can be used to smuggle items into survival mode and add them to RC config under "disable.interacting.on-ground" and "limit.commands" respectively.

Spoiler: For v1.x
This plugin requires Java 8+ and Bukkit/Spigot/Paper 1.8 - 1.12.x.

• If you want creative-placed blocks to be logged properly by your block-logger plugin, use BlocksHub.
• If you have "general.remove-invalid-items" enabled (defaults to false), you need ProtocolLib.
• If you have "general.permissions.vault" set to "true" (defaults to false), you need Vault.
• If you have "general.regions.owner-based.enabled" set to "true" (defaults to false), you need WorldGuard or GriefPrevention.
• If you have "general.regions.whitelist.enabled" or "general.regions.owner-based.allow-members" set to "true" (defaults to false), you need WorldGuard.
• If you have "general.worldedit.enable" set to "true" (defaults to false), you need WorldEdit.
  • If you use FAWE instead, you also need to enable RestrictedCreative in FAWE's config.yml:
    Code (Text):
    extent:
    allowed-plugins:
    - "RestrictedCreative"

1. Stop your Bukkit/Spigot/Paper server
2. Download the .jar file and put it into the /plugins folder of your server
3. Start the server, let it generate files into /plugins/RestrictedCreative folder and then shut it down again
4. Edit the config.yml file to your liking and save the file
5. Add permissions as you like
6. Start the server and use the plugin!

• Option to limit specific block/item usage (1 use per x seconds)
• Command /rc block list - it lists all the chunks that have at least <configurable amount> tracked blocks in them and sorts them from most to least blocks; list items would also be clickable and they'd teleport the player to the chunk
• Command /rc block show - nearby creative-placed blocks and entities would be marked with particles
• SQLite <-> MySQL converter
• Support for CraftBook, FastAsyncVoxelSniper
• Add lore to creative items
• Change players back to survival mode if they leave the allowed region
• Rename world without losing creative blocks
• Command to purge the database of all blocks of deleted worlds
• Option to limit breaking blocks only to user who placed them
• Permission to disable flying for creative players
• Option to remove attributes (effects) from items
• New database design in v3 (see Discussions #693)
• Better support for RTL languages
• Option to disable Slimefun integration
• Support for Vehicles plugin
• Support for Residence plugin
• Support for Lands plugin
• Execute commands when switching gamemodes (similar to changing permissions and groups)

• Reloading is not supported: don't use /reload nor plugin specific reload (PlugMan etc), it can cause glitches, bugs and other problems.
• Visual glitch: if FLOWER_POT is blacklisted and creative player tries to place a flower or other plant into the pot, it will visually be there only for that player even though they got a warning message that their action was denied.
• Visual glitch: when a block behind creative-placed item frame is destroyed, the frame will stay hovering for a few seconds before disappearing.
• Limited armor stands on older versions: there is no way to distinguish a creative-placed piece of armor and a survival-placed piece of armor on an armor stand in 1.10 and lower. Therefore, by default, interacting with armor stands is prohibited for creative players in these versions.
• Disabled pushing/pulling slime blocks with rails on top: due to some weird piston mechanics I'm unable to block creative-placed rails (well, any non-attachable and non-pushable block for that matter) from dropping when the slime block below is moved by a piston. That's why I've disabled pushing and pulling slime blocks with rails on top when tracking is enabled in the config.
• WorldEdit's //undo is not supported. Using this command will remove protection from affected creative-placed blocks. If you need to have blocks created by WE marked as creative-placed, please make sure your player's can't use //undo.
• Didn't find what you were looking for? Let me know!

Let me know about any questions in the Discussion section, and feature requests, bug reports etc. in the Issue tracker (RC v1 and RC v2). Please leave review section clear of them. Positive ratings are always appreciated!