Bug 51: I was using the .summon comman...

[BugTracker]

Bug ID       : 51 - I was using the .summon comman... 
Bug Date     : 2014/11/22 01:32:15
Assigned To  : Lokked
Priority     : Medium

Category     : VGClient
Sub-Category : Other
Severity     : Standard
Reproducible : Only seen once

Details:
I was using the .summon command on various creatures in Khal. When I stacked wasplings on top of each other, they all disappeared except for one of them. This did not happen with rats and cackler pups.

Originated From World: New Telon (1)
Chunk                : Khal (85)
Location             : -1141 -56879 1259

Entered on Dec 14, 2014 14:12 by John Adams
Thinking this could be a client anomaly, how it handles 2 things in 1 exact location at the same time (saw it earlier with dupe raw data too). Posting only to follow up as we design spawn location handling

[Lokked]

This may be unintentionally intended. I didn't consider that people would be using this in lieu of the .combine command, but it sounds like this is what's happening.

Standing in 1 place and .summon'ing will place all of the summoned NPCs into the same _placements record (it's got a unique constraint on Position/Orientation). Because the wasplings are all the same spawn_id, it would have just combined these records into 1, whereas different spawn_ids would each have their own _entry record.

I'll have to investigate this and make .summon more in line with .combine.

[Moldew]

I'd like to add what may have been happening. When I summoned the wasplings, they all ended up under the world. I ended up under the world myself somehow and found them. This was done on a stairwell, so if you looked closely, you could see the tips of their wings.

This only happened once too, and it was at a specific location.

[Lokked]

Would you say this happens at any stair case, or particular to stair wells, or one particular location?

Please me me know about the location. If its going to be an issue with some stairs, perhaps we can spawn the mobs else where and they can path to the stairs.

[John Adams]

Yes, definitely do not use .summon as a form of Combine. Add things to a combine list using .spawn combine add. Then you can .summon your PH placement configure to the spot you want if it's not where you want it.

[Moldew]

This related? (Since we were dealing with wasplings)

viewtopic.php?f=16&t=1048&p=8673&hilit=.combine#p8673

Also, what about this? Buncha NPC's standing on the same spot. (What I would do it just delete the dupes.)

viewtopic.php?f=16&t=1048&hilit=.combine#p8590


Sorry if I'm going on a tangent here...

[Lokked]

With the bunch of NPCs just standing in 1 spot, I would just .combine them. Whatever you think is faster. Even if its guards facing different directions: .combine will remove all duplicates. It's not just for creating to PH/Rare Spawn relationship, although it will do that. It's meant to be an easy way to say "All this clump of spawns should be a single spawn location. And please preserve the variety of spawn types."

The first link, where there appeared to be an error, you can ignore. It's doing what it's supposed to be doing.

[John Adams]

Content dudes,

I will make an attempt to do up a little in-game video of how I "clean" areas. As with anything, there's a dozen ways to do one thing, but I'll show you mine if you show me yours

Basically I just make macros:

Code: Select all

/say .spaw combine 20
/say .spawn combine save

I target my middle guy in a pile, the radius of 20 keeps it nice and tight, then click my hotbar icon for the macro (set to the "1" key on my keyboard) and in one click the pile is combined and converted into a single spawn point. That is for stationary spawns.

For wanderers, set a macro:

Code: Select all

/say .spawn remove

to button 2 or somewhere safe you won't accidentally click it. Then just find the best location for your wanderer to start its wandering, and simply target+click the Remove macro on the rest.

Remember, New Telon only has sandbox data on it now, so don't worry about messing up. This is all a practice run until w re-parse our raw data hopefully in Jan 2015. Then we can start this for reals.

[Kilsin]

That would be really helpful John, thanks