iSafe
iSafe - An assortment of beneficial features
Description ==
In iSafe, I concentrate on the way server Administrators are situated when managing their server, such as myself. Personally, I never feel I have all of the features I want, or need... maybe you do as well? I created iSafe to help resolve those problems. iSafe provides you, as a server Administrator, with many of those useful features that never seem to be around when needed.
Quote from iSafe:
Features ==
- 12 Different multiworld blacklists, with serveral toggable penalities & other administrive settings. Improved!
- User files manager.
- Auto update checker.
- Multiple configuration files.
- Permissions support.
- Supports Vault and superperms. (You don't need Vault installed)
- Supports Vault and superperms. (You don't need Vault installed)
- Security & simple AntiCheat settings.
- IP Management settings.
- Various fire related settings.
- Enchantment settings.
- Furnace & Weather settings.
- World & TreeGrowth settings.
- Explosion settings.
- Flow & Piston settings.
- BlockPhysics & BlockFade settings.
- ForceDrop & Bucket settings.
- Movement settings.
- Gamemode settings.
- Teleport & Chat settings.
- Voidfall settings.
- Damage & HealthRegeneration settings.
- CreatureTarget settings.
- Prevent invisibility potion usage.
- Various creature settings, such as disabling endermen griefing, prevent zombies from breaking doors etc ..
- Disable crop trampling for both mobs & players individually.
- Handle what colors sheeps can grow their wool of.
- Combustion settings.
- MobSpawn blacklist for various reasons, such as spawer egg, natural etc ..
- Alter the messages sent out by iSafe!
- Full debug mode. (Currently under development.)
- Mostly everything iSafe does is configurable.
Other ==
Downloads | Forum thread | Source | Tickets | First time tut
@mrmag518
I do not quite understand what you mean by that.
@PatrickFreed
Thanks for that, I'm thinking of rewritting all the permissions to lower case.
@Crazdale
Theres something really wrong with ur superperms, is the superperm jar the same version as the main permissionsex jar?
@PatrickFreed
At this point, I'm seeing SuperPerms not working at all. I made a superperms node of test.test. Added a child node of bukkit.command.kick to the test.test parent.
So in PEX permissions, I gave my group the test.test node... I am unable to use kick. It seems that for some reason, I cannot use any SuperPerms nodes, even with it enabled.
I found an issue with PEX where it would only read permissions if they were entirely lower case, regardless of whether the plugin was checking for capitalized letters.
ie player.hasPermission(Node.node); would return false if you set Node.node in PEX. It would return true if you put node.node, however.
@mrmag518
OK, mrmag518, thanks for all your help. It seems this is something with PEX, and I am not sure what... but it, for some reason, is not finding certain permissions. It seems to skip (not see/ignore) any negated permission I add in, and it also does the same for any permission on SuperPerms.
Not really sure why... but I'll keep working with it, and try to find the fix.
Thanks! ^-^
@IronCrystal
If you OP and/or have the permission node to place obisidan and you set obsidian to false in the config, you can break obsidian, if the opposite is done, you cannot break obsidian.
@mrmag518
I am definitely op and I don't see why I wouldn't have permission to place obsidion. I can place it, and when I can still destroy it. Did I code it wrong?
#I would recommend taking a decent look over the isafe configuration file and managing your wanted features.
Flow:
Disable-water-flow: false
Disable-lava-flow: false
Weather:
Disable-LightningStrike: false
Disable-Storm: false
Disable-Thunder: false
Drops:
Allow-Bedrock-drop: true
Allow-GoldBlock-drop: true
Allow-IronBlock-drop: true
Allow-Diamondingot-drop: true
Allow-DiamonBlock-drop: true
Allow-un_natural_portal-drop: false
Allow-TNT-drop: false
Allow-droping: true
Allow-ExpirienceOrbs-drop: true
Allow-Dimondore-drop: true
Player:
Allow-Teleporting-without-iSafe-permissions: true
Disable-Hunger: false
Allow-Sneaking: true
Allow-creative-gamemode-on-player-quit: true
Enable-Chat-permissions: false
Allow-Sprinting: true
Enable-fishing-permissions: false
Only-let-OPs-join: false
Enable-Bed-permissions: false
Broadcast-to-player-on-join: true
Misc:
Disable-LeavesDecay: false
Prevent-crop-trampling: true
Prevent-portal-creation: false
Enable-kick-messages: true
Piston:
Prevent-piston-Retract: false
Prevent-piston-Extend: false
Breaking:
Allow-SoulSand-breaking: true
Allow-Obsidian-breaking: false
Allow-MobSpawner-breaking: false
Allow-Sponge-breaking: true
Allow-TNT-breaking: false
Allow-Ice-breaking: true
Allow-Pistons-breaking: true
Allow-BedBlock-breaking: false
Allow-Bricks-breaking: false
Placement:
Allow-Ice-placement: true
Allow-Bedrock-placement: true
Allow-Water-blocks: true
Allow-MobSpawner-placement: false
Allow-Sponge-placement: true
Allow-FireBlock-placement: false
Allow-Lava-blocks: false
Allow-Obsidian-placement: true
Allow-SoulSand-placement: true
Allow-un_natural_portal-placement: false
Allow-Pistons-placement: true
Allow-TNT-placement: false
Entity-Damage:
Disable-Contact-damage: false
Disable-Fall-damage: false
Disable-Lightning-damage: false
Disable-Suffocation-damage: false
Disable-Lava-damage: false
Disable-Drowning-damage: false
Disable-Suicide-damage: false
Disable-Projectile-damage: false
Disable-Custom-damage: false
Disable-Entity_Attack-damage: false
Disable-Void-damage: false
Disable-Starvation-damage: false
Enviroment-Damage:
Allow-Fire-spread: false
Allow-Flint_and_steel-usage: true
Allow-Explosions: false
Allow-Enviroment-ignition: false
Allow-Fire-damage: false
Furnace:
Disable-furnace-burning: false
Disable-furnace-smelting: false
Mobs:
Allow-Pig-spawn: true
Allow-EnderDragon-spawn: true
Allow-PigZombie-spawn: true
Allow-Slime-spawn: true
Allow-Zombie-spawn: true
Allow-Skeleton-spawn: true
Allow-Silverfish-spawn: true
Enderman-grief:
Allow-Enderman-Pickup: false
Allow-Enderman-Place: false
Allow-Sheep-spawn: true
Allow-Ghast-spawn: false
Allow-SlimeSplit: true
Allow-Spider-spawn: true
Allow-Squid-spawn: true
EntityTarget:
Disable-pig_zombie_target-target: false
Disable-target_died-target: false
Disable-owner_attacked_target-target: false
Disable-random_target-target: false
Disable-closest_player-target: false
Disable-target_attacked_owner-target: false
Disable-custom-target: false
Disable-forgot_target-target: false
Disable-target_attacked_entity-target: false
Allow-Enderman-spawn: true
Allow-Giant-spawn: false
Allow-Cow-spawn: true
Prevent-PigZap(Pig transformation to ZombiePig): false
Allow-Wolf-spawn: true
Allow-Creeper-spawn: false
Allow-Monster'Human'-spawn: true
World:
Register-world(s)-save: true
Register-world(s)-unload: true
Register-world(s)-load: true
Buckets:
Allow-WaterBucket-empty: true
Allow-LavaBucket-empty: false
Player-Interact:
Allow-Buttons-Interact: true
Allow-IronDoors-Interact: true
Allow-WoodenPressurePlate-Interact: true
Allow-Levers-Interact: true
Allow-Chest-Interact: true
Allow-WoodenFenceGate-Interact: true
Allow-TrapDoor-Interact: true
Allow-StonePressurePlate-Interact: true
Allow-WoodenDoors-Interact: true
@mrmag518
Redownloaded the PEX 1.17 build package.
Typed out the permissions file from scratch. Still not finding those permissions and denying me the ability to place lava buckets in the 'member' group.
Going to try and downgrade to PEX 1.16 and see if that does anything.
Nope, 1.16 did the same thing.
@Crazdale
Try to re-generate the PEX config.
EDIT: I added a special PEX listener, but it only checks if PEX is working with iSafe.
@mrmag518
Running version 1.17 of PEX
@Crazdale
I only compare ur file to mine now, so im gona tell the diffrences:
1. in the PEX config, I see u have no debug node in the superperms, I have that. 2. and some smaller diffrences on the group set-up (dpesnt need to make any diffrences to iSafe)
Since you dont have that debug in the superperms options, do you have the latest version of PEX?
@mrmag518
Here is my PEX config...
http://pastebin.com/UAhErwLx
Here is my Permissions file...
http://pastebin.com/kAh2ThZy
Here is the iSafe config file...
http://pastebin.com/Wh208W3H
Here is the console while starting...
http://pastebin.com/iRXqVMAb
When I tried to place a lava bucket, under the member group, this is the permissions debug info...
2011-12-31 13:00:30 [INFO] User VoidingNixx checked for "iSafe.*", no permission found
2011-12-31 13:00:30 [INFO] User VoidingNixx checked for "iSafe.lavabucket.empty", no permission found
edit: your format is fine... if you're going to be kind enough to help troubleshoot, I can at least take time to piece together your text, however you write it.
This is obviously a PEX problem... it is not checking for these permissions. Funny thing is, it is working totally fine for a good number of other plugins I'm running, but this one, WordRank, and TreeAssist, for some reason, the permsissions are never found... I don't really understand it. ;p
@Crazdale
Ok, im gona give u some info about my set-up: my PEX config:
permissions:
backends:
file:
file: permissions.yml
backend: file
superperms:
disable-unmatched: false
enable: true
debug: false
strict-mode: false
parent-nodes: true
createUserRecords: false
allowOps: false
debug: true
basedir: plugins\PermissionsEx
and my testing rank:
Member:
default: false
options:
rank: '12'
permissions:
- iSafe.lavabucket.empty
- iSafe.waterbucket.empty
- iSafe.*
prefix: '&f[&eMember&f] &7'
and the 2 iSafe config nodes:
Buckets:
Allow-WaterBucket-empty: true
Allow-LavaBucket-empty: false
When I test waterbucket without permissions, it works perfectly. When I test lavebuckets without permissions, I can't. then I gave myself the permission and I would place lavabuckets.
EDIT: wow.. this post format sucked..
EDIT 2: here are some info: 18:53:32 [INFO] User mrmag518 checked for "iSafe.*", found in superperms 18:53:32 [INFO] User mrmag518 checked for "iSafe.lavabucket.empty", no permissio n found
@mrmag518
I'm already to a point of just giving up on this... so not too worried about it anymore. I don't wish to take up more of your time.
You can give me things to check/test with SuperPerms, and I'll give it a shot... I thank you for your time and effort... but, I'm pretty sure everything is good. Maybe you can point out something I totally missed. ;p
edit: by "giving up on this", I don't mean your plugin.... I mean, dealing with the permsissions. ;p
@Crazdale
Are you 100 percent your superperms are working correctly, because iSafe runs its permissions trough superperms and then PEX would listen to it.
I'm gona go on my server and do some testing.
@mrmag518
http://pastebin.com/JtTyPWGu
This is a file I'm just testing atm... just with iSafe and PermissionsEX.
edit: I'm running PermissionsEX in debug, and this is what happens when I place a water bucket.
2011-12-31 12:35:25 [INFO] User VoidingNixx checked for "iSafe.*", no permission found
2011-12-31 12:35:25 [INFO] User VoidingNixx checked for "iSafe.lavabucket.empty", no permission found
2011-12-31 12:35:25 [INFO] User VoidingNixx checked for "iSafe.waterbucket.empty", no permission found
As you can see, it's not finding the permission. I'm having the same problem trying to negate nodes in PEX... it isn't finding anything negated... so I'm not sure what is up with it. SuperPerms and all that good stuff is enabled... it just isn't working *shrugs*.
I've written and rewritten so many permission files over the past 2 days, that by this point, it could very well be a bug in the permissions file, and am just no longer able to catch it. ;p
@Crazdale
Hehe, thanks for the compliment. But i'm a little curious on how you writte the permission nodes?
@mrmag518
Meh, I'm sorry I snapped at you... but honestly, it isn't how I'm writing the file... so I'm not sure where the problem is. Glad you are a cool dev mrmag518. Wish there were more level-headed people like you out there. ;)
@Crazdale
I am glad you understand, and I am sorry for my little disrespecting reply.
@mrmag518
Thanks for the reply. Well, it has to be in my setup then, if you tested with PEX. I'm having problems right now with negated permissions with PEX as well... but I have no idea what's up with it. From what I'm looking at, and reading, everything should be just peachy... but it is obviously overlooking permissions for some reason.
As long as you say you tested with PEX, and it works for you, that's good enough for me.
Thanks mrmag518!