I’m currently working on CloudToast which allows people to get games and mod them and then upload them.
Of course, these are only adding to the game which is selected to upload. There could be a possibility someone could try to re-upload it, but there hopefully will be a flag system.
It uses DataStores which collect players into the dictionary. The players will have certain stats, looking like
--: A new player
{
games = {},
mods = {},
badges = {},
warnings = {},
banned = false
}
--: The CloudToast DataStore
{
--: Players
}
If I were to segment that example into code it would be
--: A new player
function plr(args)
return {
games = {},
mods = {},
badges = {},
warnings = {},
banned = false
}
end
--: The CloudToast DataStore
{
plr("JohnDoe"),
plr("Roblox")
}
So you should be able to understand the development of how the DataStores work. As for uploading your game to the database- you’d have to import a CloudToast Modding Module- or a CloudToastMM which would basically allow people to import their mods into the game.
For security reasons, you’d have to probably only have the option to enable mods through a private server, for example.
This is a bit of a big thing for me, as I’ve never actually tried to create something as big as this. I’m not going to send any code or anything like that, as I don’t want to have it spread, however I might show it when I actually release it–
Yes- it’s not ready for release yet but it should be soon!
To-do
- Create a full demo of the Plugin for publishing mods and uploading games
-
Finish the CloudToastMM- it’s still a work in progress
- Finish all DataStores
I’m thinking of purchasing a domain for CloudToast too for the fun of it (and for the datastores being accessed across games!), what do you think?
