Updated to latest version as of 5 min ago. Problem not only persists, but has spread to more character ID's. Something just caught my notice: Is it normal for the ID's to be out of sequence in the database - does that matter? Because right at the 1st character to have trouble, I see it go from 21834 -> 21837 -> 21836 -> 21835 -> 21838 -> 21839 -> 21841 -> 21840 -> 21842
Update:
I deleted all characters (just to be clear, every time I say that I mean in the client, and I never have navicat open while running) and then filled all slots on the account.
I tried to create new characters filling all slots on the account. It seems character creation itself doesn't really complete for some slots - when in the menu for creating the next, all selection remain including the name typed. Normally when you successfully create a character log out and go to make another the name field is blank.
I got the old invalid key issue on one, and noticed that on the server side it was saying the "invalid key for character Eight" (I named them One, Two, Three...) was not the character I was trying to log in (which was Nine). Afterword those 2 characters were swapped in the client's list. I'm now getting an error on the server side (first time ever for any error message at all) saying "stack around the variable uList" is corrupt. I guess I have to do a wipe and complete rebuild now, and I've no idea what started all this.
Update 2:
Ok, I got it figured out now. I kept thinking it was something I did.
It's a bug. No account can fill the entire 16 slots of the character roster. The 5th, and 10th slots will always get this pol-0001 error. I talked to another person running a server and they said also the 15th slot, but for me after 13 characters the connection server always crashes requiring me to delete one for that account out of the database to even reach the character select screen.