Reply to Re: A couple of questions
If you don't have an account, just leave the password field blank.
All of that is possible. I can't believe I had forgotten to do some of these things 
(or maybe it was intentional at the time?)
1) Make a global var for the summon's life. Set the variable to = summons current life in his hit procedure. If that doesn't work, you could always spawn a script with a loop that always makes the summon's life variable = to the summon's life. In summoned.c, set his sp_hitpoints() to his life variable. Remember to reset the summon life variable in the spell script.
2) You could make a timer by spawning a script and attaching it to 1000. Declare the timer value and make a loop with wait commands and increments the &timer value by +1 for each second. When your timer has reached a certain point, use hurt() to kill off the summon.
3) Just make the whole hit procedure (excluding the change to the summon hp variable if you did that here) an if statement that determines if Dink hit the summon. I think you can use &missle_source for this.
(or maybe it was intentional at the time?)1) Make a global var for the summon's life. Set the variable to = summons current life in his hit procedure. If that doesn't work, you could always spawn a script with a loop that always makes the summon's life variable = to the summon's life. In summoned.c, set his sp_hitpoints() to his life variable. Remember to reset the summon life variable in the spell script.
2) You could make a timer by spawning a script and attaching it to 1000. Declare the timer value and make a loop with wait commands and increments the &timer value by +1 for each second. When your timer has reached a certain point, use hurt() to kill off the summon.
3) Just make the whole hit procedure (excluding the change to the summon hp variable if you did that here) an if statement that determines if Dink hit the summon. I think you can use &missle_source for this.
