Does quest::disable_spawn2 work?

[MNWatchdog]

I'm trying to depop a area of a zone of it's current mobs and prevent those mobs from respawning using quest::disable_spawn2(#####); and the mobs still continue to spawn.

I want these mobs to stay down until I use quest::enable_spawn2.

I've tried using the disable both before and after depopping the mobs.

Am I using this wrong? Did a search and there's no examples I can find of it being used and of course the Wiki has no information other than this function exists.

[trevius]

I haven't really messed with those commands much yet, so I am not sure, but that is another one that KLS made examples for. Here are the examples she made:

sub EVENT_SAY { 
        if($text=~/despawn/i)
        {
                quest::disable_spawn2(10842);
                quest::say("Yes sir!");
        }
        elsif($text=~/enable/i)
        {
                quest::enable_spawn2(10842);
                quest::say("Yes sir!");
        }
        elsif($text=~/spawn/i)
        {
                quest::spawn_from_spawn2(10842);
                quest::say("Yes sir!");
        }
}

I believe you use the spawn group ID, NOT the NPCID, but I could be wrong about that. I also believe that disabling it should depop it for you, so you shouldn't have to use a depop on them as well.

[MNWatchdog]

Shouldn't it be called disable_spawn_group then?

I guess that makes sense it would be groups, but the command name definitely should be changed if it is, if for nothing else, because there's almost no documentation other than the command itself.

Why didn't search not show that there we examples?

Well, anyways, I'll try group IDs.

Thanks.

[nenelan]

Spawn groups are stored in the dbtable, spawn2. Makes sense to me.

[joligario]

@nenelan: No, spawn groups are in spawngroup and spawnentry. Individual spawn points are in spawn2.

@MNW: Have you thought about using spawn conditions instead?

[MNWatchdog]

Originally Posted by joligario

@nenelan: No, spawn groups are in spawngroup and spawnentry. Individual spawn points are in spawn2.

@MNW: Have you thought about using spawn conditions instead?

Spawn conditions? Not sure what ya mean. I just started putzing around with scripts 2 days ago.

Examples always appreciated.

OK, found what you're talking about....and learning continues.

[KLS]

It takes the spawn2 id. Ex:

mysql> select * from spawn2 where id=10842;
+-------+--------------+---------+---------+------------+------------+----------+----------+-------------+----------+----------+------------+------------+---------+
| id    | spawngroupID | zone    | version | x          | y          | z        | heading  | respawntime | variance | pathgrid | _condition | cond_value | enabled |
+-------+--------------+---------+---------+------------+------------+----------+----------+-------------+----------+----------+------------+------------+---------+
| 10842 |         7667 | qeynos2 |       0 | 139.699997 | 312.700012 | 3.100000 | 0.000000 |         640 |        0 |        0 |          0 |          1 |       1 |
+-------+--------------+---------+---------+------------+------------+----------+----------+-------------+----------+----------+------------+------------+---------+
1 row in set (0.00 sec)

[MNWatchdog]

How do I get the Spawn2 ID from NPCs ID then?

Example please.

[KLS]

mysql> select * from spawn2 where spawngroupID=(select spawngroupID from spawnentry where npcID=2093);
+-------+--------------+---------+---------+------------+------------+----------+----------+-------------+----------+----------+------------+------------+---------+
| id    | spawngroupID | zone    | version | x          | y          | z        | heading  | respawntime | variance | pathgrid | _condition | cond_value | enabled |
+-------+--------------+---------+---------+------------+------------+----------+----------+-------------+----------+----------+------------+------------+---------+
| 10842 |         7667 | qeynos2 |       0 | 139.699997 | 312.700012 | 3.100000 | 0.000000 |         640 |        0 |        0 |          0 |          1 |       1 |
+-------+--------------+---------+---------+------------+------------+----------+----------+-------------+----------+----------+------------+------------+---------+
1 row in set (0.18 sec)

Keep in mind these are spawn points you don't turn them all on and off at once, they're one at a time.

[MNWatchdog]

Nevermind - Really need a way to delete post!

[joligario]

I seriously think it would be easier to just put the pit mobs on a spawn_condition...

Example: Kithicor changes night/day mobs.

[MNWatchdog]

Originally Posted by joligario

I seriously think it would be easier to just put the pit mobs on a spawn_condition...

Example: Kithicor changes night/day mobs.

If I understand this right, I'd have to basically make a copy of all the spawn2s in the zone and set the new set of entries in the pit to a different condition than the normal mobs, which has them disable from spawning. Then I just use set the condition to 1 for spawned and 2 for not spawned?

If that is correct, I guess I could do that. Just so newb, wasn't wanting to make significant DB changes.

I'm making these fixes for general consumption.