Open VideoGameSmash12 opened 10 years ago
Auto smite does work well, we added it in cjfm in a effort to further automate things.
The strike system is also something that we looked into, but as its offlinemode it was deemed unreliable and would cause more harm than good.
It will also check if the player is cracked or is premium. If it is cracked, the next time the player logs it, it will be cleared if it's not in the list of YouTubers and famous people. If it is premium, it remains on the .yml file.
Would do nothing... Would make no difference to the issue at hand.
Smite history sounds like overkill. I'd be willing to do something like the auto-smite for a single server session, however. Question is - do we really need it?
I can see a use if there are no admins online... The system we had running on CJFreedom worked well, and was part of our plans to potentially make the server only need a few admins to administrate instead of the millions we currently have.
It might be worth having it added for when the admins are on and seniors can toggle for now? We can then ensure its working how we want it to, if it then seems to be getting few to no false positives, we then change it so its always on when no admins are?
@StevenLawson already built a strike system in TFM quite a long time ago, @VideoGameSmash12. The code it stale but still works. It's hooked up to some anti-cheat features like the nuke monitor and anti-freecam.
I suppose we could use the same system here?
I'm thinking it would be a nice system for automation, however, I still feel it should only be active if no administrators are online.
I'm thinking we actually might prevent this behaviour completely. It would be a simple enough change to block players in creative from killing those in survival.
@JeromSar Dont forget those using god mode and such... But I think some form of punishment should be applied in addition, just as the admins would apply if it was caught in game.
@Wild1145 I suppose hooking into Essentials for Godmode isn't too hard to do. I don't think there should be a sanction if we prevent the behaviour beforehand. Just like we don't sanction for placing lava.
@JeromSar Fair enough. As for the god mode bit, I dont remember how Camzie did it, but I dont think we needed to link into Essentials... I dont remember though I might be wrong, I havent seen the code in some time.
I presume they will get some sort of message to tell them not to do it? Like the lavaplace one that says its not enabled?
@Wild1145 We already hook into Essentials for nickname handling (TFM_EssentialsBridge
). Yes, a message in place would be likely, :)
@JeromSar I know you already hook in, I was just saying that I dont remember us needing to do anything specifically essentials linked to make it work. We might have, It was a while ago it was added to the project.
Actually, I think it would be easier to just prevent players in Creative/GodMode to attack players in survival.
I performed this on the CJFM and the original FOPM by blocking PVP in god and creative (no smite etc.). To test for god mode, I simply created my own handler for god.
Here's what I came up with, If a player is in creative mode, and they hit another player in survival, it will not do any damage. However, I can type a command (ex. /cpvp) and people can hit me in creative mode if I want them to test out weapons etc. If someone does hit them in creative and /cpvp isn't enabled for that player, they will be auto-warned.
You are all forgetting one thing, say player x spambots the server with bots with killaura on, then what? auto smite lags the server and crashes it. Before we even think about this we need a solution to spambots.
Regardless, I am working on patch for cmode pvp so stay tuned.
Have made a patch, and quite an elongated one at that. Blocks way more than just gmc players fisting gms players. Anyway, I will add a autosmite feature to the code.
@JeromSar and @Wild1145 What else should I add? I have blocked gmc pvp, fly mode pvp, god mode pvp, bow pvp, potion pvp and have added the commands /requestunstrike and /unstrike. The first is for ops that think they were unfairly smited by the system and can request for staff to use the unstrike command on them to remove a strike. Anyway what do you think?
Whats wrong with bow pvp, potion pvp, fly mode pvp? @Commodore64x
@OxLemonxO because this goes a bit beyond the issue, plus I completely overhauled the potion blocking system which some people might get angry at? I dunno.
@Commodore64x Bow pvp, potion pvp, and fly mode pvp is perfectly fine.
Lots of things to talk about, so prepare your eyes!
Auto-Smite:
I have been smiting so many people who creative pvp'd recently and I've had enough typing /smite so why not add an auto smite? Here's how it works: When a player dies, it will check if it was a player who killed the player, if it was, it would check if the player is in survival, if not, then SMITE with the message: " has creative pvp'd! Smiten as a punishment!", but if they were, no smite. There could be other things too, you decide! :)
Strike History:
Here's how it works: If a player has been smiten, it will record it and check if it is a 3/3, if it is, then tempban! If it's not, then it will add 1 to it. Special Command for Telnets: /listsmitehistory Tell me what you think!
Forum page link: http://www.totalfreedom.boards.net/thread/14835/server-suggestion-smite-strike-history