Welcome to the ZDoom Forums!

Well if not this, could we at least have an XRaise state?

this would be a very useful thing to use :D

you could make so much awesome monsters, heh, @ghastly: the vagary could throw corpses at you this way :D

I suggested something similar to this a while ago (an extension to A_VileChase I believe), but this way sounds better.

The main reason I suggested it though was to have normal raise-able monsters and to also have a staff that makes corpses explode.

Raise.XDeath.Eat, or something like that (most likely won't work)? That's a problem that'd have to be worked through before this would be implemented, obviously.

My plan for a Glutton creature that eats the corpses of enemies to gain strength is the main reason I suggested this feature. ;) Here's how I'd do it with my 'HealType' method:
[spoiler][code]actor Glutton : Fatso 32021
{
HealType "Eat"
States
{
Heal:
GLUT GHIGHIGHI 6
Goto See
}
}

actor EatableDemon : Demon replaces Demon
{
States
{
Raise.Eat:
//insert gross gibbing sequence here
Stop
}
}
[/code][/spoiler]

As for resurrecting monsters who have died in certain ways due to different damage types, this is an excellent idea. Here's how I'd simulate that in DECORATE:
[spoiler][code]actor NewImp : DoomImp replaces DoomImp
{
States
{
Raise.XDeath: //this is a DamageType in its own right, correct?
TROO TSRQPONJI 4
Goto See
Raise.Fire:
BURN VUTSRQPONMLKJIHGFEDCBA 3 //using Strife's burn death as an example
Goto See
Raise.Disintegrate:
// Uh, is there any point to this state, since the Disintegration death completely vaporizes the victim anyway?
Stop //Heh.
}
}[/code][/spoiler]

There's bound to be a problem with this method that will arise sooner or later when a modder wishes to do something extremely innovative with this system. Looking at my two examples here, which are quite different from each other, syntax-wise, I can foresee problems cropping up here and there.

Yes, just have a heal damage state dedicated to it.

Well, actually no. This would not work easily because you'd have no way to get it to eat one and spawn another one, unless you were somehow able to pull what type the ressurection target type is.

[quote="Ghastly_dragon"]Would raise states based on what monster raised it be possible, too? The Gremlins from the Quake 1 expansion pack come to mind (where they eat a corpse and spawn another monster).[/quote]

Yes, that's exactly what I had in mind! Jimmy's Glutton concept could become very real and functional. :D

Would raise states based on what monster raised it be possible, too? The Gremlins from the Quake 1 expansion pack come to mind (where they eat a corpse and spawn another monster).

This is a brilliant idea. In fact, I was thinking of uses for something like this the other day, though I didn't know it had been pitched as a suggestion. This would open a multitude of possibilities, and would make an excellent addition!

More generally seen in Doom 2 when an Archvile comes along and puts the pieces of a gibbed zombie or imp back together.

Yes, since I tend to run into the problem of monsters or marines burning on fire, and when a vile revives them, they transform from a normal corpse

So basically that would allow for different vile types that can only raise certain enemies, while at the same time allowing for different raised states based on how the enemy died (so that an enemy that was burned to ashes will have an animation showing them being reconstructed from the ashes, for example)? That sounds like a very cool idea.

Why not the raise states being based off of what damage dealt the final blow. For instance, why not have Raise.Disintegrate be for when they are revived. IMO this is MUCH more flexible and for a simple reason: You could provide a raise state label in A_VileChase (defaulting to "Raise" if not defined), much like how A_Chase has parameters for what states to use for melee and ranged attacks, and then, for example, if said monster died of ice, you could provide a Foo.Freeze state in the raised monster, where Foo would be the parameter for 'state' in A_VileChase. If Foo.Freeze was not provided, it would just use Foo. If Foo is not provided, said monster cannot be revived by said 'raise' type. This could be used to create things such as vile bossfights, where there would be viles and a big bad vile boss that can revive normal viles, but the normal viles cannot revive eachother.

Augh that statement took some time to write and polish <_<

Bump. I [i]thought[/i] this feature suggestion had already been pitched. :wink:

So, any news on how hard it would be to get this in? It's essentially DamageTypes for Heal and Raise states instead of projectiles and Pain and Death states.

[quote="Graf Zahl"]The original suggestion sounds interesting but the specialized Heal state is not really necessary, only the specialized Raise state.[/quote]Actually, yes, if I could come up with a better way to implement this, I would.