AFK Logout timer

[Adrian]

Being disconnected when training, that is another topic. It is an error and that has to be fixed. Training should be considered being active.

First of all, let me clear up that those that get kicked and then are angry and don't log in again (something really simple to be done) have other reasons and not the logging off to get angry about the game and abandon it. Let's please not mix up things.

Second, there is another thing we have to do, which is sending the user to the Character Selection screen instead of disconnecting them.

With this said, the reasons are several. One is because being AFK for a long time (10 minutes is more than enough to go to the toilet or grab some food or water), specially in Central Saves, annoys people too much as they think they are available players and just standing there. We prefer them to be sent to the Character Selection as many games do.

Also, it interferes with some server calculations on population in some "grey areas" of what is considered activity and what not. We prefer only really active players inside the game. 30 minutes is just too much.

Also, until we change it, this also means the time the server waits for a connection to be fully dismissed.

This has to be polished, of course, but I can't imagine that being kicked after 10 minutes of inactivity can enrage anyone. If that happens, there are surely other reasons piled up.

[GALO ÉPICO]

Yes, in this way you explained it will be very good things really, I really liked the part that so the afk will no longer count as active population because this very disrupts the realm of syrtis where you imagine having 500 online but in fact are 200 active and 300 missing afk just as numbers example. And when setting up spells or waiting to get into a dragon vesper inside a dragon group does not count as inactive afk, then yes I agree that 10 minutes this very good!

Good but even with everything you said I would not see with bad eyes 15 minutes, for me it does not matter because I'm always active, but from 10 minutes to 15 minutes since it was 30 minutes I do not see it badly in 15 minutes, but that's okay if you want to put 10 minutes. If it was a poll / poll type choose the time either 5minut or 10minut or 15 minutes I would vote 15 because I do not find this much for those who stay connected hours.

I know it's simple to connect again just log in to the game, but like a car when the engine dies, just turn on the car and continue but it's annoying that it happens and having to start the car again, I think being disconnected is annoying and it's only connect again but you lose some of the mood of the magic of the thing when it is disconnected, because you can no longer read everything that was written in the chat and can not follow the chat war movement to know what is happening.Bom Summing up 30minut which was I do not see badly in 15mint in my opinion of who stays hours online and does not want to miss a chat message by disconnection.

[Hollow-Ichigo]

Originally Posted by Adrian

Second, there is another thing we have to do, which is sending the user to the Character Selection screen instead of disconnecting them.

This is better than a full dc

[nocruesfr]

Yup this is better.

[erzsi]

Originally Posted by Adrian

First of all, let me clear up that those that get kicked and then are angry and don't log in again (something really simple to be done) have other reasons and not the logging off to get angry about the game and abandon it. Let's please not mix up things.

Second, there is another thing we have to do, which is sending the user to the Character Selection screen instead of disconnecting them.

With this said, the reasons are several. One is because being AFK for a long time (10 minutes is more than enough to go to the toilet or grab some food or water), specially in Central Saves, annoys people too much as they think they are available players and just standing there. We prefer them to be sent to the Character Selection as many games do.

Also, it interferes with some server calculations on population in some "grey areas" of what is considered activity and what not. We prefer only really active players inside the game. 30 minutes is just too much.

Also, until we change it, this also means the time the server waits for a connection to be fully dismissed.

This has to be polished, of course, but I can't imagine that being kicked after 10 minutes of inactivity can enrage anyone. If that happens, there are surely other reasons piled up.

I'm being fairly consistently disconnected about 3-5 minutes into the game, and I'm active (mounted, riding to some fort). This is a recent change, from before Hallowe'en's update. Is this related to that?

Also, when disconnected from the Character Selection screen (or during the login exchange with the client), I'd like to be able to log in without waiting an hour or three. Will this change affect that?

Last time it was an hour and ten minutes. Time before that, I gave up and played another game.

The rest, I have to say, I'm with NGD on the whole thing. I arrive at Central Save, and thirty people are standing there. Doing nothing. 5 minutes is maybe too fast, but honestly, it's not like the server is so crowded it's difficult to get back on. And if you change it to DC to character selection instead of complete logoff, it could stay 5 minutes. I'd be fine with that.

[Kralmoe]

What about those who leave their character for hours running in circles like idiots in the save?

Are they going to get kicked out or they can stay because they 'move'.

[Mashu]

Originally Posted by Kralmoe

What about those who leave their character for hours running in circles like idiots in the save?
Are they going to get kicked out or they can stay because they 'move'.

That should be considered as bot and bannable in my opinion.
It requires constantly sending key press which some script, or putting something heavy on keyboard, anyway it's a hack. Isn't it ? I don't know other ways to keep running like that, if you dont press key character stops.

Repetitive actions should be banable imo, there could be some bot detection system.
Or suspected player could be PM-ed by GM, like they do in other games to check if it's a bot.

Having good stats on players activity is crucial for NGD to optimize server such that it's pleasant for all of us. Having players that cheat the stats, hurts us all.

The same goes to multi-logging from the same IP to dragon wishes, than one character or the other takes actions but not both at the same time. Though this could be solved by allowing to enter portal only people who participated in invasion (this would be fair no matter how people would cry about it).

[Grindelmort]

I dont think people running in circles will be a significant issue if people are just pushed out to the character selection screen.

[Hollow-Ichigo]

Originally Posted by Mashu

That should be considered as bot and bannable in my opinion.
It requires constantly sending key press which some script, or putting something heavy on keyboard, anyway it's a hack. Isn't it ? I don't know other ways to keep running like that, if you dont press key character stops.

Repetitive actions should be banable imo, there could be some bot detection system.
Or suspected player could be PM-ed by GM, like they do in other games to check if it's a bot.

Having good stats on players activity is crucial for NGD to optimize server such that it's pleasant for all of us. Having players that cheat the stats, hurts us all.

The same goes to multi-logging from the same IP to dragon wishes, than one character or the other takes actions but not both at the same time. Though this could be solved by allowing to enter portal only people who participated in invasion (this would be fair no matter how people would cry about it).

You just need to hold down W and Q/E and click off the regnum window. Doesn't require anything though people that do that should still be autologged.

[erzsi]

Originally Posted by Hollow-Ichigo

You just need to hold down W and Q/E and click off the regnum window. Doesn't require anything though people that do that should still be autologged.

That's actually exploiting a bug/glitch in the client. The client should not sustain a keypress if the window is no longer in focus.

I don't know how long it would take to run that bug down and fix it, though.