Druid Monster Mover 1.02 Crash *with FHI*

I know this probably can't be helped, but I would like to point out that this version of the monster mover is incompatible with FragHouse Invasion 4.1. When I have tried to run the server, it crashes without any warning or error displayed - instantly.

If it could be helped with a simple OR statement or something similar, would you mind making a fix, Dru?

1 question, why you want to run monster mover with fraghouse ?

the maps are overaly so small you barely lose monsters anyway..

That's only on some maps, buddy... there's others that are massive and are very time consuming to look in every possible place. Plus, for some reason (either a bug in FHI or a bug between FHI and SMP), sometimes the monsters spawn in places not possible to travel (ex: under the map, behind a wall, in the little fake skybox thingy, etc) and waiting for the wave to time out is exhausting... Do you know how much energy I have to use just sitting in the same place, observing the scenery?! Well, not much - or any at all - but it's way too boring to have any fun -_-

I'm just requesting it be made compatible if it's an easy check to edit (like if ( GameType == Invasion || GameType == FHI)). If it's any harder than that, I don't want Druid to waste his time on it.

The very idea of trying to run this with the number of monsters that FHI spawns is just plain insane.

You *might* be able to get it to work by setting the defaults for all the settings up to much higher numbers, but then the monster mover will be far less useful.

Heh, thanks for changing the title - I guess I left that part out

But the fact of the matter is, on my server, I have all the max monster variables set to 1 - albeit that 16 monsters still spawn, but that might change very soon to follow the exact number I specify.

The main reason I could use this mutator with my server is that after we (players) kill off every monster we can find, the wave still doesn't end - because some monster is still alive. Even if the checks for monsters' ranges/locations are once every minute, it still beats waiting for the wave to time out - which for some odd reason seems to not happen in some instances.

<shrug> If someone wants to submit a patch, I'll consider adding it.

Kiros72 wrote:

...Plus, for some reason (either a bug in FHI or a bug between FHI and SMP), sometimes the monsters spawn in places not possible to travel (ex: under the map, behind a wall, in the little fake skybox thingy, etc) ...

I can't help you with the crashing or the use of FHI, but this bug where monsters spawn out of map is known to happen quite frequently when you use satore and specify monsters that are large in scale. Anything bigger than a titan stands a very good chance of spawning under the floor mesh if the floor is not at the bottom of the world box.

You can replicate this very easily by setting up a quick invasion on DM-Antalus with a few monsters that are about 6 or 8 times the normal size.
Depending on the overall size of the monster, they will either spawn under the hills and be invisible, or you might only see the top half of the monster. satore tried to fix this at one point but it never got a 100% fix.

v0rTeX wrote:

Kiros72 wrote:

...Plus, for some reason (either a bug in FHI or a bug between FHI and SMP), sometimes the monsters spawn in places not possible to travel (ex: under the map, behind a wall, in the little fake skybox thingy, etc) ...

I can't help you with the crashing or the use of FHI, but this bug where monsters spawn out of map is known to happen quite frequently when you use satore and specify monsters that are large in scale. Anything bigger than a titan stands a very good chance of spawning under the floor mesh if the floor is not at the bottom of the world box.

You can replicate this very easily by setting up a quick invasion on DM-Antalus with a few monsters that are about 6 or 8 times the normal size.
Depending on the overall size of the monster, they will either spawn under the hills and be invisible, or you might only see the top half of the monster. satore tried to fix this at one point but it never got a 100% fix.

Oh yes, trust me, I've figured that out long ago, however, I'm not using the monster config for anything at the moment - I just keep the mutator running so when I do use it to specify monsters, I won't need to do much more than I need to. Anyway, I'm not talking about that occasional spawning under ground bit with x5 Jaghra (

), I mean a monster sometimes spawns in a place where their not even visible on the radar - my guess would be the skybox thing for some odd reason...

Of course, blame it on the skyboxes... But yes, it is very possible that a skybox is screwing it up. Heck, skyboxes mess up scriptedtextures, of all things.