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!
Thanks for the update to 1.4.7!
I have this plugin running perfectly on my MCPC+ Tekkit Lite server.
Obviously I had to change every single item ID in the default config, but that is fine.
For those curious, here is how im running MCPC+ Tekkite Lite, http://forums.technicpack.net/threads/mcpc-bukkit-plugins-on-tekkit-lite.36732/
@piritacraft
Did you get 1.5.2 for CB 1.4.7? There are two 1.5.2 versions. If you installed the correct version and it didn't work, then it's a problem with your mod platform (FTB, MCPC, Tekkit Lite) not supporting the full range of Bukkit plugins. Please report your issue to the platform developers.
I tried TekkitCustomizer 1.5.2 on FTB MindCrackv8.01(bukkit 1.4.7) and not worked. The folder with config file is not created.
It looks like dragon was right...the updated version doesn't seem to function. This is using the 1.4.7r0 that was just released
2013-01-28 20:07:00 [SEVERE] Error occurred while enabling TekkitCustomizer v1.5.2 (Is it up to date?) java.lang.AbstractMethodError at org.bukkit.craftbukkit.v1_4_R1.inventory.RecipeIterator.next(RecipeIterator.java:30) at org.bukkit.craftbukkit.v1_4_R1.inventory.RecipeIterator.next(RecipeIterator.java:9) at me.ryanhamshire.TekkitCustomizer.TekkitCustomizer.loadConfiguration(TekkitCustomizer.java:126) at me.ryanhamshire.TekkitCustomizer.TekkitCustomizer.onEnable(TekkitCustomizer.java:96) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:426) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381) at org.bukkit.craftbukkit.v1_4_R1.CraftServer.loadPlugin(CraftServer.java:293) at org.bukkit.craftbukkit.v1_4_R1.CraftServer.enablePlugins(CraftServer.java:275) at net.minecraft.server.MinecraftServer.j(MinecraftServer.java:534) at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:500) at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:426) at ho.c(DedicatedServer.java:195) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:656) at fy.run(ThreadMinecraftServer.java:16)
thank you for update :)
@dragondeatth
You need to wait a few hours for bukkit to approve the new builds, so you most likely downloaded an old version
@dragondeatth
Are you sure that's the right version dragon? The only 1.5.2 I see is for 1.2.5 ...I haven't located a 1.4.7 build yet. Perhaps I'm blind but it's not in the file listings anywhere from what I can see
@bigscary
Sorry to bother you, but I downloaded the 1.4.7 version and it didn't work with Tekkit Lite :(
Here is the console log: http://pastebin.com/2Q3xfiVc
Thanks! :D
Okay, I posted a CraftBukkit 1.4.7R0 compatible version. Please note that if you are running a modded server which is not simply "Tekkit Classic", then you will probably need to add items to the ban list and/or change IDs and data values, because the default ban list has IDs for recommended banned items in Tekkit Classic.
I currently use MCPC+ 1.4.7 with tekkit lite 0.5.2, and can run any plugin/mod without converting because the new MCPC+ dynamically converts on the fly. Its GREAT!
It would be great if Tekkit Customizer was updated for 1.4.7, then i could finish my plugin persuit!
@dragondeatth
I haven't used bukkitforge in a few weeks so honestly I don't know where it stands compared to MCPC+. I do know with MCPC+ I can use almost any plugin designed for 1.4 without any complication. Stability was a lot higher for me compared to bukkitforge as well and bug fixes reported get fixed really quickly. That being said it isn't perfect and is still prone to some issues.
My biggest beef with bukkit forge before was the inability to use any proper permission or land protection system and most block change recordings systems didn't work properly which is why I switched. I have not had that issue since. There were also some issues like chunk unloading and entity limiting.
You're always welcome to PM me if you want to discuss server management. I'm always happy to knock around ideas with other server admins.
@bunnyhop100
I'm using Bukkit Forge at the moment. Does MCPC+ do the same thing as Bukkit Forge? If it does, would you recommend it instead of Bukkit Forge? :)
@bigscary
Yes, exactly. I have Bukkit Forge installed, so I'm able to install Bukkit plugins! I just need you to update it to 1.4.6 or 1.4.7, because right now it's top outdated to work on my FTB server xD
@bigscary
MCPC+ is the latest in merging CB and Forge and has been working quite well. Most plugins work fine with it with the odd exception. Tekkit Customizer is one of those exceptions however I feel it's more likely due to the plugin being designed for 1.2.5 rather than 1.4.7.
You are correct BukkitForge is out there as well offering a coremod approach to bukkit compatibility rather than a CB/Forge merge. I have found MCPC+ a lot more stable.
If you had a version (of Tekkit Customizer) designed to work in 1.4.7 you very well could be considered a plugin god to the community as tekkit customizer is the missing link for most server admins and the 1.4 series of MC....well I mean moreso than you are considered now =)
@dragondeatth
No sorry, there's nothing I can do to make a CraftBukkit plugin work with FTB. FTB would have to add a mod to its mod pack which is more or less a CraftBukkit clone. I thought somebody was working on that - it's called Bukkit Forge or something like that?
@bigscary
Yeah, this doesn't work with Tekkit Lite nor Feed The Beast. Can you please make it compatible with the newer versions, because my Feed The Beast server really needs this :(
@bigscary
Hi Bigscary,
It doesn't work with my 1.4.7 build. Unfortunately there's no log messages except something bad happened. I'm working with MCPC+ (build 23 atm) which is off the reservation as far as tekkit lite is concerned.
MCPC+ right now is still WIP which very well could be part of the problem.
If there's a log debugging config for your plugin I can specify to spew out some actual useful information for you please let me know and I'll send you whatever results I'm getting to see if there might be an easy solution to resolve this.
@bunnyhop100
It doesn't work for your later build? Anyway I'm only trying to support recommended builds. My Tekkit launcher doesn't have a new recommended build yet.
@Pandalein
I feel your pain - any plugin with a reasonably complex config file is difficult to deal with due to the YAML file format. I'm sorry that you had so much trouble.
@Bigscary
I have been using 181:5, i dunno why i put instead 185:5 that time. It kept happening so i replaced the whole config with a newly generated one removed all entries cept one for control and added the crystal chest line, it works perfectly fine. My old config had no other 181 entry anywhere but there was an error of sorts in there, not sure what the hell happened but now i made a new config again and everything seems in order. Thank you again, now i feel very stupid >.<
Any chance of making a 1.4.7 version of this plugin for use with the newer tekkit packs? Even if the block IDs all need to be adjusted for custom builds this plugin would be incredibly useful for anyone using post 1.2.5 builds