Complely confused on HTTPS saving

I’ll make it short and sweet here.

I don’t know how saving to a 3rd-party works. Roblox tutorials don’t help, and reading other code seems do be confusing. If anybody could explain what resources I need and how it works specifically, that would be cool.

From what it seems like, some people use Github. That’s pretty much all I know, really. Any ideas?


Ok, so you should be using http service But the data in that message will be different on the service you want to use, what do you plan to use?

I am aware it uses httpsservice, but thanks for that :slight_smile:
I also seem to be misunderstanding what you just said. What do you mean by


1 Like

what 3rd party application will you be using?

I would be using Github most likely (I don’t know what else I could use other than pastebin)

1 Like

What data would you like to save?

Likely strings, but possibly numbers.

1 Like

Github is not really a place to store user data if that’s what you’re thinking (Might be against their ToS), also there might be rate limits. If you plan to store user data externally via httpservice, you’ll need to setup a database somewhere that you can use, such as on a VPS, dedicated server, or some other service like AWS. Don’t rely on free services, or do hacky ways to store things (an example would be trello)

If you have no idea how to go about doing any of this, i’d recommend learning how to setup websites using nodejs, mysql, and nginx.

Another thing to note is hosting data may not be cheap. For a small game that has barely any players, it’d not be a problem, however if your game expanded to thousands, your storage could have problems, so be aware. Running databases can be challenging at first (especially if you have no experience).

As to answer your question, it depends on the website you’re saving to, as each website has different URL layouts, and different headers. most would likely use a POST request.


I wouldn’t use it to save player data, but to keep data available for the game to use.

1 Like

Are you planning to use the data across different games?

Possibly. Not sure yet.


1 Like

I’d really recommend sticking with datastores in your case.
Here’s a tutorial i’d use as a reference.

Though i would also say learning nodejs and mysql are really useful skills for later on, but for a game right now, datastore works very well.


I do use datastoreservice already, but ti has limits. I want to be able to store stuff somewhere where I could change data live, without going into the game.

The best example of this is AeroGameFramework, which uses GitHub to store the source scripts.

1 Like

I see, that’s definitely a use case where you’d need httpservice. Though you can still use datastore, how you could do it is:

  • every server pings a custom website every once in a while, like 10 seconds. You then send back things to do, such as edit a datastore.
  • you change peoples data on that website, the website then tells the next game server to change it (assuming the player is not already in game)

This is the only way i can think of to edit datastores remotely. Sadly theres no way for our own websites to ping a game server.

1 Like

What are some free sources to host roblox data one?
I know GitHub and Pastebin are two.

1 Like

I don’t know any free sources to recommend, if you want reliability and scalability, paying is the only option for storing large amounts of data.



1 Like

Use google fire stores from personal use i think its just great! Link:

Oh man, I totally forgot about that!
Do you know how to use it with roblox tho?

Edit: It is pretty great, I used it in an app I made for myself a while back, using Sketchware.

1 Like

Same way you’d use any external database with Roblox - with a solid understanding of:

  • HTTP requests, specifically GET and POST
  • Database management
  • Serialisation and deserialisation (for translating data between your external database and your Roblox game)
  • The external database software you’re using (e.g. MySQL, Firebase, etc)

For security, you’ll want to understand:

  • Authentication vs authorisation
  • Request throttling
  • SSL/TLS encryption

If you want a better system you’ll also want to understand:

  • Backup conventions
  • SQL vs SQLess
  • Different datatypes within the database system you’re using (e.g. signed vs unsigned integers, BLOBs, nvarchars)
  • Orphaned records
  • Data consistency

And if you get really far into the rabbit hole:

  • NodeJs
  • RESTful API specifications
  • HTTP status codes
  • URI conventions
  • DNS configuration

Not a lot of actual information here, but a good list of things to start googling