 |
Ceres
Wanderer
Joined: 25 May 2006
Posts: 88
|
 Posted: Wed Jul 16, 2008 8:24 am
CMUD [2.30] #ONINPUT
|
I have been absent from playing Muds for some time and am in the process of converting my old zMud scripts to CMUD. It seems that the #ONINPUT triggers now trigger on commands sent from scripts whereas with zMud they didn't.
Is there any way to prevent emulate the behaviour of zMud and prevent #ONINPUT from processing script created input? |
|
|
|
|
Ceres
Wanderer
Joined: 25 May 2006
Posts: 88
|
Posted: Wed Jul 16, 2008 8:35 am
|
I have resolved this issue - the problem was that I had puut the #ONINPUT trigger within a Global module - moving the trigger to the main window tree has resolved the issue. I am not sure whether the behaviour still needs to be addressed if the #ONINPUT trigger exists within a Global module which cause the undesirable behaviour.
|
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Wed Jul 16, 2008 9:50 am
|
#SENDRAW
|
|
|
|
|
|
|
|
