Dancer Archive

Thread: I guess buffbots aren't going away after all.

Tiaga
Fri Aug 13, 2004 1:48 pm
#1

While it was probably poorly worded, I think the answer was merely saying that the toolbarSlot command was not going away. I can check for a clarification if you wish. They don't usually have a lot of time to formulate a well worded answer in these answers.

Ever since the announcement I started nagging TH about it. Labelling it as removing recursive macros is IMO a fallacy. You can do the same things without recursive macros. With the direction I've been trying to push things, technically it wouldn't be removing recursive macros at all, just long running macros.

Just don't fall into the trap of "This is the only way it can be done". There are ways to have a macro called from another not start over with a fresh timer, if that is the approach they decide to take.



Inside my heart is breaking, my make-up may be flaking
But my smile still stays on
My soul is painted like the wings of butterflies
Fairytales of yesterday will grow but never die
I can fly - my friends
SWG Entertainer.com Fashions by TK

Panthu
Fri Aug 13, 2004 2:07 pm
#2






Ravanne_Esi wrote:

From DEV IRC Chat:



[18:20] *Rennio{Flurry}* "With the proposed removal of looping macros, will entertainers still be able to use /ui action toolbarSlot00 loops in order to communicate with customers, or will they still be forced to keep repunching short macros? The removal of looping macros solves our buff bot problems, but limits us in the customer service we are allowed to provide to patrons.


*Rennio and to everyone who is concerned about recursive macros, we are not going to remove the /ui macro commands. We are going to use a different method to encourage people to play "at the keyboard". Removing those basic abilities for players to use the GUI command would be a huge inconvenience and we dont want to do that.






Removal of recursive macros is meaningless, with the /ui action command you can still do infinate action loops.


/shrug


I knew it was too good to be true.





I agree with Tiaga. This is still going to happen, this just wasn't the way to do it. I'm hoping for a "time out"solution personally. Like, you can run as many loops as you like and call as many other macros as you like for only so long, then you have a forced dump. This would be much better for both combat purposes and also for our own valid Live macro uses. They haven't dropped the ball on this, they are just trying to do it more completely and with out hurting anyone's valid ATK play.




P A N T H U Y GlitterUsagi
M i n d B o d y S p i r i t
Dancer ImageDesigner Doc

Luciee_Depri
Fri Aug 13, 2004 7:27 pm
#3


I had hoped they would start simple, perhapswith a strong statement that AFK gameplay was not allowed and would result in negative action against your account. If you were in your house, unlikely to be seen, bothering no one, then no big deal (eliminating the need to mess up combat/crafting macros used at the keys or out of the public eye). The majority of people would then avoid being afk in public (entertainers, combat xp farmers, loot farmers, etc. who seem to irk others the most) because they could be reported and possibly suspended/banned. Of course there are flaws with this type of plan but there are flaws in nearly everything that's been suggested as possibilities thus far. Not everyone would getcaught. Still, I think the chance of being caught would serve as a good deterent.
Sigrun
Fri Aug 13, 2004 8:12 pm
#4






Luciee_Depri wrote:


I had hoped they would start simple, perhapswith a strong statement that AFK gameplay was not allowed and would result in negative action against your account. If you were in your house, unlikely to be seen, bothering no one, then no big deal (eliminating the need to mess up combat/crafting macros used at the keys or out of the public eye). The majority of people would then avoid being afk in public (entertainers, combat xp farmers, loot farmers, etc. who seem to irk others the most) because they could be reported and possibly suspended/banned. Of course there are flaws with this type of plan but there are flaws in nearly everything that's been suggested as possibilities thus far. Not everyone would getcaught. Still, I think the chance of being caught would serve as a good deterent.







You hit the nail on the head. This is actually the *only* way to solve the AFK "play" problem. No matter what the 6 devs on this game think they can code, the 5000 people who really, REALLY want to "play" AFK are going to find a way around it.


But don't just trust my word for it. Look at the other MMOG's out there. Research what their policy reunattended play is and how they enforce it.


Why is SOE not learning from them? Heh, why does SOE do a lot of the dumb crap they do?






Ingame Names: Sif @ Bria, Chilastra, Flurry, Naritus, Starsider | Hiordis @ Kettemoor | Freya @ Tempest
Quotable: It's pretty freaking underwhelming when the story turns out to be you, alone, in a field, for two weeks, punching toads. | At least SOE lasted a year before they went Turbine on us.
Esharra
Fri Aug 13, 2004 9:08 pm
#5

For several years I worked for a MMOG that was utterly destroyed by unattended play. Finally the devs had enough and said "No unattended play or your account will be banned". At first the player base laughed it off. They wrote alarms into their macros, coded in reply messages saying they couldn't speak English and daily thumbed their noses at the devs with forum posts about their latest work-around and how they would never accept the change to the Code of Conduct. A lot ofaccounts got banned. The game improved. End of story.



Esharra ěsh-äŕ-rä, noun
1. Entertainer
2. Bounty Hunter
3. Smuggler

"One man's oddity is another man's routine." -Bertos Goodner (a dancer)


Beery
Fri Aug 13, 2004 11:00 pm
#6

"I still have faith. If not through a timer of sorts, then by preventing a ui action from calling itself. You couldn't place a macro in the toolbar slot and then have it call itself over and over again. But you could still use the ui command in your macros, just so long as they didn't call themselves."


I don't know if anyone else has mentioned this, but this wouldn't work. In order to get the same result as a self-calling macro, players could use two almost identicalmacros that simply called one another.



--------------------------------------------------------------------------------------

Since June 2004, running one of the game's first completely nonviolent characters. Testing the limits of non-combat MMORPG play and trying to have fun into the bargain (although the developers make it difficult).

Combat is no longer compulsory.
Ravanne_Esi
Sat Aug 14, 2004 12:32 am
#7

From DEV IRC Chat:



[18:20] <Brekkee> *Rennio{Flurry}* "With the proposed removal of looping macros, will entertainers still be able to use /ui action toolbarSlot00 loops in order to communicate with customers, or will they still be forced to keep repunching short macros? The removal of looping macros solves our buff bot problems, but limits us in the customer service we are allowed to provide to patrons.


<TH> *Rennio and to everyone who is concerned about recursive macros, we are not going to remove the /ui macro commands. We are going to use a different method to encourage people to play "at the keyboard". Removing those basic abilities for players to use the GUI command would be a huge inconvenience and we dont want to do that.






Removal of recursive macros is meaningless, with the /ui action command you can still do infinate action loops.


/shrug


I knew it was too good to be true.





Ravanne Esi
Master Dancer, Master Entertainer, Master Musician
Ragin' Rancor Enterprises
New Hope, Naboo
-

Sigrun
Sat Aug 14, 2004 12:38 am
#8

In another posting, TH indicated that the current line of thinking was to detect how long someone had been running a macro and, if that exceeds some threshhold, the software would stop the macro.


This gives you no AFK infinite loop macros while still preserving the basic "good" functionality of the macro system.


Chill.




Ingame Names: Sif @ Bria, Chilastra, Flurry, Naritus, Starsider | Hiordis @ Kettemoor | Freya @ Tempest
Quotable: It's pretty freaking underwhelming when the story turns out to be you, alone, in a field, for two weeks, punching toads. | At least SOE lasted a year before they went Turbine on us.
QuixoticJedi1
Sat Aug 14, 2004 12:43 am
#9

I still have faith. If not through a timer of sorts, then by preventing a ui action from calling itself. You couldn't place a macro in the toolbar slot and then have it call itself over and over again. But you could still use the ui command in your macros, just so long as they didn't call themselves.



Quix'Otic

Knight Errant of the

Gypsy Court


DemmonA
Sat Aug 14, 2004 12:43 am
#10

you know how they keep nerfing people? well, they really hate afkers so they're gonna nerf them good.
Sigrun
Sat Aug 14, 2004 12:45 am
#11






DemmonA wrote:

you know how they keep nerfing people? well, they really hate afkers so they're gonna nerf them good.






They must have a SERIOUS hate-on for Merchants then...




Ingame Names: Sif @ Bria, Chilastra, Flurry, Naritus, Starsider | Hiordis @ Kettemoor | Freya @ Tempest
Quotable: It's pretty freaking underwhelming when the story turns out to be you, alone, in a field, for two weeks, punching toads. | At least SOE lasted a year before they went Turbine on us.
Ravanne_Esi
Sat Aug 14, 2004 12:52 am
#12






Sigrun wrote:

In another posting, TH indicated that the current line of thinking was to detect how long someone had been running a macro and, if that exceeds some threshhold, the software would stop the macro.


This gives you no AFK infinite loop macros while still preserving the basic "good" functionality of the macro system.


Chill.







If the last command in your macro calls a /ui action then you are starting a new macro and a new timer.





Ravanne Esi
Master Dancer, Master Entertainer, Master Musician
Ragin' Rancor Enterprises
New Hope, Naboo
-

QuixoticJedi1
Sat Aug 14, 2004 12:53 am
#13






Ravanne_Esi wrote:





Sigrun wrote:

In another posting, TH indicated that the current line of thinking was to detect how long someone had been running a macro and, if that exceeds some threshhold, the software would stop the macro.


This gives you no AFK infinite loop macros while still preserving the basic "good" functionality of the macro system.


Chill.







If the last command in your macro calls a /ui action then you are starting a new macro and a new timer.






Not necessarily, completely depends on how you program it. I think we'd best just wait to see what the developers come up with.




Quix'Otic

Knight Errant of the

Gypsy Court


Page 1 of 2
Previous Next