Third-Party Seller Terms of Service

1. Acceptance of Terms

By uploading files on waspscripts.com (“the Website”), you agree to comply with and be bound by these Third-Party Seller Terms of Service. If you do not agree to these terms, please refrain from becoming a third-party seller on the website.

Throughout this document, “third-party seller” and “scripter” are used almost interchangeably. Do keep in mind that becoming a scripter doesn’t mean you have to become a third-party seller. If you are not or don’t plan to become a third-party seller, any terms of service exclusively related to third-party sellers do not apply to you.

2. Seller Responsibilities

2.1 Product Liability

As a scripter on waspscripts.com, you are solely responsible for the functionality, performance, and legality of your automation software products (“Community Scripts”). WaspScripts is not liable for any issues arising from the use of your Community Scripts, including but not limited to damages, losses, or disputes. You are also responsible for complying with any software licenses you use on the software you develop. By using SRL and/or WaspLib libraries you are automatically tied to their GPLv3 Licenses. Scripts that don’t use these libraries still require to be GPLv3 licensed to be allowed on this platform. If you are not familiar with this license, it is recommended you at the very least read the GPLv3 quick guide. Additionally, if you choose to sell scripts, you must comply with Stripe’s Terms and Conditions.

2.2 Accuracy of Information

If you choose to sell scripts, you must provide accurate and truthful information when registering to become a third-party seller. Any attempt to provide false or misleading information may result in the suspension or termination of your scripter account.

2.3 User Credentials

Scripts must not read, write, or modify user credentials except as required to interact with the games. Accessing user credentials outside of standard Login functionality should be discussed with staff prior to release. Scripts not complying will be removed immediately for user safety.

Staff reserve the right to punish scripters for deliberate misuse of user credentials. Punishment includes (but is not limited to) immediate removal from the marketplace and/or immediate removal from the WaspScripts Discord Community.

2.4 Malicious Code

Scripts must not contain any malicious code, including but not limited to spyware, adware, or any code that harms the user’s system or data. Scripts may not modify the user file system, except during normal activities such as creating logs, reading/writing user configurations, or taking screenshots or recordings of the game environment.

Any data logged (log files, screenshots, recordings) should protect user information where possible. No debugging information should be sent to the script author automatically; the transfer of logs should be initiated only by the user, whether in reporting a bug or by request of a scripter providing support.

Scripts may not modify or delete any file (except for logging/debugging purposes) without user consent. This includes any method of forcing a user to update to a specific version of the script. For example, deleting the script file or folder is strictly prohibited. Staff reserve the right to punish scripters for deliberate inclusion of malicious code. Punishment includes (but is not limited to) immediate removal from the marketplace and/or immediate removal from the WaspScripts Discord Community.

2.5 Script Accessibility

Scripters cannot prevent users from running their scripts, even after the subscription period ends. This includes:

Adding functions that disable the script after a subscription ends.
Forcing the user to launch a script via WaspLauncher. Users must be able to launch an “unsupported” or “outdated” version of the script without WaspLauncher.
Any code which prevents the user from running a script either now or in the future is not permitted.

2.6 Distribution

As a GPLv3 License compliant script, you may distribute your script and it’s updates in any way you may desire.

Distribution of updates exclusively through WaspLauncher and the website is permitted as there is no requirement for you to distribute versions of your script outside of the official sales channels.

There is no requirement for you to provide source code, bug fixes, or any code snippets to any user, but, minimal customer support is expected and adds value to your scripts if they are being sold.

Leak-proofing is not permitted. Users cannot be prevented from sharing their copy of the script in compliance with GPLv3.

3. Transactions and Funds Handling

3.1 Transaction Reversals

WaspScripts reserves the right to revert transactions made through the sale of your Community Scripts at its discretion. This may be done without prior warning if it is determined that the transaction violates these terms, applicable laws, or poses a risk to the integrity of the platform.

3.2 Fund Holding

WaspScripts may, at its discretion, hold funds from your transactions for a specified period. This holding period is determined by WaspScripts and is intended to ensure the resolution of potential issues, such as disputes or customer complaints.

3.3 Transaction Fee

WaspScripts charges a fee for each transaction made through the platform. As of the current terms, the fee is set at 20% of the total transaction value for euro currency users. For all other currencies, the fee is 22% of the total transaction value. However, please note that these fees are subject to change, and it is your responsibility to stay informed about any updates.

4. Compliance with Laws and Policies

You must comply with all applicable laws, regulations, and WaspScripts’ policies when sharing or selling your scripts through https://waspscripts.com. Failure to do so may result in the suspension or termination of your seller account.

5. Subscription Model

The payment of a subscription fee entitles the user to a copy of your premium scripts (as-is). The user now owns that copy of the script/scripts. You do not retain ownership of that copy of the script/scripts. The subscription duration entitles the user to reasonable support and bug-fixing. Your script should be kept in a state of reasonably similar performance during the subscription period. A paying user is entitled to download a copy of your script from the WaspScripts website or via WaspLauncher at any time during their subscription. If you do not intend to support a script for the full duration of the subscription, do not offer that length of subscription.

6. Free Access

WaspScripts reserves the right to provide free access to any Community Script to any user at its discretion, without notifying the author. Any users with the rank Tester or Moderator have indefinite, free access to any version of the script.

Users with these roles should not abuse their privilege. Testers are expected to use the script for testing purposes. Moderators are entitled to the script to protect end-users and may read or run the script as required to ensure end-user safety.
Users with these roles are asked to be reasonable with light personal use. If you’re using the script for personal use the majority of the time, please support the scripter. All scripters can give free access to their scripts to any user for any reason. This is done through the WaspScripts scripter dashboard. Access can be given for whichever duration the scripter wants, and can be revoked by the scripter at any time for any reason.

7. Source Code Availability

The full, plaintext source code must be made available to users. Any external (non-standard) libraries must be included in the source code provided to users. For the safety of users, no external code (hosted externally or generated at runtime) can be included in the script environment. The entire script environment (excluding standard libraries) must be included in the main script. Standard libraries include:

SRL-Development (https://github.com/Villavu/SRL-Development)
SRL-T (https://github.com/Torwent/SRL-T)
WaspLib (https://github.com/Torwent/WaspLib)
n0ll’s chores (https://github.com/courtwizard17/simba/blob/main/chores.simba)

Obfuscation by ASCII encoding, hiding code in the margins, writing all code on one line, or other coding conventions deemed to be deliberately confusing to the user or staff reviewers is not permitted. All code must be human-readable by staff reviewers (i.e., in plain-text with “normal” standards).

8. Right to Edit or Disable Products

WaspScripts reserves the right to edit or disable any Community Script listed on the Website at any time and for any reason, without prior notice. This includes, but is not limited to, situations where WaspScripts deems it necessary to maintain platform integrity, address legal compliance issues, or respond to user complaints. WaspScripts shall not be liable for any consequences arising from the editing or disabling of Community Scripts under this clause.

9. Respect User Privacy

Scripts should respect user privacy and not collect personal data.

10. Governing Law

These Third-Party Seller Terms of Service shall be governed by and construed in accordance with the laws of your jurisdiction.

By becoming a scripter on waspscripts.com, you acknowledge that you have read, understood, and agree to these Third-Party Seller Terms of Service.