12-15-2003, 07:25 PM
[Useless babbling about Diablos LBOD in this post]
[Edit #2] Actually, nevermind what I said in regards to anything Diablo. Setting it to 100 makes the skill never do any damage, and I'd forgotten I put InitSteps to 0. With it to 1 the skill is invisible untill it's red goeey, in which case it's over the 30 range (as specified in the range field) and eventhough there's the lightning sparkle sound, I take no damage.
I'll stick to non-complicated skills, thankyou.
------------------------------------------------------------
[Cut from original post]
Now the strange thing is Diablo's LBOD, I was unable to spawn him anywhere with help of levels.txt, so I had to run all the way to Chaos Santuary.
This skill (called diablight) has 0 in Activate, and 1 in InitSteps, so with my BH testing it should mean the graphic doesn't start directly from him, but the effect (damage) should < But as has been mentioned, there's a "safety range". I changed InitSteps to 0 anyhow.
When I summoned him finally . . . the graphic started from the center from him, and I took damage being just near. I don't feel like running all the way there and change a setting or two, so that's all the testing for now.
Of note is I could use Charge at this point too (over and over) vs Diablo, my character didn't move but I got the graphic/sound.
------------------------------------------------------------
Putting the "minimum range" field to 100 though produced that effect. It's not red fluffy anymore, and as you might see I could stand there taking no damage.
I still don't know enough about these things, but the NextDelay + InitSteps + Minimum Range could work together if it's specified such (in what's referred to as "funcs" which aren't explained anywhere).
[Edit] I suppose it's like (whatever) Ruvanal said. With 100 I had to run ~2 screens away before it started to do damage. That's also when it got that red squishy look.
[Edit #2] Actually, nevermind what I said in regards to anything Diablo. Setting it to 100 makes the skill never do any damage, and I'd forgotten I put InitSteps to 0. With it to 1 the skill is invisible untill it's red goeey, in which case it's over the 30 range (as specified in the range field) and eventhough there's the lightning sparkle sound, I take no damage.
I'll stick to non-complicated skills, thankyou.
------------------------------------------------------------
[Cut from original post]
Now the strange thing is Diablo's LBOD, I was unable to spawn him anywhere with help of levels.txt, so I had to run all the way to Chaos Santuary.
This skill (called diablight) has 0 in Activate, and 1 in InitSteps, so with my BH testing it should mean the graphic doesn't start directly from him, but the effect (damage) should < But as has been mentioned, there's a "safety range". I changed InitSteps to 0 anyhow.
When I summoned him finally . . . the graphic started from the center from him, and I took damage being just near. I don't feel like running all the way there and change a setting or two, so that's all the testing for now.
Of note is I could use Charge at this point too (over and over) vs Diablo, my character didn't move but I got the graphic/sound.
------------------------------------------------------------
Zath,Dec 15 2003, 01:19 AM Wrote:Didn't Ruvanal calculate the minimum range for diablight from that entry suspiciously named "minimum range" before? :lol:Putting 1 in rarity still didn't make him spawn. He did spawn once before, but I have no idea how that happened.
Putting the "minimum range" field to 100 though produced that effect. It's not red fluffy anymore, and as you might see I could stand there taking no damage.
I still don't know enough about these things, but the NextDelay + InitSteps + Minimum Range could work together if it's specified such (in what's referred to as "funcs" which aren't explained anywhere).
[Edit] I suppose it's like (whatever) Ruvanal said. With 100 I had to run ~2 screens away before it started to do damage. That's also when it got that red squishy look.