Wipe the UNION 09 names every once in a while


Rataca  24 Jul 21 at 12:25pm
#12
(22 Jul 21 at 4:18am)Rataca Wrote: Counter proposal, allow us to be a letter prefix before the numbers. If wipes cant be done. You can only have 9999 combinations of name, a letter prefix will increse the amount.

Im just going to bump my suggestion here, as it seems like a good comprimise.

but with the addition of, have the rule of thumb say, try 4 number combos if all done work, use a letter prefix. I got 1234, after 4 attempts after my name was taken at 09.
Wizz  VIP Member 24 Jul 21 at 12:25pm
#13
Bump although idk how possible this is
Rataca  25 Jul 21 at 8:16am
#14
Per faction rules i just found:

https://sites.google.com/view/uu-field-m...ls/general

"All units are required to follow their respective divisions' name formats. (E.g.: MPF UNION 09 ####)
That meaning no lowercased names, all letters have to be capitalized.
In the case of names being taken already, the following actions are allowed to make:
> Using O instead of 0 in the 09.
> Using 0 instead of O in the UNION.
> If all else fails, using a dot at the end of a name format."

I dont think this is in the training room or well known. case and point the above.

Counter argument and i have DMed a bean for this, have this put in clear english in the recruit room.
Void  VIP 25 Jul 21 at 6:12pm
#16
I just type Union in lowercase and nobody really gives a shit, it's what I tell recruits too
Game Boy  VIP 25 Jul 21 at 10:27pm
#17
(25 Jul 21 at 8:16am)Rataca Wrote: Per faction rules i just found:

https://sites.google.com/view/uu-field-m...ls/general

"All units are required to follow their respective divisions' name formats. (E.g.: MPF UNION 09 ####)
That meaning no lowercased names, all letters have to be capitalized.
In the case of names being taken already, the following actions are allowed to make:
> Using O instead of 0 in the 09.
> Using 0 instead of O in the UNION.
> If all else fails, using a dot at the end of a name format."

I dont think this is in the training room or well known. case and point the above.

Counter argument and i have DMed a bean for this, have this put in clear english in the recruit room.

Most NCOs tell rcts this
Rataca  26 Jul 21 at 4:16am
#18
(25 Jul 21 at 10:27pm)Game Boy Wrote:
(25 Jul 21 at 8:16am)Rataca Wrote: Per faction rules i just found:

https://sites.google.com/view/uu-field-m...ls/general

"All units are required to follow their respective divisions' name formats. (E.g.: MPF UNION 09 ####)
That meaning no lowercased names, all letters have to be capitalized.
In the case of names being taken already, the following actions are allowed to make:
> Using O instead of 0 in the 09.
> Using 0 instead of O in the UNION.
> If all else fails, using a dot at the end of a name format."

I dont think this is in the training room or well known. case and point the above.

Counter argument and i have DMed a bean for this, have this put in clear english in the recruit room.

Most NCOs tell rcts this

Dama said it should be in all the recruit rooms on all the maps and is going to make sure it is.
Fasko  Director of Infrastructure 28 Jul 21 at 1:52am
#20
TLDR; the only proper solutions are either getting a staff member to run `/freerpname` for you whenever you need a name freed up (though you'll have no clue whether the person w/ that name is actually inactive or not), or the database route that impacts performance which means Sentinel is hella' unlikely to add.

The only way to not impact the server's performance while dealing with this shit is to just use the `/freerpname` manually whenever you need a specific name freed up, but that's pretty wack imo.
If you stick to the `/freerpname` method and automating that, then you have to deal with the name wipe chaos, which is also pretty wack.

Here's my attempt at a solution that lets the server just handle all the shit on startup: https://github.com/fasko-web/darkrp-cleanrpnames
There's still the performance issue of inserting into the database whenever a user joins, so that you can keep track of whether the user's active or not, but I can't really think of a different way to handle it.
Having the module wipe names of a certain regex (ie. UNION 09) is also pretty pointless. Since you're gonna' be required to sort through all the rows in the `darkrp_player` table regardless, you might as well just handle everyone's rpname.

Concerns regarding database corruption is pretty unsubstantiated though, since they're designed to be reliable, even when handling large amounts of data. You only get corruption when you start messing with the its structure.
  • 13 participants


  • Forum Jump