VGOEmulator.net

Foof and I concluded most of the data was derived at run-time. Unique IDs, parent IDs, the building types and IDs, though that data is still in the spawn_objects table. Are we just not using it? There's nothing to say we cannot use the SOE-captured values, as long as they remain "unique".

No, it needs to be coded in to the spawn list structs, and the database code needs to be updated to include this in the SELECT statement, and then it needs to be added down the chain of UnrealActor sub-class Constructors.

**Edit - the above was a response to Xinus.
John, I think this should come from the database. During Run-Time, we have no way of knowing that this is a RiftStone Spawn, apart from any other spawn, aside from the name = Rift Stone. It doesn't make sense to check for this name each spawn iteration. It should come from the Database / Spawn Struct.

weeee

I added in the parent_id and the object_id and also added the code to add the parent_id into the packet.

updated values for riftstone in cragwind

then

.move 51518 69161 12000

Nice!!

Xinux also pointed out there is yet ANOTHER discrepancy with data types across all our projects. The Unreal code in VGTesty (that I used to build the database schema for raw data) clearly was a uint32 for parent and object IDs. He just told me they are signed ints. We're getting trounced by this a lot lately, so I'd like a quick review of all our data types in the World Unreal engine compared to VGTesty (UnrealBitLib) so we can stop with the 0's when they should be valid numbers. This is wasting a lot of y'all's time.

I will be looking over VGVisualParser this week, because I want to add some features to the parsing. I won't do another full-parse-of-everything until we get our datatypes in line.

wouch ^^ wonderful !
Again guys ^^ it's a very good job ^^

This rift stone is invisible. If you jump onto it though and rotate in place, you will see it.

.move 54865 69028 10924, NOT the coords listed on other posts here, otherwise you will spawn inside of the rift stone and will be stuck.

Parentid is not being sent most likely.

Was this resolved before? Bug resurface?

The DB currently does not have the values in it anymore for parentUniqueId.