Limited Creative
Limited Creative
prevents any way of creative player to pass items to survival-mode, without need of a separate creative-world.
Overview
Scenario: You're starting your first survival server, just finished the spawn, the first players join and one asks: "hey sup, g1v3 me cr3at1v3. i made u teh imba *whatever*-building"
. Well, if you really decide to say okay to that, 5 minutes later, that players has stacks of diamondblocks, -armor and -tools in there bags. Next step? Reset your world and completely start over, which is never fun!
But Limited Creative is here to save you.
So how does Limited Creative prevents players from abusing creative-mode within your world:
- Switching back to survival? previous survival-inventory restored
- Trying to put items in a chest? denied
- Trying to drop something on the ground or hopper? denied
- Trying to put items into storage-carts or sell to villagers or similar? denied
- Using commands not intended for creative players? denied
- Using economy to sell for plugins? denied
- Wants to go anywhere in creative mode? denied
- Trying to place expensive blocks somewhere? allowed, for sure, that's what creative is for, but the block won't drop anything if destroyed in survival!
The restrictions aren't only for restricted players. I also like to have some of them as the owner. For example separated inventories: No need to rearrange your quick-bar after switching back to survival mode. No more bother because you thrown away a stack of grilled steaks for a single wool-block on switching back ;)
Or building a minecart track as op. While breaking blocks often carts, rails torches, redstone and much more fall to ground... no longer! LC prevents all that drops, or just removes them when you walk over.
Features
- Inventories-Module
- Display configured armor on creative players for visual distinction
- Remember creative inventory or not
- Separate adventure from survival or not
- Limit-Module
- prevent dropping of items in creative mode (even on death)
- prevent access to all types of chests in creative mode
- prevent usage of interactive signs (to stop economy in creative)
- prevent dealing or retrieving damage to/from other players (that means: no PvP between creative and survival player)
- blacklisting the use/create of items/blocks as well as breaking blocks
- blacklisting the interaction with selected entities
- optional prevent pick up of items in creative mode or remove items on pick up
- WorldGuard Region-Module
- that means: enable automatic creative-mode for selected players in regions you want
- blocks in creative regions never drop anything (independent who placed it or which game mode the destroyer is in)
- prevents pistons from getting blocks out of creative areas
- optional: let player switch game mode in creative-area (/lc creative/survival) without permission
- Command Blocker-Module
- While in creative mode, certain commands can blocked for users via configuration
- Either blocks simple strings or complex regular expressions
- Bypass certain parameter commands via permission
- GameMode-Permissions-Module
- Adds players to a configured permission-group as long as they are in creative
- This allows you to negate all permissions that creative players shouldn't use, like economic features
- Requires Vault and a Permission-Plugin supported by Vault
- BlockState-Module Disabled by default in config.yml
- Remembers if blocks are set by creative players
- Prevents the drop of blocks created by creative players, even if it is not in a region
- Works with pistons, tnt, item frames, falling sand/gravel and attached items like redstone/torches
- Supports MySQL and SQLite (definition form bukkit.yml)
- A tool (wood pickaxe by default; right-click) tells an op who created the block in which gamemode.
- A command (/lc bs) to modify the saved state in the database, via WorldEdit-Selections
All features are optional and can be independent disabled in config.
Utilizing the only for LC developed library plib, LC provides easy usability for admins:
- Self explaining config.yml, with every setting documented
- Full configurable from commandline/ingame commands
- Detailed command explanation for every (sub-)command (
/lc help
) - On the fly module enable- and disabling via configuration-commands
Documentation
While most of the plugin (config and commands) are self explaining, you can click on the features above for further description (incomplete). Also following some more references:
Commands
Configuration
Permissions
FAQ (Frequently Asked Questions)
Miscellaneous
Translation / Supporting the Plugin
Please help translating the plugin, by clicking on your Language at the Translation-Page. You can then enter the localized strings for you language. It should be easy to you to add some strings of your mother language. Improvements to English language is also welcome.
Also I would like to add some new Screenshots, maybe a Video. So feel free to send me what you imagine represents this Plugin.
Collecting Statistics
This plugin collects some basic statistics about the amount of servers using this plugin, as well as MCStats.
What is send: Server-Name, -Address and -Version, List of installed Plugins, LimitedCreative-Version, Count of players online. These Information aren't published and can only be seen by me, the Author (Possible).
The MCStats are complete anonymous and can be seen by everyone here.
You can disable all collection with /lc config metrics false
and /lc config save
Before doing that I please you to read further about the Metrics.
Known Problems/Bypasses/Incompatibilities
Attention: WorldGuard has its own "game-mode" flag. That flag doesn't relate to LC in any way! Be sure to use "//
region flag <id> gamemode creative
" instead of /region ...; Otherwise the LC restrictions won't affect that region.
Currently no ways to bypass restrictions as a creative player are known
as of Nov 2, 2013 (some reports are currently under evaluation)
Links/Contact/Donation
- PayPal-Donation
- Free-of-cost-Donation: Register on Dropbox and unlock me additional storage
- IRC-Chat: #[email protected]
- E-Mail / Jabber: [email protected]
- Skype: [email protected] / jascha.starke
- Suggestions/Bugs - How to Use debug for additional information
- Source on GitHub
- Development builds of this project can be acquired at the provided continuous integration server.
These builds have not been approved by the BukkitDev staff. Use them at your own risk.
http://ci.ja-s.de:8080/
Special thanks to all Donators:
90$ zeshan321
50$ http://www.cosmicmc.com/ (MinecraftAllen)
25$ Suzy
5$ Punkred
<sub>Timerange: Jan. 2012 till Dec. 2013</sub>
How to handle errors/problems
I will no longer bearing huge error msgs in the comments. Make a ticket for that if you want me to react on that. If there is an error message in the comments i may delete the comment without annotation.
Have you considered a feature such as that in burning creative suite (though that method is very much inefficient, ended up crashing my server on startup) where the dropping of items from blocks placed in creative is prevented (so not the destruction of the block)?
Something that blacklists certain commands whilst in creative would also be very useful. An implementation of this could be switching the user to a different permissions group (and suppressing others) when going into creative, to create a custom set of available commands.
Best plugin to filter a survival server from VIP members :D
@Possible
Wow Possible. I just had my users test out a creative zone and that is so much fun. Thanks again for the plugin. Its a great addition.
@lixah
Just a suggestion but you could always siwtch from iZone to Residence + worldedit. Thats what i run and have found Residence much more powerfull than iZone.
@Jobsti2 @Digitalink2008 I couldn't reproduce your problems, but they may be fixed with the major compatibility update. So please try again when devbukkit has approved v0.8.2. If it still appears, please file a ticket with additional debug informations.
@lixah Oh, i don't see that at the moment. I may look into after i've released a stable release, but can't promise it to you, as there seem to be very few servers without worldguard&-edit ;)
This is great, exactly what i was looking for.
1 thing, im using izones instead of worldguard, it would be nice if there was a way i could get it working with the region based stuff with that ?
thanks
Very useful plugin! I would have made it myself if it wouldn't exist ;)
Am using b1818 with beta v0.8.1 and permissionsbukkit. All limits seem to work except build and destroy limitations. From a quick read of the comments that sounds like what i should be expecting at the moment ya?
testing with /perms check limitedcreative.nolimit.use <playername> = false testing with /perms check limitedcreative.nolimit.break <playername> = false <playername> can still place and destroy in creative.
PS. I love having the controls on creative like this. Killer plugin.
D.
Heyho,
Plugin works great, but if keepinventory: true
some permission.nodes won't work correctly, like drop or pickup. With :false all permissions are working great.
@sadendash
We're also using pex 1.17. No problemes, but we're using our old Commandbook Commands (gm 1 & gm 0) not from this Plugin, works great.
But tested /lc c and /lc s with our team, no problems! Our mods have: limitedcreative.switch_gamemode*
@Possible
Thanks for the Update. Now all permissions are working correctly, itemdrop in creative too.
@ItsKohle If you had read 4 comments bellow, you had seen i already declined that. But now i added a paragraph for this. I will not answer another comment to that topic.
Very nice, but perhaps people in survival shouldn't be able to break blocks placed by creative people? Would make this much better :)
wow this sounds fantastic, will definitely give this a run this weekend :D
@sadendash Sounds to me, like it is PermissionsEx' cache. If a permission works for one player, but not for another, there is nothing i can do. /pex toggle debug may help you. If you have more issues (you said "several"?), please create tickets.
We got several issues with the plugin! some Moderators only should use the right limitedcreative.switch_gamemode but they cant switch gamemode... some of them can change and some of them arent! I use Pex 1.17!!
@gv1222
No. Not at the moment. Storing MetaData to EACH block placed by a creative player would be a huge responsibility, that is hard to handle. The intended usage is, that you don't give full creative to your user. Just create a creative-region with WorldGuard and this plugin. As described in the features, all block-drops are prevented in these creative-regions. When the project is finished you change the region from creative to protected (no build/break), aren't you?
@Possible
Could you please add the ability to block other players from picking up blocks that people in creative have placed so that people cannot abuse it?
@Squirzy You have to enable "PermissionsEnabeld" in config, to get the nolimit.* permissions working. (well should be explained up there xD)
Jobsti complains that only the nolimit.use permission isn't working (he is right). fixing that in next version
@Jobsti2
I can confirm this, the nolimit permissions are not working
@Possible
Great plugin, works good with #1801.
requests:
• If itemdrop is disabled, it would be nice, if the item would be dropped from inventory, so I have a free slot, like BurningCreativeSuite.
• Option to configure, colorize and translate all the messages
• Messages for items on the use and break blacklist
• Option to disable the use of workbenches, like Chests
• Option to disable mob-attacking (Don't forget Bows)
• Maximum und Minimum Flight hight. Because we use inception. If a Player fly on y:126 he teleport to skylands, get the survival mode and falling down to the normal world and dies.
Bugs:
• / /region info/flag .... doesn't work, internal Error. /lc r works. (region shows help) http://pastebin.com/BDRmsGDP
• limitedcreative.nolimit.use doen't work as bypass if permissions: enabled: true. I have to give my groups - limitedcreative.nolimit.use for working use-blacklist. Other nolimit.... permissions are working.
limitedcreative.nolimit.break doesn't do anything, all users could destroy all blocks. (tested with - and - -)
Edit: After I defined the region test1 and set the creative-flag with /lc r. The following error occours, if I use /lc r info test1 or /lc r info test1 get http://pastebin.com/AK5S2Lns
Wiki: creative-group to "non-members" isn't correkt. I had to use "nonmember" ("anyone" doesn't work)