Page 2 of 2
Re: A_WolfAttack
Posted: Mon Mar 07, 2011 3:23 am
by Gez
Enjay wrote:Would there be any way (or any need?) to expose those features so that they could be used in other attacks. ie, you get the realism of the Doom system hitting the first shootable target in the path, but also the nice effect of the "dodge" and the speed related inaccuracy (and the distance degradation) - or are they intrinsically linked to an attack that "rolls to hit" (which I suspect may be the case)?
They could be implemented in normal hitscans by simply increasing the maximum spread angle in such conditions.
Re: A_WolfAttack
Posted: Thu Mar 10, 2011 6:33 pm
by AFADoomer
In live testing, the damage levels seem to be significantly higher than in Wolf3D... Using something like:
Code: Select all
WBOS FG 5 BRIGHT A_WolfAttack("boss/attack", 0.666, 64, 64, 2, 4, 160.0)
as one of the HansGrosse attacks seems to damage at 2-3 times the rate of Wolf3D when at range (as observed in Dosbox). Though this could be an effect of Wolf's weighted "random" number table (that or something I did to compensate when using hitscans is now causing problems).
Re: A_WolfAttack
Posted: Fri Mar 11, 2011 7:45 am
by Gez
Interesting. I looked into the TakeDamage() function to see if there were an explanation, but it only shows that damage are quartered in the baby skill ("Can I play, Daddy?"), no other adjustments.
Re: A_WolfAttack
Posted: Sun Apr 17, 2011 8:19 am
by Gez
New version of the patch. The first argument is now for the flags (just put 0 to get default behavior). I've added NORANDOM and USEPUFF. Also made it spawn blood, puff, and blood decals. Any comment, problem or niggle?
Re: A_WolfAttack
Posted: Sun Apr 17, 2011 12:22 pm
by NeuralStunner
Gez wrote:Any comment, problem or niggle?
My comment: FBF_FALLOFF.
Re: A_WolfAttack
Posted: Sun Apr 17, 2011 1:18 pm
by Gez
Out of scope of this thing. I'm not going to put either/or codepaths in standard hitscan functions to have them do the scan either with a trace or with a range check + sight check.
Re: A_WolfAttack
Posted: Sun Apr 17, 2011 1:19 pm
by NeuralStunner
Gez wrote:Out of scope of this thing. I'm not going to put either/or codepaths in standard hitscan functions to have them do the scan either with a trace or with a range check + sight check.
Mainly I was referring to an A_FireBullets flag to reduce damage toward the given maximum range, similarly to A_Explode.
Re: A_WolfAttack
Posted: Wed May 11, 2011 1:36 pm
by Major Cooke
Right then, so, could we get a page up on the wiki please? I would do it but since there was additional changes I have that feeling I might miss something, and then people will start putting up bug reports and what not.