Questions about Having a Testing place

Making a Testing place is beneifical for testing bigger game updates without having to constantly shutdown the place and decrease player count, but I have a few questions when it comes to these?

  • How do I not run into moderation with roblox while developing the testing place?

  • How would I go about using HTTP and Datastores while in the process?

Any questions are appreciated!

5 Likes

Can you explain more?

Datastores cannot be transferred across games, only game places

1 Like

What I mean is, could roblox moderate something in the test place which is part of the Start place and the entire game goes down because of it?

and I already know that datastores transfer across game places but How would I exactly test that without affecting the main game.

3 Likes

When you have a testing place, it should be an entirely seperate experience. This means that any moderation taken on the testing place does not affect the m ain game.

1 Like

Yes, I had it happened to me before.

2 Likes

If you want to access the same DataStores, you should publish the place under the same Experience.
If you really need to access this data from another Experience, you should learn how to program an external application that manages the API keys towards Roblox DataStores, but this can be very hard, time consuming, requires programming skills in luau and javascript/python/etc. plus additional costs for hosting may apply.

You shouldn’t have to worry about moderation if you abide by the rules of Roblox, if you still are afraid of losing your progress due to moderation you should consider not using anything you aren’t sure is allowed and make backups of your Place by downloading a copy once in a while (This can also be helpful tracing back hard to spot bugs if you download copies regularly, I do it quite often).

2 Likes

just a warning… DO NOT EVER DEVELOP on the same datastore as your main production experience. Do not EVER do that it is just not worth the risk. This is why roblox disables datastores in studio by default, it’s too easy to screw something up with your databases and too difficult to fix it in a lot of cases.
make a separate experience entirely for where you develop and test your game. not only does it solve the whole server shutdown, publishing, updating, all that stuff, but you also keep it entirely separate from the game that people are actually playing, lowering the risk of any data loss or other critical issues.

as for moderation, i’m not sure what your concern is? unless you’re actively developing something that goes against tos you shouldn’t have anything to worry about.

7 Likes

I don’t see how it’s risky if you’re only using datastores connected to your own UserId, you can’t make mistakes with others’ data. Data can’t easily be wiped accidentally, you can only alter the keys of the DataStores easily, which will apply nonetheless once you update your game.

In general, it’d be great to test with your own data if stuff really works.

Though I must say is lowering the risk of accidentally publishing your place might be worth creating a separate Experience for testing, you can even publish to this separate experience and invite bug testers to find bugs before publishing entirely.

3 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.