Detecting a walking/flying monster via QC

[Seven]

[Spike]

the qc is a bit convoluted. and frankly looks buggy to me.
but...

after *monster_start_go
if (time > self.pausetime)
monster is meant to be walking (assuming its not dead, anyway).

before then, you'll need to check if it has a target, and that its target is a "path_corner" entity. The monster will only patrol/walk if it targets a path_corner. Other entities are ignored (as they are triggered on the monster's death).

[frag.machine]

[Seven]

Thank you very much frag.machine and Spike.

frag.machine, the part of your code that checks for player is *normaly* not necessary,
as i have to make the decision in the first second after map starts.
Monsters are *normaly* not placed around players spawnpoint, but who knows...
Some mappers like this kind of extra thrill

So .goalentity is my way to go/check.

Thank you again for your help.

[Spike]

either way, entity load ordering means you cannot check this reliably in the spawn function itself.

so walkmonster_start_go would be the place to put any code that depends upon patrolling. and that's where the existing code figures out if its meant to be patrolling anyway.

[Seven]

Hello,

I didnt want to start a new thread for my small question.

It always bothered me, which of these 2 lines have more randomness, or if the engine interprets them equal:
1.) foo = random() + random() + random() + random() + random();
2.) foo = 5 * random();

Both lines can create foo values between 0 .. 5
But isnt the second line less random ?
As it multiplies the same value by 5, while the 1st line adds 5 random values ?

Sorry for this stupid question, but I use a lot of randomness in my small mod and this question bothered me for quite some time.
I plan to create a random value between 0 .. 100, so I was thinking if foo = 100 * random(); would be sufficient * random* LOL.

Thank you for your ideas.

[Nahuel]

[Cobalt]

[frag.machine]

[Seven]

Thank you very much for your posts and explanations.