Player:PromptRegisterAccount

Feature Requests Engine Features
#1

In the interest of accommodating guests in my game, I thought it would be a good idea to show, once a guest hits a certain milestone, a prompt to create an account on the website. However, it kind of sucks to inform them, “Hey, you should make an account so that your data can be saved! The thing is, no data from this session will be saved, so you’ll have to start all over again! Yay!”

The obvious solution is to tell them to make an account before they play, but I have an idea that may be a win-win-win for developers, guests, and ROBLOX.

I’m suggesting method of Player called PromptRegisterAccount (or whatever) that would open a CoreGui prompt (similar to the developer product purchase prompt) asking the user if they’d like to sign up for an account. If the user selects yes, the signup page is opened in their browser. This method would throw an error if called on a Player object that is not actually a guest.

To complete this feature, an event is needed: Player.RegisteredAccount. This event would be fired when a user currently playing as a guest signs up for a ROBLOX account on the same machine. It would pass as a parameter the UserId of their new account, allowing us to create and save DataStore keys using that new id.

ROBLOX would somehow have to know in which server the new user is playing as a guest, and notify that server of the new signup. I have never done any sort of web programming, so I’m not sure how feasible this is. I imagine lol maybe? it could be done with some IP tracking of the signup machine and guest playing machines? I really don’t know how implementation would work.

This feature would benefit all parties involved. Developers would be able to better satisfy players by keeping data. ROBLOX would see an increase in user conversion and retention. Guests would be able to have their data saved to new accounts.

Please, let me know what you think! Any suggestions are welcome; I’d love to hear what you guys have to say!

21 Likes
#2

I’d love this.

P.S. If you really wanted to save a guests data give them a code. They can re-enter it once they get on a real account and it accesses the datastore for that guests’ play session info

1 Like
#3

That’s a really good idea. I may end up implementing that!

I’d still love to have the suggested method and event of the Player object, just to make it easier on players and developers.

#4

Yeah… I wanted to reply ‘or better yet if they could create the account in-game’

…then realized how much chaos with exploiters that could cause.

2 Likes
#5

I’ve been working on something where guest players can generate a 24-hours redeemable code to transfer save data to their new accounts, but a proper implementation like this would be so much better.

2 Likes
#6

Would need to disable any UIS tracking while the prompt is open to prevent some shady devs logging password entry.

1 Like
#7

I think that the code thing is a great alternative and is a way to solve this however, an official method would actually be great, As you’ve said, all parties in question here benefit from this.

#8

I don’t think this is a bad idea, but in other words, it can be a safety issue, if someone logged or made a fake “signup” gui etc.

#9

Someone can already do that

#10

Huh, that’s an interesting way to deal with it.

#11

This is really good idea! Would LOVE to have this!

1 Like
#12

This is an amazing idea!

An idea for a game could be that if a guest joins, he gets a free bonus/virtual item if he creates an account and logs in, although it will be hard to distinguish which account is his/hers. :stuck_out_tongue:

1 Like