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
@domingo15
If you turn "On-Void-fall(Player): true" to false and the other one, the bug will stop occuring.
I think I'll keep the emergency chunk loader just for now, it helps me a little with testing the chunk loading of server when running iSafe.
But thanks for the bug report!
Would have taken me weeks to notice it.
@mrmag518
Well theres two on that one "On-Void-fall(Player): true" nd "On-Void-fall(Creature): true" but it doesn't teleport anyone thats being damage to spawn on v2.63 but when i switch to v2.64 it teleports anyone or anything that receives damage to spawn.
EDIT: I think its better if you get rid of the chunk code specially the chunk emergency loader, let NoLagg handle the chunking :)
@domingo15
I'll take a look into it, I think I have an idea on what this may be.
Edit: Fixed it, You had "EntityTo-SpawnLocation...: true" right?
@mrmag518
We have an issue here on v2.64, i don't know if its just me or my server but when anything(mobs & players) gets damage they get teleported to my multiverse spawn point on that specific world. Could you take a look on this i didn't had enough time to test it more out but that was one of the major ones because of pvp :)
EDIT: i have to switch back to 2.63 immediately due to this problem.
@foxwillow
You don't have to wait long; Just uploaded v2.64 :)
amazing - thanks a lot! i'll be keeping a close eye now :D
@foxwillow
I see your point; I have been a little lazy with the permissions nodes for a while now. But I'll get on it; I'll make it the highest priority. (So I remember it)
is there any way you can set permissions nodes for the individual things in the "Damage" section of the config? i'm trying to use isafe to add another layer of depth to a classes system, and while it's great that i can deny some classes sneak and sprint with isafe perms, i'd also like to be able to make some classes immune to fire damage, immune to drowning, etc, immune to arrows, immune to magic, etc... and right now it looks like those things are only configurable globally, not individually. :) if doable this would be massive, thanks!
@domingo15
"Disable-Block_Explosion-damage: true" means it's preventing damage to players if a block (like TNT) explodes.
"Disable-Entity_Explosion-damage: true" means it's preventing damage to players if a entity (like a Creeper) explodes.
You may have right, the explosions config can be misunderstood, and I’ll fix it.
The second is true, it blocks the explosion from damaging anything, and do you want a separate feature to block the explosions from appearing to?
@mrmag518
Uhmm! i think you should review the "Explosions Code" on the config.yml because i did some testing and i find it very confusing.
First: "Disable-Block_Explosion-damage: true" for this being true means it prevents block damage on any explosion right but it doesn't instead when i put false on that and made "Disable-explosions: true", this prevents all block damages from TNT, Creepers, or Fireball with the player or mobs receiving damage.
Second: "Disable-explosions: true" suppose to prevent explosions right meaning no exploding creeper and etc instead it prevents blocks from being damaged.
might be a little bit confusing on how i wrote it :)
@mrmag518
okay thanks man ;)..nice plugin btw ;).cant wait v2.64 out .
@i7Surf
Yes, it is possble, but thanks to you I found a bug :)
The reason why it's not disabled is because of an issue. It's fixed in v2.64.
@mrmag518
..sry for my bad english ..yeah i really want to disable that broadcast message when any online user login ..and disable broadcast what plugin i running add in server ..is it possible?.
@Wppvater
As domingo said, iSafe doesn't have that feature. What you're thinking of is a x-Ray detection system I think.
@i7Surf
If you mean that config node will stop other plugins for adding a MOTD on join, that's wrong, it only disables the "this server is running iSafe v.........", but if you ment that the isafe join message is not disabled when it's supposed to, then I'll check it.
How do i disable isafe broadcast massage when login?.cause i did read some of config.yml and i change "Broadcast-iSafe-message-on-join: false" but when i login back still broadcast other plugin that tell any online user ..any help would be great ;) .> love iSafe :)
@Wppvater
I don't think that is supported with this plugin, iSafe is all about prevention not notifying on block break.
That would be block logging but in this case with broadcast of who break the block."sorry as far as i know iSafe don't have that feature."
I don't quite get the config and the explanation. Is it possible for me to somehow have my staff members notified if someone for example mines a diamond ore block or gold block? If so, how do i do it?
@Damimad
I'll take a look into it, but try to writte them in lower case letters like domingo said.
@domingo15
Yes, I could do that. I'll start creating a new page.
@Damimad
hey man, have you try using lowercase like "isafe.drop*".