statue code from doe

[Madfox]

For some days now I'm trying to add the statue.qc from DOE to my own monster.
I'm not sure, there are two monsters knight and hellknight, that have this code.
So I tried to extrackt the code from the doe.qc, but it is tricky.

My own monster with a walk routine doesn't seem so hard and triggers like one.
With a fly monster I ain't lucky, added the same code but for some reason
"void() monster_pause" is rejeckted.

Isn't there a code that has a solution for Statues, I can't find a trace in the doe.qc.

[Spike]

I don't know what the problem would be... unless this is something basic like not prototyping things as needed (order matters, and if the order cannot be satisfied then you can always just prototype with eg: void() monster_pause; <- shove that above the function its referenced in and the actual version of the function that's defined later will update its value properly).

the monster gets enough .th_* functions to stop the thing from crashing, just no-ops that make the monster do nothing (and take no damage). It also gets a .use function that sets the .th_* stuff to their normal values, so that you can trigger it to wake it up. nothing that wouldn't work in vanilla.

[Dr. Shadowborg]

[Madfox]

I had no problems with another walking monster to turn it into a satatue.
(well, that is..,) I had problems with turning the grey skin off to natural.
I can target them the same way as the doe monsters.
So is the statue code only impemented in the entity code, or on other places too.

The flying monster is something that won't compare the action in qc some where.



Here is what I wanted to obtain.
Making use of a static entity of a flying monster in frame 127.
Then, as soon as the player tries to use it, it turns into a flying model of the original.
A kind of morphing state from an item to an entity statement.

Maybe a bit weird, but when I made the monster, I was planning to do so.

[Dr. Shadowborg]

[Madfox]

Ah! So it is the ai.qc I should look for first.
The proximity mine, sounds like doe.qc.
Thanks for the help. The code from the Serpent.
You can find it here
The Cabbagemouth.., hungry feeling.

[Dr. Shadowborg]

[Dr. Shadowborg]

Update:

Gonna need a few more days, some stuff in RL came up and I gotta build out the basic monster first before I can properly test the special features.

Examining the framegroups reveals that this is a rather interesting monster to work with. Initial .qc version will probably feel like a vanilla quake flying deathknight; Full potential will require some more work, and will result in a much more varied (and deadly) monster.

[Madfox]

Ah, so the cabbagemouth stays hungry!

Here is the code I have in game, it has no alteration in the othe qc.
That's probably how to make it smarter.
For now the code is smarter then me.



Take your time, I'm puzzling already longer for it, and just started coding.

[Dr. Shadowborg]

Update:

Monster code v1.0 is complete and working. Final debug now in progress, once it's done I'll stick the .qc file 'n stuff up for you. (probably be sometime tomorrow)

[Madfox]

Thanks shadowborg!

I tried with placing an mdl frame 146 static in game, and then teleport another serpent to the same place, while killtarget the static.
It only works with a teleport_dest above the original.
That way it doesn't look the same monster anymore.

Great you managed it with qc.

For now I'm trying to make the squad_serpent look like the original quaddamage.
It still doesn't look convincing enough, and how to make a static frame turn?
(flag~all serpent poses start turning)

[Dr. Shadowborg]

[Dr. Shadowborg]

[Madfox]

That's great, Shadowborough! I will try that out.
I am curious to see what will happen. I'm changing the skin to match the Quaddama.
It's still a mistery how to get the skin changed, something in the last death frame.

Thanks for your help, I'll check it out.
Succes with the Cabbagemouth!

[Dr. Shadowborg]