|
charneus Wizard
Joined: 19 Jun 2005 Posts: 1876 Location: California
|
Posted: Thu Apr 08, 2010 1:25 pm
[3.16b]BUG with %pref evaluating on command lines and in output windows |
Pretty odd bug that a fellow MUDder and I came across. I was telling him the command-line way to turn on time stamps, and typed:
`tech Do #EXECWIN "Chat" {#CALL %pref("ShowTime",1)}
which actually evaluated on HIS end and turned on his time stamps. It didn't turn on mine, but when I typed (next):
tech #CALL %pref("ShowTime",1)
it evaluated on MY end and turned on the time stamps.
This can be pretty serious since we are able to mess around with someone else's preferences until this gets fixed.
Charneus |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Fri Apr 09, 2010 6:28 am |
This actually isn't as serious as it first appeared.
Quote: |
tech #CALL %pref("ShowTime",1)
it evaluated on MY end and turned on the time stamps. |
That is actually normal and expected. Variables and functions are parsed and expanded on the command line. You don't even need the #CALL. Just doing
Code: |
tech %pref("ShowTime",1) |
will do it to.
What I cannot reproduce is any way to cause this to happen on a remote user machine. My guess is that your friend had some sort of bad script that is executing text received via chat somehow. Probably with %eval or #EXEC which are pretty common in scripts imported from zMUD.
If you find a way to reproduce it, send me the exact text being received from the MUD that causes it to happen in a blank session. |
|
|
|
Private Adept
Joined: 10 Jan 2002 Posts: 264 Location: USA
|
Posted: Sat Apr 10, 2010 12:09 pm |
it was me on the remote machine, the chat window only contains 2 trigs, both blank subs:
^?chan ch=%w? --> #SUB {}
^?tell? --> SUB {}
did not happen in this window, timestamps were turned on in my main window though... as to what caused it, no clue,
I had just did the import wizard from zmud, and had only sorted out a few things... Later when i at least got the compatibility report empty (like 1000 items),
we could not reproduce this again...
the one bit of wierdness that i repaired that coulda had something todo with it was my weapon aliases... 40,60,80,100,etc,etc... those were causing %eval issues
past that, the only other things "fixed" were
"%1" to %1
~@@theme_color_mud o to %char(64)@theme_color_mud
changing ~[ to %char(91)
#IF {1=1} to #IF (1=1) ... heh, those hadn't changed since 3.62 when i came from tintin
stripping ~ from ~<mxpstuff
and changing all my scripts that did like #ADDITEM blah {(1|2|3)} cause cmud now quotes em
that was 99% of what cmud balked at
the exact line from the mud was...
{chan ch=tech}(Tech) Charneus: Do #EXECWIN "Chat" {#CALL %pref("ShowTime",1)} |
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|