I will tell you what has changed - voice recognition. The moment
the EQ team started down that path, most of these command line changes were
inevitable.
What you guys need are programmable keyboards\keypads. I have a
58-key programmable keypad I use to do all sorts of things -- its primary
use however is to give me direction keys on BOTH ends of the keyboard, as
well as a better layout for hotkeys, etc. Not to mention I can switch
hot-key banks, and press a hot key button with a simple push of a key.
Since the implementation of all these keyboard commands, I can do damn near
any command or sequence of commands in EQ with my keypad at the push of a
single button.
The price range of the programmable keypads on the internet is
anywhere from 24.95 (a cheap 20-key type) on up. There are two available
from one particular company in 20 ($85) and 58 ($130) key models that allow
key labeling and everything . If you guys are interested I can post some
links for your perusal.
> Well now there's a reason for us to use the /stopsong command. BTW, from
> the example 100 = 10 secs, so time increment would be close to 50. You're
> also limited to 5 lines. Lastly, the pause command can be stacked, but
> must
> be listed first on the same line. Something like this:
>
> /pause 50 /cast 1
> /stopsong
> /pause 50 /cast 2
> /stopsong
> /pause 50 /cast 3
>
> May need to change the time increment to allow for general lag, but that's
>
> what testing is for. Also, there's no space for an additional "/stopsong"
> to stop song # 3, so I guess this isn't a whole fix-all.
>
> More interestingly, my enchanter buddy is lamenting this new addition and
> feels it'll take any skill out of EQ. Enchanters can now set up macros to
> continually re-mesmerize things since they know exactly how long something
>
> will wear off. He mentioned that Verant was against macros from the
> beginning and is wondering what has changed to make them implement this.
> He's pretty much against this enhancement. I just gave him the, "Back in
> my
> day we actually had to push the buttons " tease and told him he doesn't
> have to use it if he doesn't want to.
>
> I look forward to using this to weave Hymn and Clarity during down times.
> I'll actually be able to take somewhat of a break, just repressing the hot
> key.
>
> ---Windleaf
>
>
> At 12:25 PM 9/28/00 -0600, Kimes, Dean W. wrote:
> >Yes that's true but what if you inserted a command before the one to turn
> >off the song that could only be executed to turn one off and would fail
> to
> >turn a song on? Like maybe...
> >
> >/Cast 1
> >/Pause 4
> >/Sit
> >/Cast 1
> >/Stand
> >/Cast 2
> >/Pause 4
> >/Sit
> >/Cast 2
> >/Stand
> >/Cast 3
> >/Pause 4
> >
> >Rinse and Repeat?
> >
> > Kit
> >
> >-----Original Message-----
> >From: John Tatsukawa [mailto:john@...]
> >Sent: Thursday, September 28, 2000 12:23 PM
> >To: eqbards@egroups.com
> >Subject: RE: [eqbards] Patch Message
> >
> >
> > >At 02:14 PM 9/28/00 -0400, Scott Malin wrote:
> > >What I'm wondering is what happens in the case of a missed note or a
> >fizzle?
> >
> >Macro has no intelligence, so I would assume it would keep following it's
> >commands step by step.
> >
> >At 12:03 PM 9/28/00 -0600, Kit wrote:
> > >Yikes! I'll bet that will be nerfed within minutes. Of course there
> will
> > >still be no way to deal with missed notes... or will there, hmmm.
> > >
> > > Kit
> >
> >Don't know why it would be nerfed. This enhancement allows a caster to
> >perform a number of funtions with one key, same as weaving.
> >
> >However, yes, missed notes would mess the timing up. I wonder if you
> could
> >then just press the "social" key again to interrupt the current macro or
> >whether you'd be stuck waiting for your it to end? Something to
> definitely
> >test.
> >
> >---Windleaf
> >
> >
> >
> > >Sounds like you might be able to set up some weaving via the social
> keys
> > >with this new "pause" command. It'll be fun to test!
> > >
> > >--------------------------------
> > >
> > >*Pauses in Socials*
> > >
> > >You may now enter pauses in social batches with the /pause command.
> /pause
> > >takes an argument from 1 to 600, with the value being equal to the
> number
> > >of tenths of seconds (i.e. /pause 100 will yield a 10 second pause).
> > >
> > >For example, a social consisting of:
> > >
> > >/sit off
> > >/cast 1
> > >/pause 100
> > >/sit on
> > >
> > >...would cause you to stand up, cast the spell in slot 1, wait 10
> seconds
> > >after you've STARTED casting the spell, and sit down.
> > >
> > >Furthermore, you can also use the /pause command on the same line as
> > >another social by separating the commands with a comma. Even though the
> > >pause command is specified first, it is executed AFTER the command on
> the
> > >same line.
> > >
> > >For example:
> > >
> > >/sit off
> > >/pause 100,/cast 1
> > >/sit on
> > >
> > >...would have the same effect as the example above. It is important to
> > >note that the comma can only be used to separate a /pause command from
> > >another, and MUST be specified first on the line.
> > >
> > >
> > >
> > >Please send submissions for the eqbards newsletter to
> lol@...
> > >with the subject submissions.
> > >
> > >
> > >Please send submissions for the eqbards newsletter to
> lol@...
> > >with the subject submissions.
> >
> >
> >
> >Please send submissions for the eqbards newsletter to lol@...
> >with the subject submissions.
> >
> >
> >Please send submissions for the eqbards newsletter to lol@...
> >with the subject submissions.
>
>
>
> Please send submissions for the eqbards newsletter to lol@...
> with the subject submissions.
>