#advnpcspawn

[jenco420]

Originally Posted by ChaosSlayer

Ok I seem to have problem simular to what Cavedude is describing - I have entered data for roambox into DB spawngroup table - and nothing is happening. NPCs just sit there doing nothing.
I have zoned out and zone back in - do I have to fully restart the server for this to take effect?

BTW I still don't get what is the diffirence betwin: dist and delay:
dist - how far npc will travel
vs
delay - how long it will travel?

isn't it kind of same thing for the purpose of roaming around?

I had to fully restart my server to get them to start roaming.

[cavedude]

Originally Posted by trevius

I know I have successfully used roamboxes. I used them for an event I was working on and they actually worked really well. That event isn't currently running on my server anymore though.

If I was to guess to what might be causing problems, I would think it could maybe be related to the timeleft field being moved into it's own table. I am not positive, but I think timeleft was a field in the spawngroup table. If so, maybe #advancespawn and the roamboxes stuff is failing because it is still looking for that field and not finding it. That is pure speculation though. I haven't done any research into it yet.

That's a great thought. I'll give it a look now.

[ChaosSlayer]

restarted the server - mobs still refuse to roam.

[cavedude]

I figured it out. Neither dist nor delay can be 0. I've had delay set to 0 and that's what has been causing it to not function for me. (What threw me off is according to the AI command delay is optional.) Also, the spawnpoint must be within the roambox. If it isn't, then the NPC won't roam at all (I am guessing if the distance is further from the roambox than the dist DB value, it won't move) OR, the NPC will use the roambox coords as the spawnpoint and will move to that loc and sit.

dist is the number of clicks the NPC will move at a time.
delay is the amount of time the NPC will wait at each point before moving to the next. This appears to be in milliseconds, so 30000 = 30 seconds.

We need the ability to add some variance to delay at the least like we have for grids. I'll see about getting that and an option for a dist variance in as well.

[ChaosSlayer]

we need to get George to fix his spawn editor to stop seting roam boxes values to 0 =P
And preferably add roambox values editin to his editor =)

[cavedude]

Ah, I just use the PEQ PHP Editor. Though, I admittedly am a bit biased

[ChaosSlayer]

Originally Posted by cavedude

Ah, I just use the PEQ PHP Editor. Though, I admittedly am a bit biased

well George tools set are very handy when you need to keeps lots of data from varios tables on the screen at once =)
I just hope he gets the setting to 0 errors fixed SOON =)

BTW about what you said before: we could use 2 additional collumns in roamboxes table:

delay_type:
0 - full delay
1 - half delay + random up to full delay
2 - random delay from 1 to delay specified
(just like in pause in grid)

and same for distance traveled:

dist_type:
0 - full distance
1 - half distance + random up to full
2 - random distance from 1 to full

so each mob inside a roambox can travel variable distance per trip and stop for variable pause.

[Arcaan]

Originally Posted by trevius

I know I have successfully used roamboxes. I used them for an event I was working on and they actually worked really well. That event isn't currently running on my server anymore though.

If I was to guess to what might be causing problems, I would think it could maybe be related to the timeleft field being moved into it's own table. I am not positive, but I think timeleft was a field in the spawngroup table. If so, maybe #advancespawn and the roamboxes stuff is failing because it is still looking for that field and not finding it. That is pure speculation though. I haven't done any research into it yet.

Ahhhhh the Turkeys...almost went insane

[Dibalamin]

Originally Posted by Secrets

It's basically a box.

min_x = west x location
min_y = south y location
max_x = east x location
max_y = north y location
dist = distance it will roam from where it randomly spawns
delay = time before the NPC switches into a random direction

to see an npc roam anywhere, #ai roambox when an NPC is targeted

hope that helps!

Ok, I hate to disagree with someone that is proven to know more than me, but this isn't quite correct. Regardless of direction, the smaller number goes in the min. Took me almost 5 hours to figure out what was wrong with my roam boxes =o. Now, this may work with #advnpcspawn, but it doesn't work for direct DB editing.

[Yeormom]

Originally Posted by cavedude

I figured it out. Neither dist nor delay can be 0. I've had delay set to 0 and that's what has been causing it to not function for me.

You win the prize for this note.