Out of the blue! I may have found a workaround. The query below is quite simple. I don't plan on testing several hundred character create combinations. I don't think it would work on all of them. I'm also uncertain if this would affect bind points. It has worked for the few I tried that didn't work before.
Code:
update start_zones set `start_zone` = `zone_id`;
update start_zones set `zone_id` = `player_choice`;
I would rather have a real fix than a cheap hack.
* It does affect bind points as noted in the character_bind table. I suppose the only thing hurt for the noob after appearing in front of their gm naked is their pride. Stiil, not ideal or resolved. This has been happening for quite some time. unix_timestamp = 1417319554 - first occurrence of double bind coords in the table - around 8/9 months?
This also leaves SoF clients with the same problem Titanium clients had, I believe.