About subscription-only features for modules made by the community, open-source rules and user-customization for storage management

[Kevinking500]

Okay so for the first question:

• Are we allowed to make specific features in our module subscription only or something like that with a subscription get x instead of x with the basic plan?

Second question:

• Are there specific rules about modules REQUIRING to be open-source, or can it also be partially open-source or even completely closed source? I am asking this because currently my modules I make are not really needed to be closed-source, but my upcoming module(s) such as Roblox integration or ER:LC integration is hard to make it open-source without possibly breaking ToS as alot of things are secrets.

Last question:

• Are we allowed to let users configure storage management options? Such as choosing if they want user information and punishment history to be remained for 1 day (or longer with a subscription, if allowed, see first question), or like choosing how long they want punishment history to be kept for and then deleted/if they even want that

Thanks for any answers :)

[SCDerox]

• We do not support additional subscriptions for modules, in particular, we have no support or options to collect payment or subscriptions on your behalf. We won't be able to accept features that are behind a paywall.
• There's no technical reason that would prevent an open source release. In general, do not hard-code secrets (like API tokens)? This is a technically solved issue that should not be in the way of an open-source release - this can be solved by simple best-practice software engineering. If you are speaking about patented technology or using undocumented or ToS-breaking APIs, we won't be publishing these contributions on SCNX, regardless of the license of the code.
• You can use the configuration system to allow users to adjust the behavior of the bot, including how long data is stored. Once again, we are unable to accept contributions that would require our users to purchase an additional subscription from you.

[Kevinking500]

Thanks for the information!
Though I more meant a plan from SCNX, and for features that won't hinder the basic use of people but for the people who have a subscription they can have like an extended period of storage keeping or thins that don't disturb the normal use of free plan users.
Yeah I meant API tokens etc, and mostly almost all bots and/or modules are always closed-source and they also need lots of API tokens etc to actually operate the module (and pretty much all integration modules of SCNX are closed-source except the twitch one which is made by a contributor), but yeah I will try my best then to keep it safe and not to the public (as stated in the Discord's Dev ToS)

[SCDerox]

• Usually we make all module features available in the Starter plan. Business decisions are always made by ScootKit (e.g. when features cost us money), but we will work with module developers to ensure that they see any paid restrictions as fair.
• API Tokens should NEVER BE HARDCODED into the source code. Instead, they should be loaded dynamically, for example, using environment variables or the configuration system. You can see this in action in the Twitch module. There, jateute used the configuration system with a hidden field (if I recall correctly), which in our internal version is being replaced by the SCNX Credentials Deployment System as part of the Bot-Hosting infrastructure.

[Kevinking500]

• That's great! I definitely do not plan to set specific features to a paid SCNX plan, but mostly for things (I believe costs SCNX more money) such as extended storage periods, I think a 3-5 days storage period is fair and users wouldn't really require anything longer for something basic like ping protection logs after leaving the server, though some people may want it longer. Same thing goes for keeping the logs, for something simple as this I think anything longer than 3 months is unnecessary unless action was taken to the user via the module, where it keeps the logs for up to 6 months (configurable by the user) and longer could be a paid feature
• Exactly that's what I meant haha, couldn't get to the hardcoded word, but that's what I plan to do with such modules ^^

[Kevinking500]

Btw as additional context to the above, I provided the main reason why I asked the question about paid stuff in modules, but I totally understand that ScootKit decides if it should be paid or not :)
I will put your reply as an answer so it will be closed, have a great day ^^