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
If items that don't normally drop you make drop, they can be broken in worldguard regions.
@Theway2cool1
That's weird, I'll look into it.
There's a bit of a problem with the command blacklist... like, I want to disallow people from using /gm in certain worlds. That works to a certain extent, but they can still switch by using /gm <name>
@Gunnerrrrr
For eggs you need to input the creature id or name not the spawn egg id. (and you only need to do that in the mobsConfig)
nevermind that i figured it out, But eggs dont work on the blacklist. I have a creative world and need to block them. Here is my blacklist.yml:
Worlds: - Creative Blacklist: - 383:50 - 383:51 - 383:52 - 383:53 - 383:54 - 383:55 - 383:56 - 383:57 - 383:58 - 383:59 - 383:60 - 383:61 - 383:62 - 383:90 - 383:91 - 383:92 - 383:93 - 383:94 - 383:95 - 383:96 - 383:98 - 383:120
Here is my MobsConfig.yml:
Worlds: - Creative Blacklist: - 383:50 - 383:51 - 383:52 - 383:53 - 383:54 - 383:55 - 383:56 - 383:57 - 383:58 - 383:59 - 383:60 - 383:61 - 383:90 - 383:91 - 383:92 - 383:93 - 383:94 - 383:95 - 383:96 - 383:98 - 383:120
No one has permissions to unblock these, everything else works in the blacklist. Eggs do not.
needs an /isafe reload command
@Gunnerrrrr
Under the "Player" settings, set "Broadcast-iSafe-message-on-join: true" to false.
How do you get rid of the Motd?
@Damimad
Could you explain a little better, like, what do you mean?
@domingo15 v2.66 out today.
What's with all the NPEs?
@mrmag518
soo, when will it be updated for 1.2.5 because I'm starting to see crops being trampled even thought it prevents on the config.
@domingo15
Hmm.. Haven't thought about coding that.. Actually it's pretty smart, I'll add it.
@mrmag518
i just wonder, do iSafe prevent people from building on a certain world like completely remove build perms on that specific world but override it using permissions?
@foxwillow
Yeah, the sprint and sneak have some issues atm, and with the canceldamage permissions, maybe something is wrong, I'll check it out.
Have you tested any other permissions than those?
EDIT:
btw, you need to remove these nodes:
Disable-Fire-damage: false
Disable-Fire-Creature-damage: false
Disable-Void-damage: false
Disable-Void-Creature-damage: false
Disable-Lightning-damage: false
Disable-Lightning-Creature-damage: false
Disable-Fall-damage: false
Disable-Fall-Creature-damage: false
Disable-Suffocation-damage: false
Disable-Suffocation-Creature-damage: false
Disable-Drowning-damage: false
Disable-Drowning-Creature-damage: false
Disable-Lava-damage: false
Disable-Lava-Creature-damage: false
Disable-Contact-damage: false
Disable-Contact-Creature-damage: false
Disable-Projectile-damage: false
Disable-Projectile-Creature-damage: false
Disable-Starvation-damage: false
Disable-Starvation-Creature-damage: false
Disable-Suicide-damage: false
Disable-Suicide-Creature-damage: false
Disable-Entity_Attack-damage: false
Disable-Entity_Attack-Creature-damage: false
Disable-Magic-damage: false
Disable-Magic-Creature-damage: false
Disable-Poison-damage: false
Disable-Poison-Creature-damage: false
Disable-Custom-damage: false
Disable-Custom-Creature-damage: false
ok, love the permission nodes, but it turns out they aren't working. (i didn't test them and had some users bitching, heh)
i am using pex. tried both capital iSafe.permnode and isafe.permnode
this is what i'm doing: i have a plugin that can grant players permission nodes based on their class (Heroes). so i want everyone to be hurt by everything by default, but there are specific classes that should get "iSafe.canceldamage.drowning," "iSafe.canceldamage.fire," etc etc. i also want one specific class to be disallowed to sprint, but instead of disabling iSafe.sprint for them, I took it away from all users and then gave every other class (through Heroes) iSafe.sprint, but everyone can sprint, including the class without it. :S
here's my the snippet of my iSafe config incase i have something wrong...
http://pastebin.com/P74WEPRe
@prototye776
"Make sure to read the iSafe wiki for assistance, information or something familiar. "
How im using it ?! what commands ??
@Ebins
No problem :)
Thanks for the feedback.
@mrmag518
That's what I needed! Thank you so much for your help, and thanks a lot for keeping this plugin updated. Its saved me more than I can count! :)
@Ebins
Disable-(Entity)Explosion-damage:
To-Players: false
To-Creatures: false
Disable-(Block)Explosion-damage:
To-Players: false
To-Creatures: false
Disable-explosions: true
Disable-primed-explosions: false
This makes explosions display as explosions but damages entities.
Better explanation: The cancelled explosion will not cancel the explosion itself, it will search for all the blocks/objects it's suppose to destroy, then clear that list, and no blocks/objects will be destroyed.