Tekkit Customizer
Use this plugin to ban items and blocks for Bukkit, Tekkit, and FTB servers using the Bukkit API. TekkitCustomizer removes banned items from the world and player inventories. It is easy to configure, can be applied retroactively, and automatically logs confiscated items. It requires no permissions plugin unless exceptions are need for certain players. The plugin settings default to commonly-banned Tekkit items.
Because every story that starts with "We decided to start up a Server..." shouldn't end with "...so we had to reset the world."
Installation
Copy the .jar file into your plugins folder to install the plugin. Then restart the server or use a plugin manager to load the plugin.
Configuration
An entry in the config file (config.yml) to ban ALL wool looks like this:
35:*:wool:because pink wool is for girls
- The first part is the material ID.
- The second part is the data value. Some blocks have the same ID, but a different data value. For instance, white wool is 35:0, while pink wool is 35:6. If you put an asterisk, that means ban ALL data values for the given material ID.
- The third part is for your reference. It will appear in the logs to shorthand what the various IDs and data values mean.
- The fourth part is the reason for the ban. It will be shown to players at useful times such as when a player tries to craft a banned item. If you don't fill in the reasons for your bans, you will be constantly asked why various items are banned.
After you edit your ban list, use /ReloadBannedItems to update the bans in-game. If your config.yml file "resets itself", that means you made a formatting mistake while editing the file. NotepadPlusPlus is a free file editor perfect for editing YAML files
A full list of Block IDs will help you add banned items. You can also get the block IDs and Data Values by using /blockinfo (requires /op or tekkitcustomizer.blockinfo permission). This tells you the information about the item you're holding and the one you're pointing at in the world. Some items have a different values in your inventory as opposed to ones place in the world (eg. a door item in the inv vs a placed door in the world).
Making Ban Exceptions
A player who has /op automatically ignores bans as with any player with permission:
tekkitcustomizer.*
You can make individual ban exceptions to give some players to generally banned items through permission nodes. Here are various examples, which should help you understand without further explanation.
- tekkitcustomizer.35.*.use - tekkitcustomizer.35.6.place - tekkitcustomizer.35.*.craft - tekkitcustomizer.35.6.own - tekkitcustomizer.35.6.* - tekkitcustomizer.35.*.*
You can't prevent a specific player's placed block from being removed from the world as this plugin does not track who owns placed blocks in the world.
Types of Bans
Usage Bans
This ban prevents players from using an item, which means left-click or right-click while the item is in-hand. This works well for items like the Mining Laser, but won't stop players from using items which benefit from passive use (eg. modded armors, Talisman of Repair, etc.). You will need a crafting ban or ownership ban to prevent players from getting those items at all.
It's not possible for any plugin to prevent a player from using an item when it is activated by a keystroke (eg. R, G, C, etc.), which are common especially for Equivalent Exchange items. This is why many EE items are on the default ownership bans list even though their functions are not all really ban-worthy.
Crafting Bans
This ban prevents players from crafting an item. When the player tries to craft the item, they get a message that they can't. This is the most player-friendly approach to preventing players from getting banned items. Forge mods don't always hook into Bukkit, meaning its possible for players to get banned items through some automatic or non-crafting approach (eg. alchemy). When you crafting-ban an item, test for workarounds, which may lead you to ban additional items to prevent those workarounds. The contraband scanner will help you identify the existence of workarounds by creating log messages each time it takes an item out of a player's inventory.
Ownership Bans
This ban prevents player from picking up an item from the ground or from a container (eg. a chest). If a player doesn't have permission to own an item, they won't be able to craft it. The contraband scanner will search each player's inventory for ownership-banned items and actually remove them without warning, notification, or compensation. Any items which are actually found in a player's inventory which the player doesn't have permission for will trigger a log entry, so you can follow-up with an investigation to find out how the player managed to get the item in the first place.
Placement Bans
This ban prevents a player from building a block in the world. A player that already has an item which is later placement-banned can still trade it with another player or break it down into energy (EE mod) to get some value out of it.
It is recommend to place most or all placement ban items to your crafting ban list. This will prevent your players from unknowingly spending their resources to craft a block which they then can't place in the world like they planned leading to them feeling cheated and likely complaining. The only exception you might make to this rule is for an item which can't be placed, but is still useful because it's an ingredient in another recipe for an item you haven't banned.
World Bans
This ban will retroactively remove the placed block from the world through the contraband scanner. This is great if you need to ban an item, but also know it's in the world (eg. energy collectors and world anchors). This will help clean up newly-banned items without having to search your entire world for them. There are exceptions to this removal as the scanner can't determine who owns the block.
Similar to the ownership ban, this ban will trigger a log message when a contraband block is removed, along with its location so that you may investigate to find out how the block got there in the first place.
Notes
Download the correct CraftBukkit version for your server as labelled on the uploaded files as major Bukkit API changes occurred between 1.2.5 to 1.4.7.
The default ban list is made for Classic Tekkit based on hands on testing done by BigScary. Before deciding to remove items from this list, be sure to read the reasons for default bans to understand why it was originally removed. If you are running FTB, Tekkit Lite, or other mod packs, do your own research for what you want banned and change the config file accordingly.
Save yourself some time! Check our Frequently Asked Questions page for the answer to your question. If you found a bug, make a ticket and include your config file.
The following features are planned for the next release:
- Vastly improved performance (Confirmed)
- Add configurable scanner settings (Confirmed, in progress)
- Change in config file structure (Confirmed, in progress)
- Change in permission nodes (Tentative, investigating)
- Consolidate Usage Bans and Placement Bans (Tentative, investigating)
- Consolidate Ownership Bans and Crafting Bans (Tentative, investigating)
- Dropped 1.2.5 support (Tentative)
- Dropped explosion prevention support (Confirmed)
Donations
Unlike other players who have a choice to play the game, my commitment to development and administration usually means I cannot and I'm fine with that choice. A lot of my free time is actually spent designing, developing, testing, and fixing plugins like this one to make Minecraft more enjoyful for all players. If you like this plugin, please consider sending me a donation by clicking the button below :) Thanks!
Hey everyone, I'm looking for someone to take over this plugin. If you're interested, please contact me via private message.
1.6 Update!
@TheDjKiDD
The workaround you mention won't work. The plugin defaults to all worlds at the time it was installed. It doesn't pick up new worlds as they're created. Sorry, I just didn't design the plugin for a situation where players get to create new worlds on the fly, it's just not something that happens on 99% of servers.
@bigscary
I'm more worried about them creating a world, crafting a banned duping item and going nuts... I put all the possible worlds up to 99 but I get the error that it doesnt exist check cfg or whatever. I assume it wouldn't apply protection to those that had not been created yet, correct? I guess if can issue the reloadbanneditems command automatically after every myst age is created that would be one workaround
@TheDjKiDD
Sorry no there isn't. But if it's their world, they can ruin it I guess? I dunno.
@bigscary
Just tested, doesn't work. BUT check your pms!!
Great plugin!
Is there anyone to configure default settings for ALL worlds? Players are able to spawn mystcraft ages into the folder world_myst/ageN. If I could just apply enforcement to all worlds in a folder that would be amazing also
@zlepper
Nice. Confirmed, or guessing? What other items might be used instead of the deployer for the last step?
@Kaosvf
Not sure, haven't tried. Made it for CraftBukkit. I've heard that BukkitForge has very poor plugin support - lots have complained that it doesn't emulate CraftBukkit very well. If this plugin doesn't work for you, try MCPC instead of BukkitForge.
Does it work in a server modded with bukkitforge?
@bigscary
Project table or Phil stone.
Create deployer
place deployer.
Create automatic crafting table
make table create explosives
use tubes to transport it to deployer
activate deployer
use ignitor or redstone torch at explosive
BOOM
Hey everyone, I need your help. My server was recently (lightly) griefed despite my running both this plugin and grief prevention. I see several houses with land claims around them that have sphere-shaped explosion marks in them, complete with crater. I need brainstorming - how could players have accomplished this? Because the disaster is somewhat limited, I don't believe it was the infernal armor (press C to destroy everything). My guess is that somehow, they made EE explosives, got them into the world, and ignited them. Any guesses as to how this might have been accomplished? I have the default ban list, minus project tables. Thanks!
@HeyAwesomePeople
Read the instructions above. You need a name for the item and a reason for the ban.
@bigscary
Mixed in Usage would be perfect :)
Thanks
@bigscary
Incomplete? What needs to be added? Also, I never use tabs.. I know what they do.
@HeyAwesomePeople
Entries like the one below are incomplete. Also if you have a tab somewhere in there (like at the beginning of a line), the whole damned file will reset thanks to Bukkit's not so great handling of YAML files. Sorry, I know it's a pain in the ass, but I have to use what's provided for me by the Bukkit guys.
On disabling EE, no, not for specific worlds. You can turn it off on your whole server somewhere in your Tekkit configs. Banning the philosopher's stone will make most of EE inaccessible for new players, but players who already have other EE gadgets will continue to enjoy the mod. Why do you want to ban the whole thing - what items are problematic for you?
To enable EE in only one world, see description above. Using your favorite permissions plugin, give all players permissions to use the EE items ONLY when they're in that world. Yes, it means you have to make a list of the EE items, sorry. I've already spent tens of hours meticulously going through all the items available in Tekkit, testing them, determining the right default bans, and recording their IDs and data values, and then testing that the correct bans are in place. This is the type of pain we all sign up for when we decide we're going to run a modded server - having to learn everything there is to know about the mods we've installed to avoid griefing catastrophes.
27534:*:
@Kane_Hart
Thanks, I'll look into that interaction ban. Are you okay with the usage ban list being applied there for your convenience, or do I have to put in a whole new ban category and have you copy/paste across the two lists?
@Kane_Hart
Before Reload: http://pastebin.com/uy5KRCMS
After Reload: http://pastebin.com/NJ19b7Q2
Now also, I want to just ban EE in every world BUT the world EE. Now this seems simple, but how do I enforce the banned items on the EE world(Not the EE items)?
Request: Interact Ban. Allowing me to ban interacting with certain blocks.
@HeyAwesomePeople
That is an annoying bug. What you need to do is for that section that causes a reload just put a fake entry in. If you mean your entire thing reloads then your doing something wrong.
Also, whenever I edit the config, it resets after a reload or startup...
Is there a way to simply disable EE in the enforced worlds?
@z2s8
You can use a combination of config file and permissions to do that. See above.