Post 2002-06-22 ideas...

A forum for the general posts relating to MacroQuest. *DEPRECATED: This forum is no longer in public use, but remains here for your reading pleasure. Enjoy

Moderator: MacroQuest Developers

cyberglitch
a lesser mummy
a lesser mummy
Posts: 42
Joined: Wed Jun 26, 2002 4:40 pm

Post by cyberglitch » Fri Jun 28, 2002 12:11 pm

ok how about something like

/if tell=/who all GM /EVADE

also

/if tell $play tell.wav

When we get a tell see if they are a GM and maybe /unload /camp or something simular.

or

If we get a tell play a certain wav file.

User avatar
L124RD
Site Admin
Site Admin
Posts: 1343
Joined: Fri Jun 14, 2002 12:15 am
Location: Cyberspace
Contact:

Post by L124RD » Sat Jun 29, 2002 1:35 am

Salutations,
no / commands for if statements...
(inside event chat)

Code: Select all

/if $p0==tell /if $who($p1,gm)==TRUE /call runfromgm
That doesn't work, but its more along the lines... for the playing of a wav... (inside event_chat)

Code: Select all

/if $p0=tell /play tell.wav
that one doesn't work either but... its more along the lines of the current syntax as well.
Last edited by L124RD on Sat Jun 29, 2002 10:51 pm, edited 1 time in total.

Gatts
orc pawn
orc pawn
Posts: 10
Joined: Sat Jun 29, 2002 10:01 am

Post by Gatts » Sat Jun 29, 2002 10:15 pm

Yet another idea.

I was looking over your source code (Hoping I could add this idea myself) and It looks pretty easy to do.

Add a way for players to add there own event triggers. Frankly there are a TON of things that a player may want to look for and run a macro on, so it makes sense to add a way to do it. Otherwise your going to end up with 100+ EVENT statements if you want to make everyone happy.

A couple of ideas:

/addevent [Trigger_Text] [Subroutine to Call]

Looks like you might need to be declare at the top, the way you parse the file, or you can scan the whole macro first and get the pBlock for the matching text. (I may be reading this right) Then just keep a list of the added events to check through on CChatHook and add to the event queue.

The other idea is just add some sort of EVENT_GENERIC that just graps everything and you can parse it like you do EVENT_CHAT. The problem with this, (I'm guessing) is that you will generate a TON of events and its probably pretty easy to overflow. So you may have to edit out certain spammy lines. All attacks, Bard songs, (but not their interrupts and missed notes please:), hungry msgs, etc.

Anyway more food for thought. Thanks for a great program

Gatts