Ban\Permaban for disconnect abusing reports

[enricksolt 2]

One of the main problem with the game right now is when you shoot at someone and wound him, in most of the case, he just disconnect while laying on the ground. Avoiding death and loot lose.

A way to resolve this, IMO, is give the player the chance to report him to the server's admin. If people keeps report him for this he just get Banned\Permabanned, based on the admin decision.

For example: this morning i was with 2 friends at Berizino, on the hospital's roof. After a while another survival get up the stairs and reach the roof, he shoot at us (with a DMR) and kills one of us. We manage to wound him, but soon as we shoot him he just disconnect. Me and my other friend were on the roof, waiting him for reconnect. After 15 minutes we leave the roof, and right after we get down the stairs he shoot us from an unknown position, killing my other friend.

Make your own conclusions.

[griffinz 2817]

One of the main problem with the game right now is when you shoot at someone and wound him' date=' in most of the case, he just disconnect while laying on the ground. Avoiding death and loot lose.

A way to resolve this, IMO, is give the player the chance to report him to the server's admin. If people keeps report him for this he just get Banned\Permabanned, based on the admin decision.

For example: this morning i was with 2 friends at Berizino, on the hospital's roof. After a while another survival get up the stairs and reach the roof, he shoot at us (with a DMR) and kills one of us. We manage to wound him, but soon as we shoot him he just disconnect. Me and my other friend were on the roof, waiting him for reconnect. After 15 minutes we leave the roof, and right after we get down the stairs he shoot us from an unknown position, killing my other friend.

Make your own conclusions.

[/quote']

He probably joined a diff server, moved, and rejoined your server

[enricksolt 2]

He probably joined a diff server' date=' moved, and rejoined your server

[/quote']

I perfectly know it and that pisses me off a lot. Especially because he do that for kill us and not for run away.

[blackbeard06 16]

That little bastard! It amazes me to see the level these people go to cheat ill vote for a Disconnect abuse rule.

[donp 0]

Next time read changelog!

* [FIXED] People can exploit unsaved states by disconnecting or alt+F4 before save

* [NEW] All statistics now syncronized on disconnection, as well as regulary

P.S. Ban for disconnect? yeah, sure... :dodgy:

What next? Ban for stealing from backpack?

[enricksolt 2]

P.S. Ban for disconnect? yeah' date=' sure... :dodgy:

What next? Ban for stealing from backpack?

[/quote']

Let's make the point: stealing from another guy's backpack is lame. If you catch him, be polite and ask him to give you the stuffs back or kill him, there's nothing more you can do.

But disconnect to avoid death, "teleport" yourself by changing server for kill the guy who was attempted to kill you, is cheating, atleast for me.

[n3uro 7]

Seconded. If it were for me, I'd find a way to add a small delay between disconnection and when the player actually disappears, like eve online and some ultima online shards i played on do.

This way you have to find a safe spot to logout and hope noone gets to you in those two minutes, and you remove the people who disconnect to avoid getting zombed or killed by players.

Of course there's no way to prevent people from doing "planeswalking" to other servers to get away, but if I understood correctly, the servers at release are going to have their own DB of players so it won't be an issue anymore.

Another palliative could be to add a small delay that prevents from shooting right after spawning in for some minutes, but I see more cons than pros to this. Just throwing thoughts around...

edit: donp the changelog fixes people dying and immediately disconnecting to prevent the server to register their deaths. It does not do anything to prevent them from avoiding a second, lethal hit after they get wounded. They can disconnect when wounded, log to a different server, bandage, eat a cow to get blood, even scavenge some ammo, move to a vantage point then get back to the original server while the poor sobs that were fighting him are still there and looking for him.

Plus, this is not about butthurt or wanting the game to be easier, it's abusing of game mechanics that are definitely not intended to be. Stealing from backpacks is a bit unrealistic given the lack of feedback to the players, but it's perfectly legitimate given the scope of the mod. Server jumping and popping out of existance by disconnecting, on the other hand, doesn't really fit into that scope, imho.

[bigmanshawn 0]

Keeping people's characters online is actually a difficult challnge with ArmA. The only real method to catch a player disconnecting is the OnPlayerDisconnected event handler, but the big issue with this is that the player's object returns null 1 frame later, so there is no real reliable way to catch it and do much of anything about it as far as I know. Now Rocket may have something up his sleeve, but when I was developing a presistent system using CallExtension I ran into this issue and could find no good way around it.

[n3uro 7]

Oh, well.

I'm not a modder, but i noticed that on disconnect the players do not really pop out of play, but they play a death animation and immediately disappear, suggesting that some kind of placeholder still is in game for playing those animations (unless they're client side). If you could catch the disconnect, pass the player id to a puppet entity, and spawn it in place of the player, it could receive further damage and be treated as if it was in fact that player (after all, the player entity exists in the database, not in the game servers, so you could link it to another puppet on the fly, right?).

[iamredseal 1]

Keeping people's characters online is actually a difficult challnge with ArmA. The only real method to catch a player disconnecting is the OnPlayerDisconnected event handler' date=' but the big issue with this is that the player's object returns null 1 frame later, so there is no real reliable way to catch it and do much of anything about it as far as I know. Now Rocket may have something up his sleeve, but when I was developing a presistent system using CallExtension I ran into this issue and could find no good way around it.

[/quote']

Using and Rcon tool will keep a database of players that have visited your server. You could look the player up in the database when seeing the message.

My big question is, what is the command to send a server globalchat message of the player's name when they disconnect? I can't find an example anywhere using the parameters and the event handler.

BTW, the Rcon tool I have been using (still has some kinks in it) is the Arma II Rcon GUI. There is also a BE Rcon tool that seems more command line. I noticed today that is must be pulling the banlist from BE because our banlist just got populated over the weekend and no one on our server initiated them. Kinda nice!