Leaderboard

According to the log, the server is receiving signal 2 which means terminal interrupt. Do you have some cronjobs that are working on the server or something? That is not a crash though.

The alias inserts happen in constant time and the commands !aliases and !userinfo will not have significant performance losses from bigger aliases lists. So there shouldn't be problems experimenting higher g_dbMaxAliases values. The only times when the performance suffers from bigger aliases db is when the db is cached into memory during the map initialization and when using !aliasessearch command. I do think that hiding the true identity can be done by changing GUIDs in general. Also, I do think players should have the option to change it also. At least over time. Using the example of small g_dbMaxAliases value and dropping the least used aliases, it would be possible to hide short lived offensive nicks and fake being a nice regular. While in the case of dropping the nicks by time, even if the most used nick would get lost it would be possible to determine from other stored data that the player is supposed to be a regular. Another poblem is that if the player has 2 nicks with a lot of playtime, it will at some point take considerable effort to have a new nick overcome either one of those old ones. Effectively he would have a possiblity to change his nick freely and all those changed nicks would be lost. We can consider adding option to remove the least used nicks. PS. I think if you want to set some sort of identity info by hand to a player like in the !setlevel example above, I think a Lua script might do that easily. Associating one name, or note, with one guid.

Thanks for adding this feature! It'll definitely be quite helpful for keeping track of players on the server! However, I have a question about how this database makes room for new names... The feature was proposed as dropping the least used names to make room... However, the wiki says... Does it drop the oldest aliases or the least used aliases in the released version? If it does just drop the oldest aliases and the limit is set to 3, someone could just change their names multiple times in a row and all of the stored aliases wouldn't be of much value. Dropping the least used aliases seems like it would be more useful. Also, I have seen people use name changing scripts that actually cycle through the names by changing it each time. If someone has a longer version of that type of script, it could eat through the stored names very quickly.