Based on the same investigation where I am curious why we need 10,000 spawn IDs for the same objects... Doors came up a while back. There is a finite list of door types (models), and I thought that if I moved a door spawn_id to something generic, that same door_id could be used across multiple zones.

Door data from SOE is usually named something like "door_widget01", but also sometimes has no name at all, or (unnamed) as it's name. Many variations, so I assumed that meant doors do not really need a specific name in order to work. Armed with this, I took a generic wooden door in Stonestair Byway and renumbered it to 1100. Doing this one simple thing completely broke the door. It would not even appear in game anymore.

So the question here is, the "name" of the door coming from SOE packets, does that somehow have to match something in the client? I wouldn't think so, but I do not understand how else this would just not work. It is illogical

TIA

By renumbered do you mean renamed it to door_widget1100? The door name shouldn't matter, but what does matter is the widget id - which is why we cannot group doors together as the widget ids are unique and mandatory for the door to properly function.

Nah not the `spawn_widgets` data, only the `spawn` ID for the door. So there would be one spawn_id named "wooden_door" for instance, that would have many child records in `spawn_widgets` with the proper widget_id.

By renumber, I mean taking what parser populated as 340001 and renumber it to 1100 (spawn.id)

I am beginning to realize this effort is futile, so please don't waste any of your time analyzing it unless you are just curious wtf I am rambling on about I wanted stranger_01 to open our DB and not shit themselves because there is 10,000 identical spawn records when there really only needs to be 1... but it's becoming a nuisance, really.

Add this to the 'nice-to-have' pile We could do as you request, but we would have to redesign the way that the queries work inside of World as world just does a simple join on both of those tables.

My obsession with 'consolidating data' is strong now, because we have very little data now compared to later. If this won't work for us today, then I think I'd better drop it forever. It'll be way too much work with 100,000+ spawns. And if it means tasking you to change World, no way. Someone else can deal with this after we're retired.