In-Game Reporting (Runners and Inactive Players in Team Battles) (Full Version)

All Forums >> [Artix Entertainment Games] >> [EpicDuel] >> EpicDuel Suggestions



Message


drekon -> In-Game Reporting (Runners and Inactive Players in Team Battles) (3/21/2013 14:51:56)

In team battles, when a player leaves before dying, the UI that displays their name, health meter, and other button options should remain in place until the battle is over. This will allow for easier reporting of runners and provide enough solid evidence, if needed, for Moderators to take appropriate action. Over time, this will help to weed out players who intentionally flee battles. Also, a time-stamp should be added to the notification (RED) bar for when connection is lost. This way, players who often fall victim to lost connection can provide a screenshot of it in case they are reported. The time-stamp will provide proof that the player did, in fact, lost his/her connection at or around the time they were reported for fleeing the battle. Having the time-stamp in the game itself makes it harder for people to forge.

Also, something should be done about players who join team battles and intentionally miss their turns consistently. Perhaps tracking the number of times a turn is missed over the course of certain amount of battles (i.e. 10). If more than 70% of turns are missed, give the player a warning. If this behavior continues, automatically report the player with all collected data for a Moderator to assess and take appropriate action. Temporary/permanent bans from team battles are effective deterrents and ought to be used accordingly.

Occasional bugs may cause players to lose their turns so it should be focused on players with high percentage of missed turns.




Sir Caden -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/21/2013 15:12:34)

Supported Mr Overlord




AQWorldsFarmer -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/21/2013 15:19:36)

Sometimes its a disconnection. I get disconnected a lot and called a runner. I really think its annoying.

But due to the fact that you addressed this in your post, i will support as long as devs can find out if its a disconnection or not.




Mother1 -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/21/2013 15:26:32)

Only one problem with this idea. The system can't tell the difference between a connection lost and a runner. Runner could just use the time card to get out of trouble with this idea, and what about people who don't know how to use screen shots, or can't use it with their computers. Not all computers are equal and people who get disconnected could get in trouble because of this idea, while runners could use the same system to keep out of trouble.




AQWorldsFarmer -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/21/2013 15:38:05)

^ how do we know they cant tell when you loggout/disconnect, there is a difference between the 2.
Although I'm not saying that absolutly 100% can tell, im not sure.




drekon -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/21/2013 16:07:54)

@Mother1, the time-stamp (date and time) would only display on the red notification bar that shows the connection loss alert. Players who simply run from battle would not see a time-stamp. A typical runner flees from battles often and likely does not take note of the specific time they run from each battle. Even if they did, they would have to go through a lot of trouble to forge the time-stamp of each event. You may have a point about some players not knowing how to take screenshots. This could easily be overcome by either providing a button to take the necessary screenshot, or simply add instructions on how to do so.




Exploding Penguin -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/21/2013 19:55:19)

From what I've learned from other people, I think you can tell who's a runner and who D/Cs from how long it takes to leave the fight. If they just randomly disappear, then they're probably a runner. If it lags a lot before they disappear, then they probably D/Ced or the battle failed to start. This should only be used for reporting those known to have some motive behind running; sometimes I accidentally close out of the window in the middle of a 2v2 and I don't want to get reported for running cause of that...




gangster a -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/22/2013 4:46:28)

sometimes people suddenly have to do other stuff with their real life and exit the battle that cant be helped so that would be a problem




drekon -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/22/2013 15:41:12)

@gangster a, if that be the case, then one can simply use the chat to notify the other players instead of just leaving the battle. If a player just quits in the first round or two without saying anything then it's safe to assume that is not the case.




gangster a -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/22/2013 16:12:53)

^ thats exactly what i do but they might still end up reporting




drekon -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/22/2013 22:04:21)

Most players are considerate enough to understand your situation as it happens to everyone from time to time. Besides, I doubt you would do that frequently enough to be concerned.




Frost the Phoenix -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/29/2013 19:29:19)

I have a way to avoid all the problems you just brought up.
If a player does any of the following

Runs from battle (on purpose)
Disconnects (accidentally)
Miss's a turn

Then the player they are allied with takes control of the character and get the end of battle bonus for both.

for missed turns

first offence

Ally gets the to chose your attack that turn.

second offence

the ally get control of your character and you get removed from the battle.

If a player does any of the 3 items in the list more then 3 times in an hour they are banned from 2 vs 2 and Juggernaut for 1 hour (from the last time) the second time they get banded for 24 hours.

The 1 vs 1, npc (1 vs 1) battles and leaving after death do not count towards the ban as they don't cause ant problems to others. NPC (2 VS 1) still counts.





EpicIsEpic -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/30/2013 13:23:19)

@Frost the Phoenix
Sometimes it is really important to miss a turn e.g. with the new robot. Npc 2 VS 1 is stupid because you have to be ally and if your ally sees that the fight is lost and he has to do other stuff.
But i like idea apart the fact that to programm that it would take ages like the idea tho.




Frost the Phoenix -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/30/2013 20:29:21)

@EpicIsEpic i did say that you ally gets the choice to move for you so i guess i forgot to add that in.
So you could counter that by if you ally also chooses not to attack then it doesn't count, as as you ally also thought it was a good idea
It should only affect you if your ally chooses an attack for you.
does that sound better?




Sesura -> RE: In-Game Reporting (Runners and Inactive Players in Team Battles) (3/30/2013 22:13:53)

I support your post but I would appreciate if you could read this as well. This post is "kinda" like mine if you'd look closely. My post also promotes avoidance of runners and some people who really experience some serious lag issues. :) Link here!




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition
0.09375