 |
hellokitty
Newbie
Joined: 25 Jun 2010
Posts: 8
|
 Posted: Thu Jul 29, 2010 2:46 pm
having trouble with CMUD's #ALL
|
I'm running on CMUD Pro 2.37, just switched over from ZMUD 7.21
now on CMUD, I'm running on two set of screens, and I do #ALL attackspell - it works fine with two chars firing out both of their attackspells in a fight.
BUT - when I add a mobname after the above commands, e.g. #ALL attackspell goblin (to start a fight and have all two use attackspell at the same time on the goblin), it doesn't work, the mud just echoes back "Attack who?" like the only command that got through to the mud was only #ALL attackspell. Anyone know a fix to this?
I could do it in ZMUD with :attackspell mobname though. Was wondering if CMUD had a different way of firing off two screen aliases on a target??
Thanks in advance,
hk.
 |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4715
Location: Pensacola, FL, USA
|
Posted: Thu Jul 29, 2010 4:54 pm
|
It might be because its not enclosed in brackets... though im not possitive, try
#ALL {attackspell goblin} |
|
_________________
Discord: Shalimarwildcat |
 |
|
|
hellokitty
Newbie
Joined: 25 Jun 2010
Posts: 8
|
Posted: Thu Jul 29, 2010 5:16 pm
|
| shalimar wrote: |
It might be because its not enclosed in brackets... though im not possitive, try
#ALL {attackspell goblin} |
shalimar, yeah that works. Now i'm attacking with the attackspell at the same time, but of course my mobname will not always be goblin though! Is there an easier way around this? So I can vary the mobname.
Thanks for the reply. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jul 29, 2010 5:25 pm
|
Btw, I meant to mention this in another recent thread about the #ALL command and the fact that the :command syntax was not available in CMUD. So I'll post it to this thread instead.
Using a "Prompt Command Trigger" you can emulate the old zMUD :command syntax. A Command Trigger (#ONINPUT) that has the "Trigger on Prompt" option selected will fire and parse the command line *before* CMUD attempts to parse the command line itself. So you can set up a command trigger like this:
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger type="Command Input" priority="10" regex="true" newline="false" prompt="true" copy="yes">
<pattern>^:([^:]+)$</pattern>
<value>#ALL {#SEND %1}
#NOINPUT</value>
</trigger>
</cmud> |
However, there does seem to be an odd issue with the #ALL command. I tried using "#ALL %1" and it failed to work. So I'll also add that to the bug list.
But this was still a useful trick to remind people that you really have full control over how the CMUD command line is parsed using Prompt Command triggers. |
|
|
|
|
ralgith
Sorcerer
Joined: 13 Jan 2006
Posts: 715
|
Posted: Thu Jul 29, 2010 5:45 pm
|
Thanks Zugg, I'm bookmarking this for future usage.
|
|
_________________
 CrossOver: Windows Compatibility on Mac and Linux CMUD Advocate |
|
|
|
hellokitty
Newbie
Joined: 25 Jun 2010
Posts: 8
|
Posted: Thu Jul 29, 2010 6:15 pm
|
| Zugg wrote: |
Btw, I meant to mention this in another recent thread about the #ALL command and the fact that the :command syntax was not available in CMUD. So I'll post it to this thread instead.
Using a "Prompt Command Trigger" you can emulate the old zMUD :command syntax. A Command Trigger (#ONINPUT) that has the "Trigger on Prompt" option selected will fire and parse the command line *before* CMUD attempts to parse the command line itself. So you can set up a command trigger like this:
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger type="Command Input" priority="10" regex="true" newline="false" prompt="true" copy="yes">
<pattern>^:([^:]+)$</pattern>
<value>#ALL {#SEND %1}
#NOINPUT</value>
</trigger>
</cmud> |
However, there does seem to be an odd issue with the #ALL command. I tried using "#ALL %1" and it failed to work. So I'll also add that to the bug list.
But this was still a useful trick to remind people that you really have full control over how the CMUD command line is parsed using Prompt Command triggers. |
Be prepare to laugh. Ready.
Where do I put this in? |
|
|
|
|
Taz
GURU
Joined: 28 Sep 2000
Posts: 1395
Location: United Kingdom
|
Posted: Thu Jul 29, 2010 6:18 pm
|
Go to the package editor and create a new trigger, then go to the XML tab and paste it in and hit save.
|
|
_________________
Taz :) |
|
|
|
hellokitty
Newbie
Joined: 25 Jun 2010
Posts: 8
|
Posted: Thu Jul 29, 2010 6:31 pm
|
I've tried it. The results are..
I have three chars, three screens open. Now with :say test, the two other screens said hi, but not the screen that I typed it in.
Any ideas? |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Jul 30, 2010 4:19 pm
|
That's similar to the bug I encountered, which is why I added it to the bug list. You might try replacing the #SEND command with #EXEC in the above script to see if that works any better. But there is definitely a bug using #ALL within a Command Prompt trigger. I hope to fix this in the next Beta version.
|
|
|
|
|
|
|
|
