Movers (tram, Undercity elevators) need fixing but where?

[Xenithar]

Okay, so my friends and I have been bug-hunting. We found that the Deeprun Tram appears to have both trams on one track and only one is visible to players, but it's not the same one for all players. This makes it impossible to board or, should you glitch on, exit the trams. In addition, one of the elevators and doors for UC is rotated about 90deg out. I am sure this is in the database and I can fix/test/PR it, but where? These are not transports so they're not in there, but where are they?

Edited October 5 by Xenithar
Added tags

[H0zen]

There are two types of transport gameobjects (GO): global map objects (type 15) - ships, zeps - and elevators, trams (type 11). In database these objects are defined in gameobject_template, type = (11,15) and their spawn in gameobject table (except for type 15). A type 11 GO has a start position (x,y,z), a rotation quaternion (4 float values) and an orientation (1 float). I am pretty sure the core does not send the correct orientation for these types, so there is the first place I'll look (a visible symptom is a 90 degree rotated wagon for tram).

[Xenithar]

Now that I think about it, I believe the tram was rotated 90deg also. Time to break out dBeaver! Thank you, H0zen.

[Xenithar]

Okay, everything in the database is correct, so this isn't as simple as I had hoped. I attached a picture of the rotated cars for reference. Not sure what is going on here, but maybe it has something to do with MaNGOS <-> client communication or the way the model gets loaded.

Another problem I noticed is that only one tram loads. Last time the tram closest to the portals was running. After restarting mangosd it was the one further away from them. May be related but I am not sure. The database matches historically correct settings, so I am not sure yet.

[Xenithar]

I want to update this topic. H0zen gave me a patch to try and a detailed testing guide. After applying the patch, everything appears to work now. Every test in his guide passed. This was a code fix, not a database fix.