Axe Software Forums
  Quest Developer Forum
  Experiencing problems with the WAIT function


Author Topic:   Experiencing problems with the WAIT function
Tyrant posted 07-07-2001 20:09 GMT     
It works when I use it in other places, but it doesn't seem to work when I use it in my current situation. Here's a STATS procedure that I coded. When the player types STATS, he can view all his stats:

define procedure <statsproc>
setstring <weapon;Sword>
msg <|c>
msg <|b|s20|clSTATS|cb|s00|xb>
msg <|n>
msg <|n|iYour Name|xi |b#playername#|xb>
msg <|n|s10|bEXP|xb |iExperience Points|xi - |b~exp~|xb>
msg <|bEXPlv|xb |iExperience Level|xi - |b~explevel~|xb|s00>
msg <|n|bSTR|xb |iStrength|xi - |b~yourstrength~|xb>
msg <|bDEF|xb |iDefense Vitality|xi - |b~yourdefense~|xb>
msg <|n|bGP|xb |iMoney Currency|xi - |b~gp~|xb>
msg <|bSTATUS|xb |iStatus Abnormalties|xi - |b|xn>
if has <yourstatus; =1> then msg <Poison!|xb> else msg <None|xb>
msg <|n|iCurrent Weapon Equipped|xi - |b#weapon#|xb>
msg <|n|b|crPress Any Key|cb|xb|w>
msg <|c>
exec <look>

end define


My problem comes with the "Press Any Key" line. When I take out the WAIT function, the procedure works fine, but it doesn't work when the function is in. I want it in so the player can press any key after viewing his stats, then he is returned to his current room. What's wrong?

Tyrant posted 07-07-2001 20:11 GMT          
By the way, the SETSTRING function in that procedure is only there temporarily just so it fills in the WEAPON string. In the final game, the WEAPON string will be whatever weapon you currently have equipped.
Alex posted 09-07-2001 12:32 GMT          
I can't see anything wrong with that code, but I'll check it when I get my computer back.