NPCSPAWN command ..broken?

[sonicintuition]

Something else I noticed which kind of falls into this category - Sometimes zones don't pop all the mobs that are in the database - whether using the npcspawn command or not. I start my server, log in, go to my zone, and a few of the NPC's aren't even there, but they show up when I repop the zone. Sometimes I have to repop 2 or 3 times before all my npc's show up.

Sonic

[John Adams]

I'm sure you've checked `spawnentry`s for that zone, the "chance" factor? 100 is what it needs to be for a 100% spawn chance. The worst thing I've seen with spawning is the mobs/pets that appear at the safe coords, but I think they are now warping back to where they belong after a bit. Odd.

[sonicintuition]

Yes, I did check that - 100% chance on everything. It seems that every time I #repop, an NPC is missing. I'll #repop again, and he/she will be back, but then a different NPC is missing. And so the cycle repeats, over and over ..while I bash my head against the keyboard. Ugh!!

[John Adams]

You are not nuts, sonic. I too saw this happen just today myself with a new boss I created. Upon zone startup (zone in), nothing was in place - then a #repop caused him to appear. Subsequent repopping over and over caused him to always appear, so I don't know what's going on. Maybe new spawns only are effected?

Has to be something in the "chance" code check. Or maybe even a timeout trying to fetch the data... shrug. Let us know when you fix it. ~grin~

[soulshot]

<bump>

Testing this out last night.

Mobs with names like killer_mob have a somewhat random chance of actually taking place in the database. I had killer_mob000 - killer_mob004 spawned and added into the database, brought the zone down and came back to 1 spawn. Respawned the same mobs again.. and they still took on the killer_mob001 - killer_mob004 profiles like they had never existed. Again I let the zone shut down and came back - no new mobs.

Went into the database and changed the name of the mob to KillerMob... went back into the game - my original killer_mob had changed to KillerMob of course, so I went about #dbspawning/adding the area just as I had before and EVERY MOB STAYED. Woohoo! So I don't know if something got broken in the latest builds but thats the only work around I can use for the moment.

-Mard

[gernblan]

I figured this out.. it's because the spawngroup names in your DB are getting longer and longer and are exceeding 30 characters (which is what the field is defined as).

I am NOT sure what changing the field itself would do to the emu.. but it does seem that some are running up against this with long mob names in long named zones.

I changed mine to varchar(50) and I get no more add or create errors and my mobs always stay, but this DOES seem to be affecting performance in a big way.

Can anyone more knowledgeable than me chime in on this please and perhaps suggest a solution now that I have at least defined the problem?

For example... here's one in my DB now...

growthplanea_serene_forest_spirit02654599733

That is longer than 30 chars obviously. And when I try to #npcspawn add another one in game, I get a server error messages in my logs that the query failed. So the spawn did not get added.

[John Adams]

I am not sure changing the varchar(30) to varchar(50) should effect performance (or it shouldn't really). I'd also guess the Emu doesn't really care what the name of the group is for anything important. spawngroup.name is supposed to only be a friendly name field, yes? The only place I really see it used is during the insert. I thought everything went off the spawngroupid?

But you could be onto something with truncating the name, and attempting to insert duplicate spawngroup.name data. Cuz "name" is Unique.