SimpleItemPermissions
SimpleItemPermissions version 3.0
SimpleItemPermissions is a Basic but powerful Plugin that allows Server owners to Control what players can Craft, what Weapons/Tools users can deal damage with, what block a player can place or destroy and much more
This plugin is great for all types Server but is aimed at RPG Servers allowing Owners to create custom classes Via Permissions
Requiments
Features:
full control of Armour, Tools, Weapons, Blocks with permission nodes.
Installation:
Note: if you do not have Vault the plugin will disable itself
- Drop the .jar into your plugin folder.
- Edit your permissions plugin with the permission nodes below.
- Restart your Server to enable the plugin
- Profit!
When Changing Values in the config you need to shut down your server then edit the Config then Start the Server again for them to take effect.
Light Version's:
Only want to use some Features of this plugin ? why don't you choose a light Version of what you need to-do.
These are coming soon!
- Block Control: View Here
- Weapon Control: View Here
- Armour Control: Version 1.0 Available Here
To-do
Allow Owners to change the colors of warnings Add the commands /help <allowing you to get helpful hints> Add the commands /sip list <gives you a list of the items you are allowed to use>
Suggest something !
Permissions:
- Item Permissions:
- SIP.Pick.Wood
- SIP.Pick.Stone
- SIP.Pick.Iron
- SIP.Pick.Gold
- SIP.Pick.Diamond
- SIP.Axe.Wood
- SIP.Axe.Stone
- SIP.Axe.Iron
- SIP.Axe.Gold
- SIP.Axe.Diamond
- SIP.Spade.Wood
- SIP.Spade.Stone
- SIP.Spade.Iron
- SIP.Spade.Gold
- SIP.Spade.Diamond
- SIP.Hoe.Wood
- SIP.Hoe.Stone
- SIP.Hoe.Iron
- SIP.Hoe.Gold
- SIP.Hoe.Diamond
- SIP.Sword.Wood
- SIP.Sword.Stone
- SIP.Sword.Iron
- SIP.Sword.Gold
- SIP.Sword.Diamond
- Armour Permissions:
- SIP. Armour.Leather
- SIP. Armour.Iron
- SIP. Armour.Gold
- SIP. Armour.Chainmail
- SIP. Armour.Diamond
- Damage Permissions:
- SIP.Damage.* - Users can deal damage with anything
- SIP.Damage.Fist - Users can deal damage with there Fists
- SIP.Damage.Sword - Users can deal damage with Any Sword (See item permissions for Controlling the each sword)
- SIP.Damage.Pick - User can deal damage with any pick
- SIP.Damage.Axe - User can deal damage with any Axe
- SIP.Damage.Shovel - User can deal damage with any shovel (spade)
- Misc Permissions:
- SIP.Misc.Brewing - User can use a brewing Stand
- SIP.Misc.Enchanting - User can use a Enchanting Table
- SIP.Misc.Bow - User can use a Bow
- SIP.Misc.Breeding - User can use wheat to Breed
- SIP.Misc.FishingRod - User can use a Fishing Rod
- SIP.Misc.LavaBucket - User can use a lava Bucket
- SIP.Misc.WaterBucket - User can user a water Bucket
- Block Permissions:
- If Control Block is true in config you need to add these Permissions, You need to Replace ItemID with the ItemID you want to allow.
- You can view the item IDs Here
- SIP.Break.ItemID - Allows the User to Break the item you have chosen
- SIP.Place.ItemID - Allows the User to Place the item you have chosen
- Crafting Permissions:
- If Control Craft is true in config you need to add these Permissions, You need to Replace ItemID with the ItemID you want to allow.
- You can view the item IDs Here
- SIP.Craft.ItemID - Allows the User to Craft the item you have chosen
ChangeLog
- ==== Version 2.2 ====
- Added option to control armour checks
- Added Brewing checks
- Added Enchanting checks
- Fixed Crafting message not displaying correctly
- ==== Version 2.1 ====
- Updated to R4.0
- Fixed the Issue with The Config not been created
- See the main post for most things
- Bug Fixes
- ==== Version 2.0.2 ====
- Add permissions for Water & Lava Buckets, See the Misc Permissions
- Changed how the Config is Created
- Bug Fixes
- ==== Version 2.0.1 ====
- Updated for 1.2.5- R1.3
- Bug Fixes
- ==== Version 2.0 ====
- Total Re-Write of Code Fixing a lot of bugs please view the Description for more details
- ==== Version 1.2.1 ====
- FIXED SuperPerms Support. (i think)
- REMOVED Color to warnings Will re-add them soon!
- Added Perms for Shears <simpleitem.shears>
- Added Perms for FishingRods <simpleitem.fishingrods>
- Added Perms for Wheat <simpleitem.wheat> (added this for 1.9 to control breading)
- Created a Message config so you can easy edit messages.
- ==== Version 1.2 ====
- Added SuperPerms Support
- Added Color to warnings/Will make them customizable soon!
- Added Perms for Chainmail <simpleitem.armor.chain>
- Added Perms for all Damage <simpleitem.dmg.*>
- ==== Version 1.1 ====
- Mainly Bugfixes
- Fixed spelling in permissions nodes
- ==== Version 1.0 ====
- First Release!
@arnie2311
...Is there a time we can expect these issues to be resolved?
@welknair
It is
Is this still being worked on, or should I continue looking for another plugin?
It would appear that you can bypass armor restrictions by shift-clicking them on. You may want to fix that, if possible.
Edit: After a half-hour of fiddling, Baeshra and I are having problems configuring your plugin. Specifically, we wish to use it to set up custom classes for our RP server, where only certain classes can do certain things. The first class we were working on was the "Juggernaut", a tanky class. He, like many classes, can only use a wooden sword, and no others. However, when we set SIP.Sword.Wood true and SIP.Damage.Sword true, we found that the class could still use diamond swords perfectly. Including SIP.Sword.Diamond false did nothing to help. Do you have any idea what we're doing wrong? Config below.
# PermissionsBukkit configuration file
#
# A permission node is a string like 'permissions.build', usually starting
# with the name of the plugin. Refer to a plugin's documentation for what
# permissions it cares about. Each node should be followed by true to grant
# that permission or false to revoke it, as in 'permissions.build true'.
# Some plugins provide permission nodes that map to a group of permissions -
# for example, PermissionsBukkit has 'permissions.*', which automatically
# grants all admin permissions. You can also specify false for permissions
# of this type.
#
# Users inherit permissions from the groups they are a part of. If a user is
# not specified here, or does not have a 'groups' node, they will be in the
# group 'default'. Permissions for individual users may also be specified by
# using a 'permissions' node with a list of permission nodes, which will
# override their group permissions. World permissions may be assigned to
# users with a 'worlds:' entry.
#
# Groups can be assigned to players and all their permissions will also be
# assigned to those players. Groups can also inherit permissions from other
# groups. Like user permissions, groups may override the permissions of their
# parent group(s). Unlike users, groups do NOT automatically inherit from
# default. World permissions may be assigned to groups with a 'worlds:' entry.
#
# The cannot-build message is configurable. If it is left blank, no message
# will be displayed to the player if PermissionsBukkit prevents them from
# building, digging, or interacting with a block. Use '&' characters to
# signify color codes.
users:
baeshra:
permissions:
permissions.example true
groups:
- jugg
groups:
default:
permissions:
permissions.build true
jugg:
permissions:
permissions.build true
SIP.Sword.Wood true
SIP.Sword.Diamond false
SIP.Armour.Leather true
SIP.Armour.Iron true
SIP.Armour.Chainmail true
SIP.Armour.Diamond true
SIP.Axe.Wood true
SIP.Axe.Stone true
SIP.Axe.Iron true
SIP.Axe.Diamond true
SIP.Damage.Fist true
SIP.Damage.Axe true
SIP.Damage.Sword true
default:
permissions:
permissions.build true
default:
permissions:
permissions.build true
messages:
build: '&cYou do not have permission to build here.'
debug: false
I just have to say thank you arnie! I've been delaying the main release of my rp server for the solus rpg plugin to update, this is everything I need. I can't believe I missed this plugin originally! I can't wait for Shrines of the Ancients to really kick off.
@FusSionzZ97
is the user shift clicking ?
Players can equip diamond armour running latest RB. Please update this is such a good plugin for RP servers :)
what is the default for those? If i don't set a permission I can assume its allowed or denied?
Thanks
mors
is this plugin compatiable with bpermissions
can this plugin handle data values like 5:2
awesome plugin thanks for making it but its not working like i want it to i am having problems getting the sword/tools to work i permissions and the misc and armor work but the swords and tools anyone no what i am doing wrong? im testing with this group
p.s. useing group manager
Not a bug but huge mistake ! When I add - SIP.Damage.Sword I can deal damage with any sword to what ever I target on !
But I want to make that it's allowed use only (for example Woord Sword) So I delete - SIP.Damage.Sword And place - SIP.Sword.Wood
So now I am not allowed to use any other swords (like I wanted to) BUT I can deal damage only to blocks not mobs/animals ! And that is dead end ! if I want to deal damage with sword to mobs/animals I need to add - SIP.Damage* but than he allow any weapon to deal damage to mobs/animals ! Can you make some ideas about this one ?
when we can expect SimpleWeaponPermissions :D?
As it is assumed armor with Shift, it is assumed, and does not show the error.
@arnie2311
Don't stop developing!
I love this idea. I am going to make professions like Weaponsmith and Armorsmith now!
Going to be inactive for a while but I will try my best to keep this on a stable build
I LOVE THIS PLUGIN, Best Restriction Plugin ever. . .
I can't disable only the Diamond Sword of a group.
Tried: - SIP.Sword.* - -SIP.Sword.Diamond
and - -SIP.Sword.Diamond - SIP.Sword.*
and: - SIP.Sword.Wood - SIP.Sword.Stone - SIP.Sword.Iron - SIP.Sword.Gold - -SIP.Sword.Diamond
In the debug window I can see the plugin first checks for wood sword. when he finds premission for woodsword it stops checking the other swords.
any solutions?
BTW: same problem for Axe's
This plugin is exactly what i've been looking for!
Only thing that I would suggest adding is a way of controlling drops as well.
For instance only a certain permission rank may get leather/meat from cows etc. To control hunting. Would be epic!
I realise that. I didn't try to be "hostile". But it kinda broke my permission...even tho' i made backups...kinda a waste of time...I should have realised it's not for 1.3.1 yet.