Page MenuHomeFeedback Tracker

Please find a way to disable ghosting and immediate logging.
New, WishlistPublic

Description

This should be one of the number one issues Rockets development team should be working on. It ruins the experience to a level of frustration that will kill this games chance if it's not addressed. Players should have to be out of combat for at least one minute before being able to log out. And should have to wait 15 minutes before logging into the same server they just logged from. If they do log out and log in after 15 minutes but log out for a second time they should be banned from that server for 24 hours. Guys let me know your input and comments to improve this it needs attention.

Details

Legacy ID
1353758038
Severity
None
Resolution
Open
Reproducibility
Always
Category
General

Event Timeline

TheMoungatalia set Category to General.Jan 21 2014, 1:00 AM
TheMoungatalia set Reproducibility to Always.
TheMoungatalia set Severity to None.
TheMoungatalia set Resolution to Open.
TheMoungatalia set Legacy ID to 1353758038.May 8 2016, 4:32 PM
TheMoungatalia added a subscriber: TheMoungatalia.

You did not read my solution I presented correctly. And its not a permanent ban that I suggested.

" You don't agree with me so you must be guilty"
Personally I feel that kind of logic is flawed.

I actually do want solutions to Combat Logging, Ghosting and Loot-Hopping.

If you see here : http://feedback.dayzgame.com/view.php?id=7949, I have suggested a solution that deals with all cases.

However I don't feel the current implementation adequately addresses those problems without penalising innocent players.

Banning someone for logging out after 15 minutes seems( correct me if I have that wrong) would actually cover a large amount of cases where someone isn't Loot-Hopping or Ghosting.

That's fine you can downvote all you want but I don't see you guys suggesting any other ways to prevent it. I know it will be partially dealt with in the new version coming out this week but it's sad you just downvote the issue. Makes it look like you guys exploit it.

down-voted because I think you need to put more thought in the implementation