Activity and Transparency
I would dearly like whether or not you are active to be accurately shown in account. It is incredibly frustrating to be demoted or removed as GL at the end of the week when it shows you as active in your account. Especially given that that activity doesn't count towards the next week either. You can get demoted or removed as GL even if you're active every single week for months.
This functionality is already available. If you type 'whois Geras', you will see if the code considers you active, it says, "Active: Yes|No". On the account, characters are already marked active/inactive by whether or not they're white {{w or grayed out with {{D on the account list.
How Activity Works:
The Active flag is set at 1 hour per week. RPing for less than an hour in any given week is not active. It is a binary threshold - either you RPed for 1 hour and 1 second, or you were not active that week.
On Saturday nights at 12am system time, the game will go down the list of all players. If a player is an inactive GL, they will receive an automatic approval hit for going a week without representing their guild. All player's RP timers are reset to 0 and they are inactive until they reach the 1 hour of RP mark in the next week.
The situation described of being "active" all month and still getting booted does not happen.
Possible Changes
I wouldn't be against reporting in brackets any given character's activity levels per week, but we've shied away from giving this information out mostly because we don't want to scare our most active players away... (OMG, I spent 76 hours on TI this week? I'd better go get some sunshine!!) <-- believe me, we have players who would fit that criteria. :)
How Activity Works:
The Active flag is set at 1 hour per week. RPing for less than an hour in any given week is not active. It is a binary threshold - either you RPed for 1 hour and 1 second, or you were not active that week.
On Saturday nights at 12am system time, the game will go down the list of all players. If a player is an inactive GL, they will receive an automatic approval hit for going a week without representing their guild. All player's RP timers are reset to 0 and they are inactive until they reach the 1 hour of RP mark in the next week.
The situation described of being "active" all month and still getting booted does not happen.
Possible Changes
I wouldn't be against reporting in brackets any given character's activity levels per week, but we've shied away from giving this information out mostly because we don't want to scare our most active players away... (OMG, I spent 76 hours on TI this week? I'd better go get some sunshine!!) <-- believe me, we have players who would fit that criteria. :)
I think this is the problem Geras is describing:
He RPs for 1 hour on Saturday the 7th, and not again the rest of the week.
On Saturday the 14th, he checks. The code says he's active. He goes to bed.
Rollover hits at midnight and it becomes Sunday the 15th. The code is now checking from the 8th-15th, and he appears inactive. Hence, he is deemed inactive at that weekly checkover.
He RPs for 1 hour on Saturday the 7th, and not again the rest of the week.
On Saturday the 14th, he checks. The code says he's active. He goes to bed.
Rollover hits at midnight and it becomes Sunday the 15th. The code is now checking from the 8th-15th, and he appears inactive. Hence, he is deemed inactive at that weekly checkover.
Or less extreme versions of this, yes. It usually ends up more like I notice I'm inactive on the 14th and RP for 50 minutes, and then seeing that I'm active I'll give in to exhaustion and go to sleep, not realizing that that activity includes 20 minutes of RP from the previous Saturday. I probably get it worse than others since my poses tend to fall just short of the cut-off for gaining rpxp, so I end up RPing without it counting to XP, and it's not that easy for me to judge how much of an RP session has counted towards activity for me. It's incredibly frustrating to think you've met the activity requirements for the week and then find out you fell a couple minutes short.
In no week will the code report what happened in the previous week plus the current week, nor will the code check for the week coming. If your activity is valid and it is before Saturday cutoff, then you won't get a hit. In any week where you show active, you will not get a hit when the cutover happens.
In my view, this issue is simply because Geras didn't know how the code works, which is why I explained when the cutoffs were and what is happening.
If he has an hour of activity on Saturday the 7th, then rollover happens, he will be inactive when he checks 1 minute after midnight on the eighth with 0 on his timer. On Saturday the 14th, either he was active from the 8th to the 14th or he wasn't. There is no "I RPed for 50 minutes on Saturday the 14th, showed active and got a hit". It would be "I RPed for 50 minutes on Saturday and I thought that was enough because I didn't know I could check it and was disappointed to register a hit when the tickover occurred". If he RPed 20 minutes on Sunday and 50 minutes on Saturday, all within the week of the 14th, he's active. One minute after the rollover, he's inactive again.
In all honesty, with these low tolerance levels, I don't see why someone at these levels low enough to get a hit would be viewed as active enough as a GL not to deserve it. The thresholds for activity are extremely low - far lower than would be necessary to do a GL's job. We automate them at such low tolerance levels for the sake of being absolutely sure of who truly inactive, not because 1 hour activity a week implies that a GL is doing a remotely acceptable job. The average active player RPs approximately 10 hours a week.
Ultimately, this is harsh to say, but I think it's the truth: GLs who slip below 3 hours a week, especially on a consistent basis, probably need to assess whether or not they have the time for the role. There are other people out there who would like a chance to take the reigns of leadership, so if a GL is just occupying a seat with no movement, it's probably appropriate for them to get hit 'til their gone. In fact, one of my frustrations is waiting the obligatory 4 weeks for an inactive GL to be ousted for inactivity just to be courteous to them and the possibility that they have valid reasons that they're away.
In my view, this issue is simply because Geras didn't know how the code works, which is why I explained when the cutoffs were and what is happening.
If he has an hour of activity on Saturday the 7th, then rollover happens, he will be inactive when he checks 1 minute after midnight on the eighth with 0 on his timer. On Saturday the 14th, either he was active from the 8th to the 14th or he wasn't. There is no "I RPed for 50 minutes on Saturday the 14th, showed active and got a hit". It would be "I RPed for 50 minutes on Saturday and I thought that was enough because I didn't know I could check it and was disappointed to register a hit when the tickover occurred". If he RPed 20 minutes on Sunday and 50 minutes on Saturday, all within the week of the 14th, he's active. One minute after the rollover, he's inactive again.
In all honesty, with these low tolerance levels, I don't see why someone at these levels low enough to get a hit would be viewed as active enough as a GL not to deserve it. The thresholds for activity are extremely low - far lower than would be necessary to do a GL's job. We automate them at such low tolerance levels for the sake of being absolutely sure of who truly inactive, not because 1 hour activity a week implies that a GL is doing a remotely acceptable job. The average active player RPs approximately 10 hours a week.
Ultimately, this is harsh to say, but I think it's the truth: GLs who slip below 3 hours a week, especially on a consistent basis, probably need to assess whether or not they have the time for the role. There are other people out there who would like a chance to take the reigns of leadership, so if a GL is just occupying a seat with no movement, it's probably appropriate for them to get hit 'til their gone. In fact, one of my frustrations is waiting the obligatory 4 weeks for an inactive GL to be ousted for inactivity just to be courteous to them and the possibility that they have valid reasons that they're away.
I know someone you can talk to in order to speed that process up a bit.Kinaed wrote: In fact, one of my frustrations is waiting the obligatory 4 weeks for an inactive GL to be ousted for inactivity just to be courteous to them and the possibility that they have valid reasons that they're away.
-
- Information
-
Who is online
Users browsing this forum: Google [Bot] and 3 guests