Archived Anti-combat Logging Plug-in

[BenRekt]

As you may have surmised by the title, this thread is concerning combat-logging and an idea to end it.

Combat logging is honestly one of the most infuriating things I have experienced on MassiveCraft. At the moment, the only way I know to actually get a combat-logger punished is to record them in the act. Personally, I expect that everyone will abide by the rules, and when another player decides to blatantly break the rules, and then EASILY gets away with it because nobody was able to record is really flat-out wrong.

I propose that MassiveCraft introduces either a generic combat-tag plug-in, which tags you when you are hit by another player or when you engage another player, and if a player logs off whilst he/she is combat-tagged either said player is instantly slain or an NPC takes said player's place, and can be killed and will drop the player's whole inventory (or what they would drop if they were pacifist false). People may say "I timeout constantly, I will easily get killed!". To that my only response is that you should be more cautious about making sure your connection is good before you run out to fight.

A more permanent fix (and probably a wider-accepted solution) would be to greatly increase the severity of the punishment given out to people who combat-log to make it so severe that people would not even think about combat logging, but to also give the perpetrator the opportunity to admit to breaking the rules, and receive a less severe punishment.

From a PvP-standpoint, this is an issue that really hasn't been to prominent until now. I honestly cannot explain the huge rise in people combat-logging, but I do know for a fact that it has been happening much more frequently than it has in the past, and it is very noticeable. Even if the solution I have presented do not work for the staff / the server, I believe I speak for a large amount the PvP community when I say that this problem really needs a fix, even if it is only temporary.

Do not turn this thread into some personal vendetta against those who are known to be combat loggers.

That will NOT solve the problem at hand.

Tagging people I think will have an opinion to share:
@FubeTheMangler @Yoloorange @Waminer @Traxex20 @panic15 @Bsavs @DisturbedReaper @qgmk @Wannag @spoonly @Bond1337 @YankeeGiant8013 @MagicalWetToast @Joshy54100 @Dogdude1284 @Charpop101 @spectec @Seba5112 @Stonejrod @jquaile @Kapry @lewistard @thor5648

 

[wafflecash]

I always ask a staff to spectate the fight when fighting a rumored combat-logger. But with a plugin it would require less Staff work and have them be punished the first time.

 

[Jackmo_Jones]

My wireless card has a tendency to shut off without warning. No way to control it and no way to predict it. Needless to say I don't like this idea.

If you see somebody logging just record it. If they only do it once it's not a big deal and if they do it multiple times there is no reason why you shouldn't be able to catch it.

 

[Gerrior]

Not generally involved in pvp but anything that will make something right and true normally gets a +1 with me. Best of hunting warriors

 

[BenRekt]

My wireless card has a tendency to shut off without warning. No way to control it and no way to predict it. Needless to say I don't like this idea.

If you see somebody logging just record it. If they only do it once it's not a big deal and if they do it multiple times there is no reason why you shouldn't be able to catch it.

Click to shrink...

Rules aren't meant to be broken, and if they aren't enforced there isn't much of a point of enforcing them whatsoever.

I also suggested another idea, if you have any thoughts on that.

 

[Jackmo_Jones]

Rules aren't meant to be broken, and if they aren't enforced there isn't much of a point of enforcing them whatsoever.

I also suggested another idea, if you have any thoughts on that.

Click to shrink...

If you mean the point about more severe punishment then yes that I could agree on.

 

[FubeTheMangler]

I like it.

 

[krios41]

I do suport this idea.
but ONLY if there is a way for the plugin if he can tell a 'disconnect' and a 'timeout' apart for the reason that if you have a bad internet conection and get disconected mid fight it doesn't count as a combat log.

People may say "I timeout constantly, I will easily get killed!". To that my only response is that you should be more cautious about making sure your connection is good before you run out to fight.

Click to shrink...

While this is true for a pvp'r, should I? a roleplayer, or builder? not play in a survival world with a bad internet conection because of the chance someone might come and raid me and i have a chance to lose conection anytime? that is far from fair. i do know combat loggers are frustrating but this is something a i wanted to say.

 

[ZiHAMMER]

I am against such a plugin. But the punishment should be way more severe.

 

[Kezlok]

100% Support. It's extremely frustrating how people can combat log multiple times and only get what I consider a light punishment.

Imagine this scenario which did in fact happen once for me: You're chasing a non-prem with god armor and most likely a lot of valueable stuff in his/her inventory. You've flywater and the non-prem has a boat. You destroy the boat and you are just about to kill the player but sadly for you the player chooses to combat-log. You wait 1 hour for the player to come back and when the player sees you, the player combat-logs once again. You wait another hour and the process repeats....
You report it to a staff explains the situation etc. and the player gets jailed for one day...
You've wasted about 3 hours on getting a player jailed for one day...

My suggestion:
If a player is attacked by another player or attacking another player they become "combat-tagged" (as BenAlex suggested aswell.) If a player who is combat tagged logs off/gets disconnected a NPC is spawned that will drop the player's stuff if killed depending on pacifist bla bla bla wada wada wada....
All players have a 2 min grace period per day where no NPC is spawned until the grace period is over. In this way the players should have enough time to log on again if disconnected at least one time per day before spawning an NPC in their place.

 

[YankeeGiant8013]

I remember when there was a pvp tag for a couple of months and staff said it could help against anybody combat logging. I disagree with Ben on that but agree that there should be harsh punishment for them or staff moderate fights which I don't think they want to do taking their time they do for the server

 

[kevencolis]

+1

 

[Madus]

Gotta research disconnect vs time out.
EDIT: This is purely for my own amusement. I can't say anything for the server.

 

[Mecharic]

In defense of current punishment, being jailed for a day SUCKS.

But yeah, I'd prefer the "increase punishment" like maybe a week-long jail or a week-long ban from playing.

~Mech the Inactive​

 

[Loewe2011]

I believe the PvP-department is already planning to implement this or a similar plugin.
http://forums.massivecraft.com/threads/pvp-emphasis.26495/#post-340163

From my point of view, this is not really necessary, since it's just a petty and -for pvper- annoying problem. It would not enrich the gaming experience of the whole community.

About the punishments: Sure, but they shouldn't be too harsh since there isnt a plugin (correct me if im wrong) that could see the difference between a disconnect and time outs/black outs/etc.. Also keep in mind, if your raiding a rp faction, dont be surprised if they log off.

 

[Jemo_]

I do not like this idea for the fact that Massive sometimes lags itself, using vamp or speed or flywater whenever this occurs can end up in a short freeze of the server where you have chances of getting kicked for flying. This does happend to me and my friends sometimes and only one can be totally fatal. Also some errors occur within Nvidea and when these happen your minecraft can crash.
I'm not sure if combat loggers are pvpers or just wanne be tryhards? If they indeed combat log and weren't recorded nor spectated, just spread it troughout the pvp community. Who wants to raid a combat logger? If more staff would be free on doing duties on this we can see if the person is; crashing, lagging etc. He can see that if the player is low he will log, or if this happends frequently in a fight. One cannot blame the other for stuff that isn't fitting to what his intentions were.

 

[Kezlok]

I do not like this idea for the fact that Massive sometimes lags itself, using vamp or speed or flywater whenever this occurs can end up in a short freeze of the server where you have chances of getting kicked for flying. This does happend to me and my friends sometimes and only one can be totally fatal. Also some errors occur within Nvidea and when these happen your minecraft can crash.
I'm not sure if combat loggers are pvpers or just wanne be tryhards? If they indeed combat log and weren't recorded nor spectated, just spread it troughout the pvp community. Who wants to raid a combat logger? If more staff would be free on doing duties on this we can see if the person is; crashing, lagging etc. He can see that if the player is low he will log, or if this happends frequently in a fight. One cannot blame the other for stuff that isn't fitting to what his intentions were.

Click to shrink...

Explain your disagree rating. I've only stated my opinion and true facts.

 

[Jemo_]

Explain your disagree rating. I've only stated my opinion and true facts.

Click to shrink...

"Your opinion" I disagree to that, nor are any facts stated though. I do agree on the light punishments, most of my pvp logging enemies got of with a nothing. Though I wouldn't sugest you trying to kill the nonprem, just report and go make some quick god armor.
Though, I think a plugin would first of all never understand why, how and who. We can't know if the guy just recieved a popup and than suddenly klicked the wrong cross and has a shit slow pc that open MC to slow. (I used to have such a pc, I was pvping at nice fps but starting stuff was just slow) Nor can we see if the person bluescreened (Believe me, it can happen, it does happen and it's not fun) or recieved a random restart of his pc to update. You can state: He needs to fix that before a raid. But if he doesn't cause it's a small raid, why should he lose his stuff if he did want to pvp fair and didn't care about his stuff getting lost in fair battle. But look at this thing that can happen: God guy non prem goes to raid a large quantities of other non prems, fair battle and nice times. Suddenly god armored guy lags spasses out and gets killed within the fight cause of the plugin. These people are vulnerable in these situations, cause of their newness to pvp and their unability to pump out god stuff. The guy logs back on and sees his gear where he worked for from start is gone. End, no fairness.

 

[Kezlok]

"Your opinion" I disagree to that, nor are any facts stated though. I do agree on the light punishments, most of my pvp logging enemies got of with a nothing. Though I wouldn't sugest you trying to kill the nonprem, just report and go make some quick god armor.
Though, I think a plugin would first of all never understand why, how and who. We can't know if the guy just recieved a popup and than suddenly klicked the wrong cross and has a shit slow pc that open MC to slow. (I used to have such a pc, I was pvping at nice fps but starting stuff was just slow) Nor can we see if the person bluescreened (Believe me, it can happen, it does happen and it's not fun) or recieved a random restart of his pc to update.

Click to shrink...

Wowowowow slooow down. It was a fact that the player was combat logging so yes I do in fact know. I even got it confirmed by a high ranked game staff. I was told that the player had been reported for PvP logging multiple times. You can't disagree to that ._.

 

[Jemo_]

Wowowowow slooow down. It was a fact that the player was combat logging so yes I do in fact know. I even got it confirmed by a high ranked game staff. I was told that the player had been reported for PvP logging multiple times. You can't disagree to that ._.

Click to shrink...

I thought it was an example:

Imagine this scenario

Click to shrink...

Also this word:

You report it to a staff explains the situation etc. and the player gets jailed for one day...
You've wasted about 3 hours on getting a player jailed for one day....

Click to shrink...

Some people might have no problem with the results they got for the effort they gave, if this was my problem I would report him right away or just rain hell on his faction if I have no evidence, just because he isn't worthy of the pvp community. I would never stand there for 3 hours and if I would I'll be more than happy with the 1 day jail.

 

[Kezlok]

I thought it was an example:

Also this word:

Some people might have no problem with the results they got for the effort they gave, if this was my problem I would report him right away or just rain hell on his faction if I have no evidence, just because he isn't worthy of the pvp community. I would never stand there for 3 hours and if I would I'll be more than happy with the 1 day jail.

Click to shrink...

I wrote: "Imagine this scenario which did in fact happen once for me" You might have missed it?... Meh

Either way it's not my style to let people walk away easily with that much loot. If I had the time I'd have stayed but sadly couldn't. But just the fact that the player actually could "choose" between going to jail for one day or losing a big amount of money makes me sad... Yes, I am a greedy bastard

 

[kevencolis]

I believe the PvP-department is already planning to implement this or a similar plugin.

From my point of view, this is not really necessary, since it's just a petty and -for pvper- annoying problem. It would not enrich the gaming experience of the whole community.

About the punishments: Sure, but they shouldn't be too harsh since there isnt a plugin (correct me if im wrong) that could see the difference between a disconnect and time outs/black outs/etc.. Also keep in mind, if your raiding a rp faction, dont be surprised if they log off.

Click to shrink...

Dont know who told you this but you should just wait until you see it on the change log before spreading rumors.

 

[Gerrior]

Whether or not you are kicked for "flying" or lagging would come into play. There are codes for everything so I am quite sure the server could read whether or not a player was kicked or quit.

 

[Jemo_]

Whether or not you are kicked for "flying" or lagging would come into play. There are codes for everything so I am quite sure the server could read whether or not a player was kicked or quit.

Click to shrink...

But not if the mc crashed or the guy got a bsod

 

[Gerrior]

But not if the mc crashed or the guy got a bsod

Click to shrink...

So then you're saying that we should just let everyone get away with combat logging? right..

 

[The Golem]

I believe the PvP-department is already planning to implement this or a similar plugin.

From my point of view, this is not really necessary, since it's just a petty and -for pvper- annoying problem. It would not enrich the gaming experience of the whole community.

About the punishments: Sure, but they shouldn't be too harsh since there isnt a plugin (correct me if im wrong) that could see the difference between a disconnect and time outs/black outs/etc.. Also keep in mind, if your raiding a rp faction, dont be surprised if they log off.

Click to shrink...

It's quite hard to find something that everyone in the server will agree with, and enrich everyone's community. If the lore staff decided to stop writing lore, and we had to make everything up, do you think people would be happy if the staff responded to our grievances "We have stopped writing lore because it will not enrich the gaming experience of the whole community, thus it is unnecessary"
From my own personal, undeniably occasional, experiences on raiding. If you are catching out scrubs alone in the wilderness with no protection, it is very easy to just set up a pool of lava underneath where they logged. It keeps you from getting the loot undeniably, but when they come back they realize they spent 15 minutes-30 minutes or more, trying to avoid death, only to come back and roast alive. Otherwise, an npc tag would be nice, but i can see why it wouldn't be added with the large amount of plugins already floating about on Massivecraft.

 

[Mightor]

I believe this problem is being tackled wrong. Combat logging is not the problem, the problem is that staff do not have a good resource to identify combat logging and punish it with besides video evidence. Therefore my solution:

When a staff member does /stats on a player, it should include these extra bits of information:
Logout Location:
Logout Situation (In PvP/Not in PvP):
Time since being hit by a player before logout:

EXAMPLE #1: Okay so lets give this example. Now lets say I'm in a big battle with Viserys vs. Alamut at my faction base. We're fighting it up, and then suddenly my Mom calls for me to come do a chore. Now I am still in fierce battle with an oponent, but I need to leave NOW. I then proceed to run inside my home in faction land, shut my door and logout. Now my stats would look like this:

Logout Location: -1002, 130, 1245 in New Ceardia
Logout Situation (In PvP/Not in PvP): In PvP
Time since being hit by a player before logout: 30s

Now lets say the player I was fighting reports me for combat logging. A staff member could review these stats (And TP to my logout location), however seeing that although I was in PvP, I was in a locked house so I am considered safe and thus allowed to logout.

EXAMPLE #2: Now in this scenario I am in a fight once again. However, I am losing against my opponent so I decide to run away until in passive mode (While still being hit), and then logout. I get reported for PvP logging and my stats look like this:

Logout Location: -1204, 130, 1045 in New Ceardia
Logout Situation (In PvP/Not in PvP): Not In PvP
Time since being hit by a player before logout: 3s

I get reported and a staff member reviews the logout location and time since being hit. Seeing that I was still just recently hit and NOT in a safe location to logout, I would be punished. I think the punishment should be a staff member doing a command that drops my inventory as if I died even though I'm logged out. When I log back in I would do my 1 day jail time, and that would be it.

Basically my philosophy is that the staff should be given the resources to moderate potentially rule-breaking scenarios, instead of adding in plugins that could be potentially abusable or game-changing that ruin the experience.

 

[Suzzie]

This would really suck for people in rural areas where internet options are limited. ​

To that my only response is that you should be more cautious about making sure your connection is good before you run out to fight.

Click to shrink...

Really? Not everyone has access to great internet connections. Some people crash and disconnect, thanks to really bad internet providers.
Although I agree there should be harsher punishments [Even though I'm a roleplayer, I know combat loggers are annoying] this anticombat log plugin really doesn't seem like that great of a solution.
-1 for of adding the plugin, but +1 for harsher punishments.​

 

[Grixer]

Interesting topic we have here ...

 

[Loewe2011]

Dont know who told you this but you should just wait until you see it on the change log before spreading rumors.

Click to shrink...

Check this out -> http://forums.massivecraft.com/threads/pvp-emphasis.26495/#post-340163

We also have many ideas for the future we hope we will get the time to implement: Kit PvP, Anti Combat Logging, Duel plugin, Highscore system, better war system in Factions etc. Though as mentioned, the top priority is TPS and MassiveTraits at the moment.

Click to shrink...

Yeah i like reading =)

It's quite hard to find something that everyone in the server will agree with, and enrich everyone's community. If the lore staff decided to stop writing lore, and we had to make everything up, do you think people would be happy if the staff responded to our grievances "We have stopped writing lore because it will not enrich the gaming experience of the whole community, thus it is unnecessary"
From my own personal, undeniably occasional, experiences on raiding. If you are catching out scrubs alone in the wilderness with no protection, it is very easy to just set up a pool of lava underneath where they logged. It keeps you from getting the loot undeniably, but when they come back they realize they spent 15 minutes-30 minutes or more, trying to avoid death, only to come back and roast alive. Otherwise, an npc tag would be nice, but i can see why it wouldn't be added with the large amount of plugins already floating about on Massivecraft.

Click to shrink...

Understandable, but as i said its just my point of view and I'm not against this plugin. The counterpoints are just there isnt much of a reasonable plugin or source to see if its a disconnect or an accident such as black outs/ time outs/ etc.. That's why I'm supporting @Mindarchy idea (not his examples! His philosophy about the problem!) above. If the combatloggin plugin sees the difference between a disconnect and an accident then yes, I'll support this idea.

 

[ZiHAMMER]

Yeah i like reading =)

Click to shrink...

"...we hope..." doesn't mean it is on the list.

 

[MagicalWetToast]

An alternative could be a one minute or shorter combat log grace period or sorts in which the pvp active (non pacifist) player has the ability to get on and not face a penalty. If not the player will drop there inventory completely armour and all. If the player repeatedly logs on and off trying to reach a destination like there house by abusing the timer a three strike rule could be put in place making them drop everything. I believe that this would address the concern of players that have not so stable connection. It would also provide a more reliable method of enforcing combat logging making it in my opinion more severe. The only down side of this is I do not believe such a such a plugin exists, meaning it if possible it would take some coding from cay.

Feel free to post any ideas or reasons why this would be a good idea or bad and if it is not fair to any member of the server.

 

[TheComputerGeek2]

I believe this problem is being tackled wrong. Combat logging is not the problem, the problem is that staff do not have a good resource to identify combat logging and punish it with besides video evidence. Therefore my solution:

When a staff member does /stats on a player, it should include these extra bits of information:
Logout Location:
Logout Situation (In PvP/Not in PvP):
Time since being hit by a player before logout:

Click to shrink...

I think this is a wonderful idea proposed, but there is something I think could be added to it, for example their remaining health and possibly active status effects. It might also make sense to allow recent previous records to be accessed along side to see if it is a potential repeated offense. Either way, the base idea is already great, I'm just looking for ways to make it even better.

 

[Athorian]

Its arguable because sometimes people get kicked from the server while in combat because of lag. This means the player isn't at fault but they would still get punished because of the plugin.

 

[TheTerrawr]

Its arguable because sometimes people get kicked from the server while in combat because of lag. This means the player isn't at fault but they would still get punished because of the plugin.

Click to shrink...

The server can tell the difference between a forced DC and a delog.

 

[TylerJG92]

I am against the idea of a plugin that moderaties combat logging. In manny cases (or at least my cases) My computer dosent handle minecraft all that well, and has crashed many times durring combat. I hate it. I am however saying that if you are worried about combat loggers, that you put in a ticket to the staff and ask them to watch the combat and then they can do something about and combat loggers. (and this way will make it so that those who do crash durring combat wont get jailed for their game failing on them....) that is my own opinion and i stick to it.

 

[TylerJG92]

The server can tell the difference between a forced DC and a delog.

Click to shrink...

and no, technicaly it cant. all it knows is you timed out, it "times out" when you crash and when you physically log out (sorry i didnt say this sooner)

 

[minecraftin_king]

A lot of the time pvp causes me to crash, so I would lose all of my items if I wasn't able to escape a raider, I don't think this is a good idea.

 

[niceguy11]

I don't pvp but combat logging is a problem and it'd be great to have a plugin what does that because I have had a few experiences which have annoyed me and it'd help you making a ticket about it.

 

[SuperSaiyanWoff]

THough I have never really had a problem with the "real" PvPers combat logging, it is annoying when you hunt someone and they do it after you almost kill them.

I agree that it would be nice if there was a way to end this.