Dancer Archive

I was attempting to cut the Formal dance flourish timingdown to tenths of seconds in an effort to make it macroable (so I don't have torely on guessing to havethe next flourish startexactly at the end of the last one), and I realized that sometimes a flourish can be called at 13.8 seconds, and other times I'll have to wait 14.1 seconds. I'd painstakingly gone through each flourish to cut it down to the shortest possible pause between flos, only to realize that it wasn't working when I plugged it into a macro. *grumble*

Example:

/flo 2;/pause 15.8;/flo 4 ------- worked perfectly in testing

/m FormalB --> /startd Formal;/pause 1;/flo 2;/pause 15.8;/flo 4 ------/flo4 came to early

Obviously, I can pick the general point at which the flo ends and throw in 5 repetitions with /pause .1 in between to cover a full half-second in difference, but why can't these flos last the same length of time every time!?

I'm sure it has to do with client connection speedissues and server latency (all that jazz), but ARGH, I needed to vent about it Can't they make the timing a client-side operation? Why does the SERVER have to tell me when I can /flo again?

~Til Kismeta~
I'm a dishonest man, and a dishonest man you can always trust to be dishonest.
It's the honest ones you want to watch out for, honestly. Because you can't tell when they're going to do something incredibly...stupid.

Nvm, ignore me I'm just all turned about now. Think I'll have to do this another way....

~Til Kismeta~
I'm a dishonest man, and a dishonest man you can always trust to be dishonest.
It's the honest ones you want to watch out for, honestly. Because you can't tell when they're going to do something incredibly...stupid.

Panthu, I want a /stopalias or /stopmacro function

~Til Kismeta~
I'm a dishonest man, and a dishonest man you can always trust to be dishonest.
It's the honest ones you want to watch out for, honestly. Because you can't tell when they're going to do something incredibly...stupid.

I mean /stopalias <alias> or /stopmacro <macro name>. Specific calls to shut down a sub-alias, etc. I want to be able to start and stop over-flos so I can sequence the flos, instead of having them go at random. Difficult to explain.

~Til Kismeta~
I'm a dishonest man, and a dishonest man you can always trust to be dishonest.
It's the honest ones you want to watch out for, honestly. Because you can't tell when they're going to do something incredibly...stupid.

I didn't see this. Flo length is a big deal to me, as some of you know. I want for us to have commands to start and stop flos at a set time, so you could macro a routine and get consistent results... or at least be able to hotkey certain mixed combos instead of having to do it all by hand every time watching like a hawk and having to ignore patrons. Also, I want them to count for Ent Healing/Buffing. We might not ever be able to be rewarded for putting effort into being pretty, but we could at least stop being penalized for it.

Above all else, we need the small anims we've been asking for like short Jumps, Turns, and Leaps that can be mixed in with any routine. We also need to gain Flos separate from Base Dances imo, so we could use any flo from any base dance as long as we have earned them.

Anyway, the info you are wanting about the Alias/Macro "pass off" method can be found in the threads talking about "toggles." Check the Fencer Forum, I think there is a bit on it in the COB Sticky. (if that's still there, I haven't been over there for a while... shhhhh, don't tell Minerunner)

Problem with doing what you're trying to do is lag. Really nothing you can do about this either, if you have it timed to the exact tenth of a second then if the first command lags even slightly on the way from your computer to the server, due to any hickup along the way, and the second flourish doesn't hit the same lag, then the server will see the second flo as being early. Trying to bandflo this way compounds the situation further...

Ping statistics for 64.37.156.19:
Packets: Sent = 1000, Received = 999, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 604ms, Average = 71ms

An example ping from me sending 1000 1k pings to www.starwarsgalaxies.com, most were below 100, most were in that 20-70 range, its those occasional spikes to 600 that messes games up

Well, sort of...

What Til was talking about was an overflo switching technique, which can be done with toggles.

What I was talking about was a legit method of "mixing" (among other things). Lag will always be a factor in any MMO, but the way we call our flos can be changed to improve results for us andcertain things can be moved tothe client.If lag was such a crippling factor, no MMOs wouldbe able to have synergies or paired animations.

There are many ways to make sure that everyone sees the same thing... what you can't guarantee is that they'll all see it at the same time. *shrug* In our case, it's more important thatpeople see the same anim order and transitions that we see than when they are actually seeing them.

Why can't we have a chain command, so that when the command is finished, the next is performed, and we don't have to have any /pause commands at all??

Jame'thiel Dreamweaver

Master Tailor, Colonel - Rebel Alliance, Gorath Server

---

Lt. Sharven Figohic - Infinity
♥ Wardancer & Space Beast Of Prey ♫
Moonshadow Wiki & ForumsMoonshadow info on swg-wiki

---

Lt. Sharven Figohic - Infinity
♥ Wardancer & Space Beast Of Prey ♫
Moonshadow Wiki & ForumsMoonshadow info on swg-wiki