if possible could you add a way to make subscriptions work in multiple places? i want to make a “premium” subscription that works on all of my games, not just one specifically and so people would have even more reason to buy it
my best approach at this would be somehow hosting the data (if player’s subscription is active or not, etc) off-site, like a custom panel or some discord bot, and then the module checks if the player bought that subscription on all my games, if so, then grant access to subscription perks
then again, my approach isn’t very good and you could probably figure out an even better way in around 10 minutes, but that’s how I would do it
You could generate a Roblox API Key of the Purchase Place.
Then, use the API Key to access DataStoreService. (using your own hosted server, since you can’t access roblox apis with HttpService)
I’ll think more about this, find a solution and I’ll insert it into the module.
Quick Reminder:
SubscriptionService is still on Beta, and it can have unknown bugs relating to Robux Purchases. Please consider using it for meanwhile developing. If any bug is found, we’ll update as fast as possible to fix it.
“Please consider doing so, it would improve this a hundred times. I can try to make it work myself if you want and send you a converted version later.” ~ that’s what you said, not me
I’ll attempt to fork your module to use ProfileService and send it to you, because anything that uses the default Roblox DataStoreService and is related to purchases is guaranteed to get a bunch of angry people that essentially lost their robux because whatever they bought has been erased due to DSS’s data issues (only on games with over 200+ people playing at the same time, but still a big problem).
And about API keys, I believe they use their own DataStores for storing the data; outside of the game itself. Which means you could have ProfileService to save the actual module’s data inside of the game, but still have API Keys using and sharing data using DataStores. So while API Keys would still use DSS and (Maybe) risk data loss (Again, maybe. Perhaps they’re using a more secure piece of code for the API Keys’ DataStores, but we don’t know that), the games would have their data protected by ProfileService.
It will expire when the user joins. But the way, it’s a hard way to resolve. One thing I thought, it’s make a python script that haves access to the DataStore, and check for every user. If expired, set to NONE. It’s one of the ways to fix your problem.
This would be a life saver, if you can do it. I’m busy on programming other stuff, and haven’t had the correct time to sit down and do this, thank you for this module and I’m looking forward to it.
Is this module intended for long term use? Such as subscriptions lasting for 30+ days where players may leave and rejoin multiple times, or is it solely for short uses where the player won’t leave the game?