Account IDs & Character IDs Not Matching.

Ok so I noticed something strange that I've never really noticed before, when making a new account in the database, it gets assigned an ID of 1024+16++, normally, at least in my experience running a 1.3.6 server, all characters made will have an account ID matching their chars in the database.

So basically a new account in the sql would have the ID of 48 for example, the account ID in the server database would be 48 and the first char would be 48

On my 1.4.6 test server, if I make 2 accounts but log the second one in first, the account ID in the sql database is 1104, yet the account ID in the server database is 1088 and the first char is 1088.

Then if I make a char on the first account that has the ID 1088, the account ID and char ID in the server database are 1104.

Yet if I make an account and log it in and created a char straight away all IDs match up.

Does anyone know how I can modify the server so the account ID given to chars is the same as the one in the sql database. I got no clue as to why it is assigning it IDs the way it is, I assumed it would do the same as 1.3.6 and reserve those IDs so even if someone with a higher account ID logged in first, their account and char IDs in the server database would match.

Figured out my problem, the import roles feature on pwAdmin was importing the logicuid instead of the actual account id, this was modified to import the account id and roleid instead of the logicuid and role id.

hmm never noticed that but on mine I get the same id of the sql... as it should reserve the ids like for example 1024 account id would also be your first charc id... and your next account u make should be 1032 account and chard id

Well I'm not sure when it was changed but in 1.4.6 v80 the gamedbd and uniquenamed both have entries first firstid which looks for the next ID available. I did try to remove it in hopes to restore it to the way it was originally but despite my attempts it still got assigned the next ID available instead of an ID matching the account.

It's find though, I found another solution to my problem at hand.

I got a report of something like this as well... I'm assuming the only 'real' issue is with/while trying to utilize the 'character' page in pwAdmin? or is there more serious repercussions that I've not yet thought of ?