Early development of SL 9.2.7 (45745), DF 10.2.7 (55664) and TWW 11.2.7 (65299)
Hi folks,
a quick update on the three newest client targets. Over the last few days we chased a couple of long-standing issues and one very stubborn client crash, and all three builds benefited.
Character look on the character screen and in the world (9.x, 10.x, 11.x)
The newer clients no longer take the classic skin/face/hair bytes; they want a list of customization choices. We now convert the stored look into those choices, so your characters finally look like themselves again on the character screen and in the world instead of showing the default appearance.Logout works (7.x to 11.x)
Choosing “Logout” used to do nothing. The logout response has to travel on the instance connection on these clients, and 11.x additionally wants a different logout-complete layout. Both are in, and you are back on the character screen as expected.The War Within 11.2.7: world entry and a Thunder Bluff crash
11.2.7 now gets past the loading screen and into the world: object updates use the new entity fragment list, the glue screen gets the warband collection and connection status packets it waits for, and the Item/ItemSparse hotfix records are served from the item properties.After that, every character entering Thunder Bluff crashed the client with an access violation. A bisect pointed at transports, and the crash dump then told the rest of the story: the client was testing a game object flag on a model it never managed to load. Three things were off, and all of them apply to 9.x and 10.x as well:Transport guids (ships, zeppelins, elevators) now use the client’s transport guid format, and elevators travel as transport guids like the reference does.Elevators are sent with the transport states the client expects (24 = active, 25+ = stopped at a floor) together with their stop frames.
Game objects whose model is a WMO (zeppelins, ships, buildings) now carry the map object flag. Since 7.0 the client decides between WMO and M2 by this flag, not by the file extension. Without it, the zeppelin above Thunder Bluff was loaded as an M2, and the client fell over when it looked for the missing model.
Thunder Bluff is safe to visit again on 11.2.7.As always: these targets are work in progress, so expect rough edges. If you hit a crash, the client’s Errors folder plus the server packet log are what we need to track it down.
Connection note
Clients up to 8.3.7 are prepared with the connection patcher from src/tools/connection; from 9.2.7 on the patcher is not used, start the original client through the Arctium WoW Launcher with SET portal "127.0.0.1" in WTFConfig.wtf.Happy testing!News
