A_WolfAttack

Moderator: GZDoom Developers

Gez
 
 
Posts: 17946
Joined: Fri Jul 06, 2007 3:22 pm

Re: A_WolfAttack

Post 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.
User avatar
AFADoomer
Posts: 1344
Joined: Tue Jul 15, 2003 4:18 pm
Contact:

Re: A_WolfAttack

Post 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).
Gez
 
 
Posts: 17946
Joined: Fri Jul 06, 2007 3:22 pm

Re: A_WolfAttack

Post 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.
Gez
 
 
Posts: 17946
Joined: Fri Jul 06, 2007 3:22 pm

Re: A_WolfAttack

Post 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?
Attachments
WolfAttack.zip
(1.94 KiB) Downloaded 65 times
User avatar
NeuralStunner
 
 
Posts: 12328
Joined: Tue Jul 21, 2009 12:04 pm
Preferred Pronouns: No Preference
Operating System Version (Optional): Windows 11
Graphics Processor: nVidia with Vulkan support
Location: capital N, capital S, no space
Contact:

Re: A_WolfAttack

Post by NeuralStunner »

Gez wrote:Any comment, problem or niggle?
My comment: FBF_FALLOFF. :P
Gez
 
 
Posts: 17946
Joined: Fri Jul 06, 2007 3:22 pm

Re: A_WolfAttack

Post 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.
User avatar
NeuralStunner
 
 
Posts: 12328
Joined: Tue Jul 21, 2009 12:04 pm
Preferred Pronouns: No Preference
Operating System Version (Optional): Windows 11
Graphics Processor: nVidia with Vulkan support
Location: capital N, capital S, no space
Contact:

Re: A_WolfAttack

Post 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.
User avatar
Major Cooke
Posts: 8215
Joined: Sun Jan 28, 2007 3:55 pm
Preferred Pronouns: He/Him
Operating System Version (Optional): Windows 10
Graphics Processor: nVidia with Vulkan support
Location: GZBoomer Town
Contact:

Re: A_WolfAttack

Post 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.
Post Reply

Return to “Closed Feature Suggestions [GZDoom]”