Previous Thread
Expand All
Collapse All
Ignore Author
Reply
Soooo.. I hope I'm in the right place. is ZMUD what we call our programming language? I'm a total novice on programming. I made a script that fails to identify the match variable, and I fixed it. So my question is... why did splitting to a new section this fix my script?
OLD not working script
start:
pause 2
put listen to %t
pause 2
put clean my cornet
pause 4
put play %p
match expcheck You finish playing (right here if failed to MATCH this hwne I'd finish playing. I'd just sit there forever)
match juggle idle
matchwait
NEW working script
start:
pause 2
put listen to %t
pause 2
put clean my cornet
pause 4
goto play
play:
put play %p
match expcheck You finish playing
match juggle idle
matchwait
My guess: The pauses likely causes it to not parse properly. By separating it out, the pauses are no longer associated with the match table.
Both scripts would likely work in Genie, but ZMud may not be as capable.
Elanthipedia - https://elanthipedia.play.net/mediawiki/index.php/Main_Page
Epedia Admins - https://elanthipedia.play.net/mediawiki/index.php/Elanthipedia:Administrators
Both scripts would likely work in Genie, but ZMud may not be as capable.
Elanthipedia - https://elanthipedia.play.net/mediawiki/index.php/Main_Page
Epedia Admins - https://elanthipedia.play.net/mediawiki/index.php/Elanthipedia:Administrators
A helpful suggestion since you are new to writing scripts. Always put the action you are doing after the match table. It can cause hang-ups sometimes with the action executing before table is fully loaded, and it won't catch the match. So instead of this...
play:
put play %p
match expcheck You finish playing
match juggle idle
matchwait
Do this...
play:
match expcheck You finish playing
match juggle idle
put play %p
matchwait
play:
put play %p
match expcheck You finish playing
match juggle idle
matchwait
Do this...
play:
match expcheck You finish playing
match juggle idle
put play %p
matchwait
