 |
Caled
Sorcerer
Joined: 21 Oct 2000
Posts: 821
Location: Australia
|
 Posted: Fri Mar 13, 2009 11:29 pm
[3.03-3.05] Change or bugfix to #send and #sendraw?
|
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger type="Command Input" priority="16700" copy="yes">
<pattern>^cease (*)$</pattern>
<value>#IF (@attuning) {atto;#SENDRAW {cease %1}} {#SENDRAW {cease %1}}</value>
</trigger>
</cmud>
The above script, I used for a long time, with #send.
After installing 3.05, it caused a loop, which I fixed by using sendraw instead. Having said that, I'm not sure when I last used the script - might have been a few weeks ago now.
Looking at it, it makes sense to use #sendraw (I don't recall why I didn't when I first wrote the script, other than perhaps being new to the two commands and making a mistake.) I'm only posting to make sure the change is not a bug. |
|
_________________
Athlon 64 3200+
Win XP Pro x64 |
 |
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Sat Mar 14, 2009 8:00 am
|
That is the correct behavior. If you read the #SEND documentation you'll see
| Quote: |
| The text is sent just as if you typed it, so it is echoed to the screen and available for #ONINPUT triggers. |
. It is because of this that #SENDRAW was introduced.
|
|
_________________
Asati di tempari! |
|
|
|
Caled
Sorcerer
Joined: 21 Oct 2000
Posts: 821
Location: Australia
|
Posted: Sun Mar 15, 2009 5:27 am
|
Yeah I spotted that when I fixed the script, it just seemed odd to me that it worked right up until just recently.
|
|
_________________
Athlon 64 3200+
Win XP Pro x64 |
|
|
|
|
|
|
