More Runtime Errors. - Axe Software Forums

  Axe Software Forums
  Quest Developer Forum
  More Runtime Errors.

Author Topic:   More Runtime Errors.

I think Im Back posted 02-04-2003 11:13 GMT
So I'm nearly complete on a very above par demo for a battle system, when I get to what I knew was going to be tricky... Roundtimes... So, my idea was to give players a property called rt which unless you have roundtime it equals zero. Then, I have predefined timers for a large scale of intervals all made up, with each's action to turn itself off and reset the rt property on the player to 0, thus, after the timer runs out you can once again move freely.
I was doing this by setting the rt property after the appropriate amount of roundtime has been calculated with...
property <player%userid%; rt=$timerstate(player%userid%-%rt)$> which corresponds perfectly to the timers already made, but as soon as it attempts to change the property, QuestNet gives me a
Run-Time Error '5':
Invalid procedure call or argument
If anyone has a bit more information on this, it'd be appreciated.

Alex posted 02-04-2003 15:19 GMT
I'm not sure what you're supposed to achieve with that line. Firstly it looks like you're missing a "%" sign - these surround numeric variables so you should have an even number of them, and you have three. In any case you don't read the player's rt property using %rt%, as that reads a numeric variable called rt. I think you need to use #player%userid%:rt# instead, though I've not tested whether that will work with the "%userid%" in there - use the $objectproperty$ function instead if that form doesn't work.
Thirdly I think the closing bracket and $ sign for the timerstate function should be BEFORE you start trying to subtract anything from it, if I have understood correctly what you are trying to do.
I think Im Back posted 02-04-2003 20:37 GMT
Yeah, I was half asleep when I posted that, so I made syntax errors when I typed it in here. I suppose I really should stop staying up for days on end writing code because it really ruins my ability to error-check the code. I should have just copied and pasted the code, but either way, after a little messing around I got things working.
Thanks for the quick reply though.

Author	Topic: More Runtime Errors.
I think Im Back	posted 02-04-2003 11:13 GMT So I'm nearly complete on a very above par demo for a battle system, when I get to what I knew was going to be tricky... Roundtimes... So, my idea was to give players a property called rt which unless you have roundtime it equals zero. Then, I have predefined timers for a large scale of intervals all made up, with each's action to turn itself off and reset the rt property on the player to 0, thus, after the timer runs out you can once again move freely. I was doing this by setting the rt property after the appropriate amount of roundtime has been calculated with... property <player%userid%; rt=$timerstate(player%userid%-%rt)$> which corresponds perfectly to the timers already made, but as soon as it attempts to change the property, QuestNet gives me a Run-Time Error '5': Invalid procedure call or argument If anyone has a bit more information on this, it'd be appreciated.
Alex	posted 02-04-2003 15:19 GMT I'm not sure what you're supposed to achieve with that line. Firstly it looks like you're missing a "%" sign - these surround numeric variables so you should have an even number of them, and you have three. In any case you don't read the player's rt property using %rt%, as that reads a numeric variable called rt. I think you need to use #player%userid%:rt# instead, though I've not tested whether that will work with the "%userid%" in there - use the $objectproperty$ function instead if that form doesn't work. Thirdly I think the closing bracket and $ sign for the timerstate function should be BEFORE you start trying to subtract anything from it, if I have understood correctly what you are trying to do.
I think Im Back	posted 02-04-2003 20:37 GMT Yeah, I was half asleep when I posted that, so I made syntax errors when I typed it in here. I suppose I really should stop staying up for days on end writing code because it really ruins my ability to error-check the code. I should have just copied and pasted the code, but either way, after a little messing around I got things working. Thanks for the quick reply though.