#Aliases History
1 messages · Page 1 of 1 (latest)
The correct way to write is txAdmin instead of TxAdmin.
Sounds like something useful, hopefully Tabby agrees with us 
What would be a use case for it though?
Like, for you
Ofcourse some players might get crazy on changing their names, so some sort of hardcap of lets say 5 or 10 names would work just fine. Or a way to "Pin" a previous name to save it
The main reason for this is that we usually have a pretty good knowledge about most of our players and we don't spend much time looking at / investigating behavior of "known" players.
That said, even the "old dogs" sometimes start changing their names to bizarre things and we simply loose track of who is who. (For example , see pic)
Sure we can look at the play-time (we notice it's one of the old players) we then check their identifiers, try matching it with Discord IDs or character identifiers in-game, to only then identify the person correctly.
And doing this for last 2 years is tiring 😄
yeah a list of "previous usernames" sounds really useful
In the picture above, the name is some sort of invisible character. And when the word gets spread out more and more players go into this "incognito" mode that sure protects them in some scenarious but is hella hard for admins
i didnt know it was possible to have an "invisible" name
In HTML this character is ᲼ but I'm sure thare are others
i like this
Maybe also a way to add something that stops these “invisible” names?
that's for Cfx to fix
but lets not make this post too bloated in case tabby doesnt wanna scroll back
I mean thinking about it, yeah
txAdmin just reads the playername from the native
Yeah okay
I thought about this a few times, the issue that stopped me is that if we log player names, there is also a expectation that we allow searching for those player names, and that's an issue when thinking of server performance
Hmm... At least in my case I don't really need the search functionality, but it makes sense what you are saying
There are, and i can guarantee that I have spent hours and hours making the player names as readable as possible.
I doubt any other fivem project out there has a better function then txAdmin does.
But of course there are like 150 tthousand unicode characters out there, so sometimes a few pass through the cracks
Yeah fair enough
are any of those players connected in your server right now? i'd love to see the players.json data so i can filter out tthose invisible characters as well
Unfortunately they are not currently connected. Is there anything I can do for you when they do connect?
:rocket: Congratulations @tulip loom, you leveled up to <@&828359841512816671>!
I have their entry in the new list
Technically I already filter out the range of zero widths... apparently that one is undocumented https://superuser.com/questions/1611705/why-are-u1cbb-and-u1cbc-invisible-on-windows
use the browser dev tools to intercept the request that happens when you click to open that player's card/modal
and share the response with me
or give me an admin account with no perms and i can do that myself
I'm tired and not thinking straight, but isn't there a way to use FireFox's approach on this?
font rendering is not really txadmin's business, leave that to the browser
best i can do is to filter out the known bad ones
I'll DM you info
shouldnt it be Cfx's task to make sure that the playername is sanitized tho?
just utf-8
Yeah okay fair enough
for example people abuse the javanese text adornation characters that are way bigger than a single line
so i remove them
same for zalgo text
but what if we just tell people that it's not possible to look for usernames but ids and just make a separate thing on the player modal with previous names?
I mean, it still is something cfx should fix
im sure some DB's break bc of these names
Technically if you type in something in the search that would become an empty string, it will convert it to a pure text "emptyname" and that is searchable
so if you type in empty, it will find them
wow
Thank you, this will make things easier
i still feel like the previous names feature would be cool tho
It would, true. I don't mind skipping the search functionality if that is the major thing that is blocking such a feature
sure, but not something I can do in 15 minutes
also those characters are just undocumented, apparently
lol
The lengths some people go to do these things...
on chrome they are rendered as invisible