Quote:
Originally Posted by varyag
Bullshit. This is what I get in reply to a reasonable post. Plain Bullshit.
|
Why the hostility? Your response is simply uncalled for. I made an honest post, and this is how you reply?
Quote:
Originally Posted by varyag
Why even talk about 'safety coding'?! We aren't discussing Microsoft operation systems here. Its a simple database update.
|
I take it you don't work on enterprise level databases.
The fact that I was able to access old items by re-using a character name definitely exposes the fact that items are tied to a relational database using names as a possible index.
Combine this with a rename function, and you have the potential for ripping off other people's stashes without even accessing their characters.
So, do you get it yet?
Quote:
Originally Posted by varyag
I suggested ONE such update to be allowed PER ACCOUNT. ONCE. To allow the OWNER of the account to CONSCIOUSLY and DELIBERATELY decide on a PERMANENT account name.
|
One thing I've learned about designing production level databases is that you always leave an audit trail. The name field could be used by ANET for indexing related records. If so, then renames are something you'd absolutely want to minimize.
Quote:
Originally Posted by varyag
Currently it is assigned by the game based on an algorithm unspecified in the game's manual which is just plain WRONG.
Someone creating his first character as "ASDF GHJK" just to test the game will FOREVER have that test name assigned to his account. WHY?!
Outrage.
|
You can delete test name characters and replace the character altogether.
So much for that argument.