|
A while ago, I made a thread about how to get rid of inactive players. However, there were many complaints about how people needed inactive players for history lessons or such. To this day I think that the majority of inactive players won't cause benefits to ROBLOX, but, that is WNTS, so this is not the main topic. So, here is my point:
PROBLEMS:
Have you ever wanted a really cool username, or you wanted to change into a really cool username, but that was already taken by an account in 2006 and he left the next day, and he made me have to write a run-on sentence to explain the frustration of this? Me neither. But close things have happened. So, usernames should be able to be used despite someone already having it! Right? No, not exactly....
The newer problem if we DID let usernames be used multiple times is...well...a noob will probably use ShedLetSky's username and try to act all cool. Then he will join a server, and EVERYONE's username is ShedLetSky. Then the REAL ShedLetSky will be hard to find because OBC users will try to dress as him, and then ShedLetSky will be an annoying name to all!
SOLUTION:
Here is my compromise. IF a user was last seen 5 years from now, then anyone can use that username. If someone else tries to use it AFTER that player, they won't get the username. If the inactive player comes back online, then they will both share that username, however, the former-inactive player will have a tiny "origional" next to their name when you look at their profile, and maybe a tiny "O" next to their username in servers.
Actually, let's put that "O" idea up for debate.
And there you have it guys! Please support if you liked it and tell your thoughts on this in the comments! And remember: no flaming! Bye! |
|
|
TrulyRejuJoin Date: 2011-01-30
Post Count: 2893 |
or just learn how to pg
that's easy |
|
|
|
support
time to namesnipe cinnabon if it comes out |
|
billaslobJoin Date: 2014-07-25
Post Count: 60710 |
hahaha No. |
|
|
KorniakJoin Date: 2013-08-09
Post Count: 3538 |
Support!
My computer runs on PotatoDOS. |
|
|
No.
First come, first serve. |
|
|
No.
I'm not 100% positive on how the ROBLOX log-in servers operate but I believe adding multiple passcodes all under 1 name would mess with it big time.
Such as I believe the process goes:
>finds username in SQL server
>Checks if credentials match
>If it doesn't then it goes to the wrong log-in screen
>If it does match then it goes to your homepage
The problem, I believe, would be switched all of the pre-existing users over to numbers. Now I'm not the best with SQL stuff but I'm 90% sure you'd have to change a lot of stuff just to make all of the pre-existing users numbers. It'd also be a struggle to re-write (what I presume to be) old code written for creating new accounts.
So just from a tech standpoint
>Have to rewrite a lot of things with the pre-existing user code
>pretty much have to rewrite all of the new user code
>Have to have the site down for maintenance for (what could be) a good 4-8 hours.
and the list goes on.
Now it is a fair note that if ROBLOX's server code already used numbers (Which would just create more conversion issues thus dragging down log-in speed) it could do your idea with probably little issues. But it's likely ROBLOX has a reason for it's usernames all being unique.
tl;dr: no support, too many issues. |
|
|
No support.
People should not have to suffer because they haven't been on the site for so long.
GG. Next! |
|
|
If you don't understand what I'm saying
Current proccess (probably):
Log-in screen> Server> Matches username> checks credentials> logs in.
What your process would propose:
Log-in screen> Server> matches username with number> Server> Matches number with credentials> logs in
Do you need more reasons why this would be a bad idea?
|
|
MerlecatJoin Date: 2013-10-23
Post Count: 26 |
@Data
No one asked how it worked. You're essentially beating a dead horse. |
|
|
Data's right, well, from what I understood. I don't understand many technological things or anything,
There are machines and computers making sure your PW is correct, not people. If the name 'lasy dude' was taken a second time, and the original came back, there would probably be an error, because there are two different correct PW for 'lasy dude.'
GG. Next! |
|
|
This problem won't happen because, well, let's say the inactive guy came back and his username was also used. What would happen is that it's not one account with 2 paswords, it's 2 accounts, 2 paswords, 1 username. What would happen is that the username AND pasword combined will = the account, not just the username. Right now, it works like this:
1. Type in the username (defines the account we want to use)
2. Type in the pasword (the thing we use to access the account)
After this change, then it would work like this:
1. Type in the username (one of the things defining which account)
2. Type in the pasword (the OTHER thing defining which account)
Btw, yes, spelling pasowrd wrong is on purpose |
|
|
@Cool
But the thing is that the server couldn't differentiate which account you were trying to log on to.
i.e.
2 datacrysis' right?
1 has the credential of "googleplus123"
1 has the credential of "youtube321"
Since both datacrysis exist how would you differentiate which account has which credential?
furthermore upon logging in which account would be logged in? technically the account we've defined to datacrysis now has 2 credentials and the server won't be able to differentiate the 2 of them.
But lets go 1 step further with scaling being an issue.
What if we had 50 people with the account name "Telamon" and multiple people had the same credentials, how would they know which account is which?
|
|
AmiletJoin Date: 2011-06-16
Post Count: 58 |
supporrttt |
|
|
No.
" Yeah, realize you're stupid, " |
|