Found possible reason mobs fail to spawn sometimes

[moydock]

I had a feeling 'Cond_Value' in the spawn2 table was the culprit so, every time I found a mob that wasn't up, and should be, i've been checking this value. And every time the value is always set to 1. And there are many more mobs with 0's than 1's so it's very unlikely it's a coincidence.

The way a mob gets a 1 in this value is when you #spawn a mob, and then save it to the db with #npcspawn create. If you spawn it with #dbspawn2 then it fills the cond_value as 0. These npc's never seem to have problems.

Hope this helps, there could be other reasons it's happening too but I'm fairly certain this is a big one.

[gernblan]

See my other post about this.

I figured it out... now how to SOLVE it?

[moydock]

Can't seem to find your other post.. Can you link it?

[gernblan]

It's currently one below this one.

The next topic down ;)

[moydock]

I think that's a different problem. I've never used those commands. I only use #spawn and #dbspawn2.

[moydock]

Oh yeah, i don't use #npcspawn add either, i use #npcspawn create.

[LostZaphod]

Line 856 of npc.cpp has this insert statement.

INSERT INTO spawn2 (zone, x, y, z, respawntime, heading, spawngroupID) values()

Note 'cond_value' is not in the statement, When executed the SQL server uses the column default value. The default value is set to 1.

Ways to fix are, change the default value to 0 or add the column and value to the INSERT INTO statement.