Dancer Archive
Thread: Lets Find a Solution for Everyone
Page 2 of 2
Panthu
Sun Jul 04, 2004 12:53 pm
#14
Drygo wrote:
While I am honored that you think my post is Corre forum worthy, please do not use me as a tool in your sick and twisted game for world domination.
Oh, it's too late... you are in deep now baby! 
DanceRulez
Wed Jul 14, 2004 6:10 pm
#16
I always wondered why they don't just use the built-in AFK timer in the client. It already exists, and as it is now a player can already set it, as a courtesy, to automatically flag them as AFK after a set time. Unfortunately a lot of people spend a fair amount of effort trying to get around this courtesy. Still the point is the client is already monitoring for user interaction so why not use this to automatically force someone into AFK status after a maximum preset time value and then notify the server and react accordingly. I also think that all macroed and aliased commands should be tagged as such (to distinguish them from active user commands) when sent to the server. Then you could also detect people who are macroing too much. Anyone might use looping macros for a bit, but what ATK player really needs a macro continuously looping in the background for an hour or more at a time? Anyway, those are some of my own ideas for a solution to the AFK problem.
Dreamland
Wed Jul 14, 2004 10:47 pm
#17
I think that an important tool they need to fix is the ability to get a musican and dancer buff at the same time. Back about january-ish i used to routinely go to a musician/dancer team on dathomir to get both my mind and secondaries buffed at the same time. This ability gives the at the keyboard entertainer an edge over the buffbot as two could team up to do the buff in half the time a buffbot does.
I hadnt even realised this didnt work till a friend andI wanted to team up to put a dent in the theed buffbot buisness and found it was no longer functional.
Kreistor
Thu Jul 15, 2004 6:29 am
#18
DanceRulez wrote:
I always wondered why they don't just use the built-in AFK timer in the client. It already exists, and as it is now a player can already set it, as a courtesy, to automatically flag them as AFK after a set time. Unfortunately a lot of people spend a fair amount of effort trying to get around this courtesy. Still the point is the client is already monitoring for user interaction so why not use this to automatically force someone into AFK status after a maximum preset time value and then notify the server and react accordingly. I also think that all macroed and aliased commands should be tagged as such (to distinguish them from active user commands) when sent to the server. Then you could also detect people who are macroing too much. Anyone might use looping macros for a bit, but what ATK player really needs a macro continuously looping in the background for an hour or more at a time? Anyway, those are some of my own ideas for a solution to the AFK problem.
Hmm, this solution sounds vaguely familiar...
I'm behind this one. It's a great starting point for the Devs to work from.
Page 2 of 2