CraftGuard
CraftGuard is a plugin that easily allows you to control crafting, smelting, using, and various player actions easily through item lists.
- Modules system to allow you to choose which actions you want to check
- Support for inheritance between lists
- Support for metadata
- Automatic whitelist : you can choose to automatically allow or disallow actions on items that aren't in any list
- And much more !
Coming from CraftGuard 1.x ? see the Upgrade page.
New user ? See the First start page.
Links :
Wiki (help) - Issue Tracker - Source code - Downloads
(Video editing in progress, the video should be availiable in few days)
Latest updates & Changelog
This is the first (beta) release of CraftGuard2 ! It adds the following features since Craftguard 1.x :
- New module system : block not only crafting and smelting but also placing, breaking, repairing, and using items, everything highly configurable and with lists !
- Improved list structure
- Added new commands
- Done a lot of optimisation
- Added new configuration option And much more !
What's next ?
Here is a list of the features i plan to add to CraftGuard :
- Brewing module
- "Permission mode" : use permission nodes instead of lists.yml
- Adding custom crafts and smeltings
- (Support for custom guis) ??
- More !
Statistics
Report a bug/A suggestion
Please use our new bug tracker at GitHub. It requires a GitHub account which takes only a minute to create, and is free. Alternatively, you can also post your issues on BukkitDev bug tracker.
Source code
All the source is availiable under GNU General Public License version 3 (GPLv3) here
@FrozenTux
Peut être que j'ai parlé un peu vite... Je me suis lancé dans de très importants changements de structure pour rendre la suite du développement (les addons) plus facile. Du coup, je ne pense pas arriver à faire de release avant après demain au mieux.
Maybe i have talked a bit fast... I have begun important structure changes to ease a lot the development of addons, so the release may be delayed by one day or two, sorry about that.
@Almathy
Oui ! Je suis en train d'apporter les dernières touches avant une première release (beta), j'espère la sortir d'ici demain !
--Yes ! I am working on the final touches before a first beta release (will not include "extra" features like custom recipes or crafting chances, which will come later as addons). Except it before tomorrow !
La 2.0 avance bien? :-)
@hankypopanky
Just tested your configuration. It's an issue with your bpermission configuration because it wasn't working for me at the beggining but as soon as i applied craftguard.default directly to my player it worked. Please refer to bpermission help.
Hey FrozenTux, I've having trouble setting up a server. I'm using this (very very basic :P) config of craftguard:
This should make users in the group "default" (bpermissions plugin) able to craft torches, sticks, crafting table. So I use this part for groups.yml (bpermissions):
unfortunatly this does not work :( I tried (being a default user) to craft a crafting table and I wasn't allowed to do that...What have I done wrong? Thanks for helping me :P
@Dustburn
I'm working on it as you can see on The new repo. But since i can only code at weekends, i think i'm still 2-3 weeks away from a release :/.
when will you release the version with the features i told to you man ? :)
@fneyret
Like he said.
@fredghostkyle1
"Preventive allowing : item which isn't in any list is automatically authorized to anyone configurable"
In config, preventiveallow: true
is there any way to have it so that insted of allowing crafting for items listed, can u set it to deny crafting with items listed? it would save my A TONE of time, thanks!
This plugin works well for me. I like the ability to create a crafting black list by setting my default permission to false. Nice stuff.
After few tries, i finally decided to rewrite CraftGuard2 from scratch.
If you're interested, you can follow the progress of the project on this github repo : CraftGuard2 GitHub repository
@ToddVee
I just replied.
About additional crafting recipes, i'm working on rebuilding the "core" of the plugin (the code was too messy), and then I will add custome recipes.
@FrozenTux
I sent you a PM with the link to the config. Have you made any progress or spent any thought with the idea of additional crafting recipes? Thank you so much!
@ToddVee
Strange... Can you send me your config file (via dropbox or pastebin) ? I will test and try to figure that out.
@FrozenTux
yes, all of them are surrounded by apostrophes, e.g. '44:3'.
@ToddVee
Did you put your ids within apostrophes like in the how to configure example ? Because ids are read as strings, so if you forget the apostrophes the id won't be recognized at all.
I have that with steps - although "masons" are allowed to craft steps, they can't. I use machinacraft to let them build automated craftingtables so thery can craft it. the chest you need to place the recipe in is locked by admins so nobody except admins can change the recipe.
To me it seems the plugin can't handle those sub-IDs, e.g. 44:3. ":3" seems so be ignored, however then they should be able to craft steps because they start with 44... weired =)
@Maruviel
Hello, Can you please send me the entire content of your config.yml file, so i can do tests.
You can for instance upload it here.
Hello!
I have a "Chef" perm group on my server, and they can cook specific things, but for some reason no one can craft bread despite the ID being placed correctly in the config file, and the perm node being added to the PEX perm list. Here is the group format.
craftguard: chef: granted: - '282' - '281' - '297' - '320' - '322' - '335' - '350' - '354' - '357' - '363' - '382' - '353' permission: chef.permission
PEX has:
- craftguard.chef.permisssion
Placed at the bottom of the perm listing.
I've gone through -all- of our plugins and I can't find a single thing that would cause Chefs to not be able to make bread. I've also tried adding the craftbench ID, 58, to the list , as well as the wheat ID 296, and players set as a Chef still cannot craft bread.
I'm in the process of redoing the PEX perms for the inherited player group, so perhaps that will work, but I would appreciate any input.