Please keep in mind that the information here is subject to change at any time. We might include or remove content as needed.
As many of you know, Roblox has a Featured sort on the Games page. The sort is managed and updated by our Featured Games team. In order to be considered for the Featured games sort, your game must pass a set of guidelines. Those guidelines can be found here.
The rest of this topic is a list of useful information the Featured Games team has compiled to help developers who want their games Featured and those who have been picked for the Featuring opportunity.
Challenges that you might encounter:
Game Optimization
Improving performance on all devices, including low-end devices such as phones and tablets.
Marketing & Advertising
Creating a release schedule and marketing plan. Building a portfolio of usable advertisements and thumbnails.
Game Security
Filtering Enabled with proper networking security to facilitate a healthy game environment free of exploiters.
Scaling Game Data
Using data stores to collect necessary data in a way which scales with growth.
Do not worry, we will work with you on all of these challenges!
Here is a list of resources created by the Developer Community that may help you get started:
If you have any suggestions to include on this topic please reply below and we will check it out.
Feel free to directly message the Featuring_Program group on the Developer Forum if you have any questions or concerns about the Featured Games Program.
We were planning to include the post but at the time it was missing images and we were waiting for our team to resolve the image issue before including it. Thanks for the reminder!
Oh wow lol, thanks for featuring it! I think some of it is a little broken or unreliable, as its in the pinned tutorial set I think Iâll give it a make over!
What is meant by ânecessary dataâ? And whatâs it mean for it to scale with growth?
I mean it may just be talking about saving playersâ data in a reliable way in which they donât lose it sometimes shouldnât lose it, but Iâm just making sure.
This probably means that the game should save whatever the player would expect to be saved so that they can resume playing next time theyâre on. This is different for every game. Data stores can be complicated once error handling and retrying is taken into account, so it makes sense that this would be one of the âchallenges that you might encounterâ.
This probably means that your data store system should not break with an influx of players or with a game update.
Here are some things that wonât scale with growth: (do not do these)
Sticking all player data from every player that has played the game into one single table under a single key
Grabbing a playerâs position on a leaderboard by iterating through all results in an ordered data store
Storing player data across many keys such that it takes a lot of data store calls to read or write a playerâs data
Making many data store calls for other reasons, such as checking all of a playerâs friendsâ data stores (could be 200 calls!)
Not having any indication of the version of a playerâs data. (If your data format changes in the future then you might need to know the current version of the playerâs data to transfer it to the new format or fill in some new default values.)
Not having error handling, retrying, or autosaving.
A lot of these might be fine at a small player count, but once your game grows they could cause problems. You need to avoid things such as these which will cause problems when your game grows.
