Questions regarding contributing by making a module for SCNX

[Kevinking500]

Hey, I have multiple questions about contributing to SCNX with a module. These are the following:

• Is there a limit/rule about how long information is stored in the database? For example is there a rule where it can't be forever until deletion, or something else?
• Are there limitations/rules that apply when communicating to external API's, if so, what are they?
• Additionally please provide me with additional information that I may not (or may) already know that can be useful for me

Thanks!

[SCDerox]

Hi,

Thanks for your interest in contributing to this project.

• There are no limits for data storage in general. However, the data should be adequate, relevant, and limited to what is necessary in relation to the purposes for which they are processed or stored. Please avoid storing PII where possible. When publishing your module to SCNX, it will undergo a review process where we will be able to assess your data use and request changes if we find compliance issues. You might also need to publish what data your module uses for what purposes in our documentation (https://docs.scnx.xyz/oss/create-module-docs/ for details).
• Before a module gets published on SCNX, we will thoroughly examine your use of external APIs. In general, we require that external services meet European privacy standards and have a clear disclosure of company information; in particular, they must have a complete privacy policy that meets European regulations. In addition, your use of external APIs may not violate our guidelines, the API operator's guidelines, or Discord's guidelines. Before publishing a module on SCNX, we will complete a full review of your use of the external API and take steps or request changes to ensure compliance with third-party rules and applicable regulations. As a developer, you usually don't need to worry too much about these steps, as they will be conducted by us. If your API requires developer registration or an API token, we will also take care of obtaining these details and maintaining the contractual relationship with the API operator on behalf of our customers.
• Since I can't know what you don't know, I can't really provide any detailed comment about your last point, but we're always happy to assist where possible. In general, we recommend you have a strong understanding of JavaScript and the Discord API to develop a successful module.

[Kevinking500]

Alright, thanks for the replies and information!
That's exactly what I was needing to hear.
One last question:
How can I make the bot interact with the database of yours?
Additionally (if I do manage to get the module working successfully) that the native Integrations page allows for the user to enter the key as currently that page does nothing :)

[SCDerox]

To interact with the bot database, please create a sequelize model in the model directory specified in your module configuration file (see README.md for details). I suggest checking other modules for their use of the database. To learn more about sequelize ORM, please visit: https://sequelize.org/

[SCDerox]

This seems like a more complicated module that likely requires much more work than you expect. Could I suggest making a smaller module first (something that for example only works on Discord without any third party APIs) so you get a feel of the systems before committing to such a big project? 😄
Happy to provide ideas via DMs if you are interested.

[Kevinking500]

I plan on making 2 modules:

• a more simplified general roblox integration (just basically Roblox + Discord, where commands provide user information, and possibly later more features) to get into the basics of these systems, as there is also pretty much no database required for this, just API calling and that's about it
• The more complex module for ER:LC, the one here above where loads is needed and it's a huge project that takes up alot of time, testing and effort, which I am up to for a challenge after getting known to the basics ^^

But I am definitely also interested in a smaller module aswell to get into some Discord basics ^^

[Kevinking500]

Update: I have decided on a not too hard, but not very simple module to start off:
A "ping protection" module with fully customisable messages, settings and more.
No need for any API requests - Everything is handled inside Discord with possible Discord API requests but I will see - and some data storage for user history (only if enabled, otherwise nothing is stored)