Hit Points script

[durnurd]

Well, it would help if we knew what line 39 was.  Try posting the updated script, at least up to line 39

[gwal]

This is a bit off-topic, but anyone who want to try a more 'simple' method of hitpoints should look at the script from the Dark Elf game. It uses UserData, and a variable for each enemy's hitpoints.

[cbass]

I very much agree that Userdata is the best and easiest place to store enemy hp.

If you want a more fancy display for their hp bar, like above their heads, or a display of the most recent enemy that has attacked you or has been attacked, i know this is very possible in the sgdk environment.

Actually, i implemented the latter in this very rough and unfinished project here:
LINK
Run the .EXE in the code folder.
the script is not in normal script, it is a compiled com object, but the source is included.  it probably won't be very helpful if you don't have VB 6.0, but the .bas files where the source is located are readable with a text editor. 


If you want a fancy display like that you have to get a little more complicated.  You have to have a MaxHP and a currentHP for each monster.  You then have to edit inventory and how they are displayed every time the monster losses hp (usually in the onspritecollide event).


If you have any question, or are totally confused,  I can pull the correct snippets of code from the source and post them.  (providing I have sufficient motivation tomorrow )  Should be enough to get you started.

[bluemonkmn]

I haven't looked at the script, so I can't tell for sure if anyone has discovered this or not, but I should point out (in case you haven't) that you can store as much data as you want in the userdata property of a sprite.  You can store an array in the UserData property.  And If necessary, each element of the array can be another array, ad nauseum.

[durnurd]

I think you mean ad infinitum...

ad nauseam: So as to disgust or nauseate.

Unless you mean to create arrays so repetitively that it becomes nauseating.  I suppose they're similar.  And I also suppose it can't really go to infinite depth, due to a maximial limitation on machines imposed by their registers, memory, and hard drives.  Yeah, I'll stop trying.  Good enough.

[bluemonkmn]

Right, that's why I chose "ad nauseum" instead of "ad infinitum" because you can't go on forever, but you can go on until you get sick of it .  If "ad ridiculousum" were a real term, I might have used that instead.