Potential conflict with Alex's Mobs Farseers?

[katubug]

Hi, I'm not sure whether this is an actual issue or if we're just unlucky, but I wanted to ask if there was any possibility that the combination of these two mods might be causing Farseers to not spawn.

Farseers are meant to spawn only at the very edges of the world (an item teleports you to 30 million blocks out), but so far none have been found by myself or my server mates. They do show as having a weight of 30 in basically all biomes, so they should be spawning. However, I'm wondering if their unusual spawn conditions might be conflicting somehow. Can you let me know whether this is possibly the case? Thank you!

[mactso]

Alex Mob has his own custom spawn configuration and his own custom "canSpawn" methods for some mobs.
In order to spawn, FarSeers would need to pass Alex config file conditions and the FarSeer's canSpawn method.

As a minecraft example, you can' set Sheep and Woves in desert but they are hardcoded to only spawn on grass blocks.
Other mobs only spawn on leaf blocks.

If farseers are hard coded to only spawn if they are 30,000,000 meters from spawn, then they won't spawn any closer.

Hope this helps!

P.S.

I have an idea how to address mobs like this. Basically I would add a "PsuedoMob" which you set the spawning conditions for. Then you also say PsuedoMob1 spawns farseers. So the PsuedoMob would spawn (say in forest at 3,000 meters) and it would immediately summon a Farseer in it's place and then despawn itself.

This would let you spawn any mob anywhere regardless of normal limitations. I'm turning it over in my head to figure out the best way to do it so it won't be soon.