Steel Security
I have noticed that recently a lot of server admins have installed something like LogBlock or NoCheat and then thought that they were untouchable. Then they turn around to see that their server have been completely ruined by either hackers, spammers, or griefers. I wanted to put and end to all of this, so I started the creation of Steel Security. My goal is to have one plugin that will make a server as safe as possible with minimal work for the admins that covers every last aspect of grief prevention.
Note This a beta release the only features currently implemented are:
- Censoring With whitlest words
- Anti Spam
- Anti Caps
- Login Limiter
- Offline Game mode changing
- Block Blacklist
- Vanishing
- Player Spectating
- Ticket Request System
Planned Features Are: (Note: These are not implemented yet)
- Block Logging With Rollbacks
- In game Config Editing
- Anti Speed,flying,fastplace,etc. Hacks
- Region Protection
- Chest Protection
- Online Intefaces
- Chat and Command Logging
- Back-Ups
- Inventory Monitoring and Cheat Checks
- Sequential Teleporting
- IP Logging
- Global Banning
- World edit logging
- Op confirm
- Admin passwords
- Video Logs
- Anti Xray
- Hack client feature survey tracker.
- Remote server.log veiwing
I hope this plugin puts an end to griefers and hackers so any admin can sleep soundly at night.
@mike111177
Ah good. Is there an ETA on the nodus detection? I suspect over half my players on my factions server uses nodus.
@Suhjinko
At the moment most of the features can be disabled. Soon they all will.
@Melodicaxe
that is relieving. I've been really stressing about that
erilidon we are all experiencing the same problem and no anti cheat plugin has a fix ;*(
Would it be possible to enable/disable parts of this as we want? For example all I may want would be Anti Spam and caps, could I disable everything else?
@deleted_8591593
Can you tell me what was going on when it happen. like was it when someone joined or qiut or weather it was on start up?
This has crashed my server 3 times, so I have removed it. I was running SteelSecurity v1.1.0-bb67 on craftbukkit build 2317. Here is the error:
2012-08-16 18:52:24 [SEVERE] Could not pass event PlayerMoveEvent to SteelSecurity org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:332) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:213) at net.minecraft.server.Packet10Flying.handle(SourceFile:136) at net.minecraft.server.NetworkManager.b(NetworkManager.java:281) at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:109) at net.minecraft.server.ServerConnection.b(SourceFile:35) at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:583) at net.minecraft.server.DedicatedServer.q(DedicatedServer.java:212) at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:476) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:408) at net.minecraft.server.ThreadServerApplication.run(SourceFile:539) Caused by: java.lang.NullPointerException at net.othercraft.steelsecurity.listeners.SpectateManager.onFollow(SpectateManager.java:256) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:330) ... 14 more
@carstorm
Yes there will be
Will there be sqlite support. I don't have a mysql database to use.
@pimsserver
The block logging is probably going to be in the next major update and after that the rollbacks. The Nodus Tracking is under a heavy experimental phase due to the many variables that can show nodus usage.
@pimsserver:
The MySQL database is just a continuous log, the only tables that will have delete-able items with the SS interface are OPs and the Ban list. And if we use the database for region and chest protection, they will be fully editable too.
@Theway2cool1:
The database will have both regular OPs and Admin OPs actually.
Do you think you have an ETA for the block logging with rollbacks and the Nodus tracking?
Will it also log rollbacks? because, right now, with HawkEye, it's rather confusing when you only see PLACED blocks which are not there because someone rolled them back (carelessly), ages or minutes ago.
It would be nice if Steel Security could tell admins who rolled the blocks back, when, who (griefer) and why (reason parameters, possibly required if set to true in the config).
Could you also please make the log showing up in the chat work as HawkEye instead of like CoreProtect (CP only shows the latest edit, HE shows EVERY edit, devided over multiple pages, if necessary)
@Theway2cool1:
We're trying to go with MySQL for what we're doing, rather than having to manually edit files. That way, it can be done easily in-game, which is what we're going for. We're trying to have server restarts only for the plugin updating, and nothing else. Also, the difference is that you can be OP-ed, and not on the Admin list, so you can OP people, and prevent them from OP-ing others, and maybe also prevent them from kicking and/or banning others too, if we add that.
@siOnzee:
We're working on that.
@aphilosopher:
No hacks is on the to-do list right now, it isn't implemented yet.
@joehot200:
I am pretty sure it does, but check with Mike.
@CTMiner
That's actually almost exactly how mine works, except it's a config in the plugin folder, not MySQL. Like, if someone's name is not manually added to that config, they get a message saying "[OpConfirm] You have been de-opped by the server!", and they essentially get automatically de-opped the next time they move, run a command, place a block, or break a block (and the command gets canceled, as well as block break/place).
OP confirm works like this: There is a MySQL table with a list of absolute whitelisted members. Whenever someone gets OP-ed by a user not in that list, it will send them a message in chat saying "_ tried to OP _". That list is separate from the OP list, so you can specify people you fully trust in that list, and then it will prevent someone who got OP from OP-ing others in that list, because it will prevent them from OP-ing them, and they will probably be de-oped by someone who got the message. If that makes any sense to you. Right now, Mike and I are working on all the MySQL stuff and the Online Interface.
wow, judging from the planed to do list this plugin has potential to become so extremly awesome!
meanwhile i wont be installing it until it cant replace nocheatplus as in the player movement hacks etc,
since nocheatplus is about the only option to those hacks at this time then it wins out on this one, (even though its become buggy laggy and abandond)
Might I ask what you plan on doing as far as OpConfirm? I wouldn't mind sharing the source for what I've created, since you guys are the ones that inspired me to create it. What it does is automatically de-ops players unless their name is added to the config by an owner.
does this stop admins hacking too?
i have seen clients promote people to admin, then they can hack all they want! does this stop that? i notice as super i can still use nodus.
Please MySQL with Tickets :)
hi. i love this great idea . i was wondering weather it includes anti forcefield for pvp. and if so when it be out. thx.