@

i think i see your problem in the code you posted. 0x7007 is one request with an action byte, and 4 is not create:
1 = create
2 = character list
3 = delete
4 = name check
5 = restore (cancel delete)
so right now your server creates the character during the name check, and when the client then sends the real create (1) it doesn't get the answer it expects. the character list also comes from 0x7007 action 2, and the client wants the reply as 0xB007 starting with 02, not on 0xA104. if the list request goes unanswered or comes back in the wrong shape you get exactly what you describe: char in the db, empty select screen, then a crash on relog.
for 4 just answer B007 04 01 if the name is free (or 04 02 + error code if not) and don't write anything to the db. do the insert only on action 1.
this is how it works on the newer isro client, i haven't checked 1.692 specifically but these action codes have been the same since vsro, so i'd be surprised if they differ.