[m0th]

New hiccup.

If I try to make a Shar Vahl starting Vah Shir, it actually sends it to Crescent Reach - despite having gutted those starting locations out entirely.
I think that may be in the server files itself as a default when it cannot find a location to send the new character to though.

Any help on that would be bangerang...

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Original Issue RESOLVED

- Current World:Expansion set to 0 (Classic).
- Expansion:CurrentExpansion set to 0 (Classic).

- Gutted Crescent Reach / New Freeport as character starting zones out of the databases to avoid zone syncing issues. I have no intention of using these zones anytime soon, if ever.

- Set expansion_req to 0 for all class-race combinations in hopes this is a step to allowing all base race/class combinations available in Classic.

- Set World:CharacterSelectExpansionSettings to 2175 (Up to Gates of Discord + Serpents Spine) - This allows me access to Iksar, Frogloks, Vah Shir + Berserkers and Beastlords

- Edited world/client.cpp Race/Class tables set to true for everything.
(Trying to make All Class / All Race - just adding details)


Concept: Make Vah Shir available in Classic, but start in Kelethin.

// Added Start Zone points for Vah Shir to start in Kelethin

// Shar Vahl Start Zone Points marked as 3 min, 99 max in start_zones table. Vah Shir Kelethin start points 0 min, 2 max. (This should make it so that when Luclin is available, it will swap to Shar Vahl by default?)

// Shar Vahl marked as 3 min, 99 max in zone table. (Just extra checks.)

// Vah Shir / Shar Vahl expansion_req set to 3, Vah Shir / Kelethin expansion_req set to 0. (Just extra checks.)

// - ROADBLOCK -
Cannot select Kelethin for Vah Shir, and they continue to end up in Shar Vahl on character creation.

After a bunch of digging, I was reading it may be hardcoded in Titanium.
Is this just a Titanium issue? Should I just use SoF?