Rules changing: away-from-keyboard rule specifics
Posted: Mon Jan 27, 2020 3:01 pm
As I'm wrapping up the big list of technical fixes behind the scenes, it's a good opportunity to do some housecleaning in the Codex.
Based on the title, if anyone's worried that AFK rules would change completely (to allow AFK playing), the rule overall stays. I watch other shards, and overall how changes in technology affect our lives, and it's really important for the community and the economy that your character's actions have "human input", even if that means just watching it on the 2nd monitor.
A bit of history:
When we started the shard, there was no AFK rule. After a few months, the rule was to respond within 10 minutes, just to prevent people from macroing while sleeping or at work. Btw, those were times when we didn't have mobile data, and even wifi in public places was usually unreliable, so when I went away from home, there was usually no way to check my character or start/stop the macro. Then it turned out, you can get a lot more resources by farming monsters, so we reduced the response time for fighting/leveling to 1 minute. But every now and then, someone is AFK doing some activity, which is actually profitable... and it's a procedure of getting it thought-thru and posted on the codex as one of the forbidden things. And sooner or later, something else that's macroable and profitable, will be found. A couple of years ago, a player was recalling around to check for fallen houses, and at the time I was considering whether that's legit or not - the argument was, that he is at the keyboard when he actually loots stuff from the ground, so he's not actually breaking the rules. But actually, it's this recalling around that makes the profit.
The change
Instead of listing all the things that are forbidden, it would make sense to invert the rule. One has to be at the keyboard if doing any action (clicking on items, moving around, clicking on gumps/menus, speaking). Whenever I've seen someone with a macro running, it was for some kind of gain/profit. There would be exceptions for training skills, and they would have to be defined in a way, so that I can script the conditions right in, and don't have to check the folks who are doing something that's whitelisted (perhaps, whether it's fighting a trainer, either in the training room or a private one).
This will simplify our checks. With the new staff member we're going to be much more consistent with AFK checks, and over time I intend to also script them, so that we can gradually let automation take over this. (with an occasional manual check, to cover any blind spots that the automated systems can't). Well, there there are anti-AFK captcha systems out there (on runuo/servuo forums), though popular server-side scripts tend to have a client-side counterpart... also, things like the captcha and "click the 3 potions that are of the same color" can be broken, and aren't reliable enough.
This would go for public chat announcements as well (selling/buying, come check out the XYZABC shop...)
While on the subject, I'm going to simplify/restructure the Codex a bit. The main page of the codex will likely stay more or less similar. Though this page here, will likely be completely rewritten: http://uoex.net/codex/penalties. The penalties will be simplified a bit, but will remain progressive: repeat offenders will get an increased penalty, but if enough time has passed since the last rule breaking, the penalty is also reduced.
Recalling around is also related to this issue. When doing AFK checks, players sometimes recall around so fast it's hard to even trigger the AFK check on them. It's one of the anomalies of the game, being able to to hold down so many spawn spots at the same time, so I have also been thinking about adding a gradual cooldown to recalling. Recalling a few times would still work witout any delay, and after consistent recalling it would build up, first a few seconds, up to 10-30 seconds cooldown between recalls (same goes for sacred journey, and all versions of instant travel).
Overall, we're consolidating the two Anti-AFK systems (the automated gathering captcha, and manual everything else) into a rule, or few rules, that are easy to understand, make sense of as a whole, as well as to enforce.
So, I'm looking for your input on the subject of AFK:
- what activities should be allowed to be done AFK?
- How frequently being checked is still OK, and when does it get annoying?
- Care to share an AFK-related story from another shard, or some other game?
- Have you ever been jailed for being AFK on Excelsior, how did that go?
- Any AFK-related wisdom that you'd like to share with the rest of the shard?
Based on the title, if anyone's worried that AFK rules would change completely (to allow AFK playing), the rule overall stays. I watch other shards, and overall how changes in technology affect our lives, and it's really important for the community and the economy that your character's actions have "human input", even if that means just watching it on the 2nd monitor.
A bit of history:
When we started the shard, there was no AFK rule. After a few months, the rule was to respond within 10 minutes, just to prevent people from macroing while sleeping or at work. Btw, those were times when we didn't have mobile data, and even wifi in public places was usually unreliable, so when I went away from home, there was usually no way to check my character or start/stop the macro. Then it turned out, you can get a lot more resources by farming monsters, so we reduced the response time for fighting/leveling to 1 minute. But every now and then, someone is AFK doing some activity, which is actually profitable... and it's a procedure of getting it thought-thru and posted on the codex as one of the forbidden things. And sooner or later, something else that's macroable and profitable, will be found. A couple of years ago, a player was recalling around to check for fallen houses, and at the time I was considering whether that's legit or not - the argument was, that he is at the keyboard when he actually loots stuff from the ground, so he's not actually breaking the rules. But actually, it's this recalling around that makes the profit.
The change
Instead of listing all the things that are forbidden, it would make sense to invert the rule. One has to be at the keyboard if doing any action (clicking on items, moving around, clicking on gumps/menus, speaking). Whenever I've seen someone with a macro running, it was for some kind of gain/profit. There would be exceptions for training skills, and they would have to be defined in a way, so that I can script the conditions right in, and don't have to check the folks who are doing something that's whitelisted (perhaps, whether it's fighting a trainer, either in the training room or a private one).
This will simplify our checks. With the new staff member we're going to be much more consistent with AFK checks, and over time I intend to also script them, so that we can gradually let automation take over this. (with an occasional manual check, to cover any blind spots that the automated systems can't). Well, there there are anti-AFK captcha systems out there (on runuo/servuo forums), though popular server-side scripts tend to have a client-side counterpart... also, things like the captcha and "click the 3 potions that are of the same color" can be broken, and aren't reliable enough.
This would go for public chat announcements as well (selling/buying, come check out the XYZABC shop...)
While on the subject, I'm going to simplify/restructure the Codex a bit. The main page of the codex will likely stay more or less similar. Though this page here, will likely be completely rewritten: http://uoex.net/codex/penalties. The penalties will be simplified a bit, but will remain progressive: repeat offenders will get an increased penalty, but if enough time has passed since the last rule breaking, the penalty is also reduced.
Recalling around is also related to this issue. When doing AFK checks, players sometimes recall around so fast it's hard to even trigger the AFK check on them. It's one of the anomalies of the game, being able to to hold down so many spawn spots at the same time, so I have also been thinking about adding a gradual cooldown to recalling. Recalling a few times would still work witout any delay, and after consistent recalling it would build up, first a few seconds, up to 10-30 seconds cooldown between recalls (same goes for sacred journey, and all versions of instant travel).
Overall, we're consolidating the two Anti-AFK systems (the automated gathering captcha, and manual everything else) into a rule, or few rules, that are easy to understand, make sense of as a whole, as well as to enforce.
So, I'm looking for your input on the subject of AFK:
- what activities should be allowed to be done AFK?
- How frequently being checked is still OK, and when does it get annoying?
- Care to share an AFK-related story from another shard, or some other game?
- Have you ever been jailed for being AFK on Excelsior, how did that go?
- Any AFK-related wisdom that you'd like to share with the rest of the shard?