Extention to A_SkullAttack

[Ghastly]

A_SkullAttack[(int speed[, int damage[, str damagetype[, str state[, str attacksound[, int flags]]]]])]

Damage is damage-on-collision (randomized like the Lost Soul damage is, but allowing for custom formulae?), damagetype is obvious (defaults to whatever A_SkullAttack uses normally), state is the state it jumps to after it collides with something, and the only flag I can think of at the moment is allow-pain, allowing the calling monster to enter their pain state while charging (Lost souls, for example, can't enter their pain state until they stop).

Current ideas for flags:
-Allow pain
-No random damage
-Don't lose momentum when hit
-Don't adjust z momentum
-Charge-where-facing, not at target

[NeuralStunner]

I certainly like this! For any such function is good to add customization.

Damage is damage-on-collision (randomized like the Lost Soul damage is, but allowing for custom formulae?)

the only flag I can think of at the moment is allow-pain

Needs a NORANDOM.

[Graf Zahl]

Needs no randomness in the passed damage value.

[Ichor]

Can't damage be defined already, like it was a projectile?

[XutaWoo]

Yes, but that sucks up the damage property and is always randomized.

Also, how about a flag that makes it so that the monster's momentum can't be cancled out, outside of running into something?

[NeuralStunner]

Yes, but that sucks up the damage property and is always randomized.

What about using parentheses as for projectiles? I.E.

Code: Select all

Damage (20)

[Spleen]

It's also logical to add a flag for invulnerability, since Heretic's Minotaurs have that, I would think.

[Gez]

I think it'd be a better idea to use an actor flag for that, called INVUNLCHARGE. My reasoning is based on two points:
1. The MinotaurFriend would not need to have redefined states.
2. It'd be the same as in Eternity, and I like it when different ports propose a consistent implementation of the same feature.

Though you could as well have a flag in the function itself too if so you want.

[Snarboo]

I definitely approve of this. It would make for more interesting behavior for rushing monsters.

Quick semi-related question: what affect does A_SkullAttack have on a player when called?

[Caligari87]

Depending on the output of A_JumpIfTargetInLOS, it usually forces the playerpawn to enter it's default "OhShit" state, which then decides whether to strafedodge or fire, depending on the selected weapon.

[NeuralStunner]

It would make for more interesting behavior for rushing monsters.

This gets me to thinking, perhaps it could also use a flag to retain gravity. This way you wouldn't get randomly flying Demons, for instance.

[Ghastly]

This way you wouldn't get randomly flying Demons, for instance.

You don't, I don't think. I've used A_SkullAttack and ThrustThingZ to get leaping monsters, and they're affected by gravity.

[NeuralStunner]

Horrid luck on my part then, I tried it and they flew.

[Ghastly]

Well, they will leave the ground, if their target is higher than they are, but they're still gravity-affected.

[Amuscaria]

What about a flag that keeps the monster calling this action on the ground instead of flying up at monsters with a higher Z-pos? (unless there is already a way to do this).