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!
Whoah, why unable to use Damage Values bigger then 128? o_O Needed!
Hello! I was wondering if there is any way for tekkitcustomizer to stop removing nether diamond ore. I tried removing the entry of it under the world ban in the config, but it seems to just reset itself. The console also gets filled up with spam from notifying the console every time it removes a diamond ore in the nether.
1.3 Update!
@yrthilian
Yes, I think it will. I've added mystcraft to my soft depends so that any plugin by that name will load before TekkitCustomizer.
I don't understand your comment about forge. I don't know what forge is, or what a "block limit" is.
@Sinistralis777
What made me create this is when I first tried Tekkit with GriefPrevention and discovered that SO much of Tekkit completely bypasses all plugins, which was horrifying. Then I looked around at item banning plugins, and all of them seemed very difficult to deal with, especially those that did all of their configuration via permissions. So now here's the complete Tekkit item banning solution, where all you have to do is install it and reboot. :)
@lee3kfc
Did you remember to reboot your server after you updated? I tested this with the steam engine before I released. I'm very confident the fix is good. You can check your boot logs to get the version of TekkitCustomizer you're running.
@bigscary thank you for fixed the never stop explosion bug what i told you! :D but i tested it and steam engine explosion was never stop :s
I installed this without reading the comments. I just saw the name of the designer and knew it was good. Thank you.
Haha finally got sick of all the people bugging you about Tekkit and GP? Nice to see you took a Developer's approach to this problem.
Will the next update by chance work with mystcraft?
I love the plugin and it works great on the default world but really need it to work for mystcraft if at all posable :D
thanks
note you might want to update forge for the server. I am unable to get in and the fix for the block id limit is part of current forge
1.2.1 Update!
Another awesome plugin from bigscary! I applaud your work, oh genius! Haven't used it yet, but I'll be installing it shortly on my tekkit world.
@fatpancake
I'm gonna need you to be more specific there. :) I don't quite understand what you mean. If you want to give players permission in one world but not another, then use your permissions plugin to do that. If it doesn't do it, then you should consider switching to a better permissions plugin.
Bigscary i advise adding different world perms because ur plugin is deffective with another world with multiverse plugin
@1996BRECHT
It's not required to type the apostrophes ('), sometimes bukkit just adds them when writing values back to file. The * means ALL data values for an item id.
is it possible that you need to set the id:damage value like this -> 'id:damage_value' ?
PlacementBanned: - 126:0:Energy Collector I - 126:1:Energy Collector II - 126:2:Energy Collector III - 223:1:Tesla Coil
becomes then:
PlacementBanned: - '126:0':Energy Collector I - '126:1':Energy Collector II - '126:2':Energy Collector III - '223:1':Tesla Coil
also, why is there in the config sometimes a '*' before an item name and sometimes not (see above) ? thanks, very helpful plugin !
@suslady21
Yep, use your permissions plugin to give players permission to use the banned item as long as they're in the "allowed" world. You'd still leave the item on the ban list, but make an exception for players in that world via permissions.
Is there any way to ban an item in 1 world (NO EE WORLD) but not in another(EE WORLD)? I still want to have some items banned in the EE world, but not all (Like collectors) for people who just want to have fun with EE or just want to use the condenser. PS. I use multiverse for the multi worlds.
@magictj
Check both the "place" bans list and the "ownership" bans list.
@bigscary
Thanks but there not there in the config ill see about the default thing
@magictj
The collecators are banned because they'll wreck your economy. Check your config file again to see if they got put back. If they did, ban an item nobody uses in that section, because when you leave it empty, it defaults.
Hi, I like this plugin although when we opended the config energy collectors were still there, but we want them to not be banned so we removed them, however they are still banned???