Skulltag's (onoez) Reflection powerup type

[Ghastly]

Since Skulltag is open-source, could we backport the Reflection powerup type (returns a certain amount of damage taken to what damaged you)? If so, could we possibly use powerup.strength to determine how much damage you return (Powerup.Strength 0.5 to return 50% of the damage, for example)? I just tested it, and it does work on monsters, not just other players.

An optional "it would be great to have" thing, the ability to set an obituary (But yeah, probably too much trouble)?

[Apothem]

I just tested it, and it does work on monsters, not just other players.

Strange, I remember my first encounters with this pickup were in MP. It was being used in an actual SkullTag match too!

[Gez]

"not just other players" != "not on other players"

[NeuralStunner]

This would be a great thing to have, though I would consider whether it would be better as a special mode for PowerProtection. (Removed damage being returned to the attacker.) This way, one could reflect only the DamageTypes that the powerup covers.

[Ghastly]

This would be a great thing to have, though I would consider whether it would be better as a special mode for PowerProtection. (Removed damage being returned to the attacker.) This way, one could reflect only the DamageTypes that the powerup covers.

As long as Powerup.Strength could be used to define how much you want to reflect, that'd be awesome.

[Ryan Cordell]

Well, CF_REFLECTION as a flag is unused in the ZDoom source, so I'll see to backporting it from Zandronum somehow. I'll probably go with the OP suggestion though, to avoid mucking with PowerProtection.

[Blox]

It might be an idea to add in Damagetype properties to it that would affect the final reflected value. (So Powerup.Strength * DamageType)

[Ryan Cordell]

Saw the final post a bit late, but whatever. Deciding to get off my lazy arse, I'm putting up the patch for PowerReflect that's been stagnating in ToB for far too long.

The code is, for all intents and purposes, horrible like nobody's business and most likely doesn't reflect more than one damagefactor.. but I'll let other people test that out for me, see if it works.

[Graf Zahl]

Added, sort-of. The implementation was shit and wasted a lot of potential. It makes far more sense to actually use the damage factors as intended and read them in P_DamageMobj instead of caching just one value and using that for everything.