SubSer - Create custom subscriptions

Resources Community Resources
#1

SubSer

SubSer is meant to allow the ability to create subscriptions for players to subscribe to. It includes all of the needed functions to set up a working product that can expire after the set time. SubSer is for games that have subscriptions. It is flexible, easy to work with, simple, and get’s the job done.

Setup

  1. Download the model via the link at the top of this topic.
  2. Once downloaded, insert it into your game by going to the toolbox and selecting “Your Models”.
  3. Read through the GitHub repository for examples, documentation, and more details about this module.
  4. Use the collected information to create a script that creates a subscription, activates it, and checks if a player is subscribed or not.

Documentation

type: function module.new (Time, Scope)

This function will create a Sub (otherwise known as a subscription). The parameter Time determines when the subcription will expire. It requires an int to work. The parameter “Scope” determines the name of the Sub. It requires a string to work.

type: function module:Activate (Player, Scope)

This function will activate a subscription for a player. The parameter “Player” determines which player the subscription is being activated for. The parameter “Scope” is used to find the desired subscription.

type: function module.ResetData (Player, Scope)

This function will completely wipe the data for a player for a specific subscription. The parameter “Player” determines which player will have their data wiped. The parameter “Scope” determines which subscription the player’s data will be wiped from.

type: function module:ManualCheck (Player, Scope)

This function will check if the player’s subscription is still active. The parameter “Player” will determine what Player will be checked. The parameter “Scope” determines which subscription the script is checking for.

type: function module:AutoCheck (Toggle, Scope, Player, Callback)

This function will automatically check every few frames if the desired player’s subscription is active. The parameter “Toggle” determines if the auto check is disabled or enabled. The parameter “Scope” determines which subscription the script will check for. The parameter “Player” determines which player the script will automatically check. The parameter “Callback” is the path to a function. This function will fire once the subscription is no longer active.

Conclusion

Thank you for taking the time to read through my post. I hope this module proves useful to you.

GitHub Link: GitHub - Targetry/SubSer
Download Link: SubSer - Roblox

Rate your Experience
  • I love this module; no feedback.
  • I have some feedback (Reply).
  • I have a ton of feedback (Reply/DM)

0 voters

11 Likes
#2

Module seems nice but I think you should provide some code examples & use cases.

3 Likes
#3

I could whip up some code right now however the functions seem self-explanatory. I even included documentation which makes using the module pretty straightforward. If there is enough demand, I will consider it.

There really is only one purpose of this module; to create subscriptions. I don’t really know how to put it differently. After all it is basically just a mock-up subscription service.

#4

Where is the GitHub link? Could you please send it?

#5

I already listed it in my post. Did you not read through the entire thing? Please don’t ask silly questions if you have not fully read through my post. It is located near the bottom of my post.

#6

For me it doesnt show, see:

Screenshot (323)
Screenshot (323)3840×2160 440 KB
is this a devforum bug or something?

#7

I would say it is a devforum bug. It appears for me. Here is the link: GitHub - Targetry/SubSer (Fingers crossed it works).

#8

Thank you so much, the link works, I will attempt to report the forum bug in the bug report category soon!

1 Like
#9

It would be nice to include more flexibility in adding custom datastoring methods. From the looks, it only uses DataStore2, which is great, however, creating a new datastore for a subscription under a scope is not efficient and could result in throttling. Adding a callback function would be extremely useful so developers can link it into their existing datastores.

Other than that looks like a nice module!

2 Likes
#10

Added to my list of things to do. I’ll get to work on that. Thank you for the feedback.

1 Like