-
Notifications
You must be signed in to change notification settings - Fork 24
Contribution Policy
We're glad you're interested in contributing to Livecountsedit! This article will cover both how to contribute, and the do's and don'ts when it comes to contributing code here.
To contribute directly: The same way as you would to any Github repository: Make a fork of our Github repository, make changes in your fork, and submit a pull request on the original with your fork.
If you would like to contribute an add-on (also known as script) to Top 50: Post your code in the #scripts forum channel in our Discord server. You can test it by pasting into the browser console (Ctrl+Shift+J) or by using the Run Code Snippet button in the Add-ons tab.
That is a great question. Direct contribution generally works best for bug fixes and small features that fit well with Livecountsedit, please coordinate with us on Discord if you ever plan on directly contributing anything big, to prevent any conflicts. Add-ons, on the other hand, can be almost anything you want and requires no coordination with us beyond submitting the code and an image/description. Note that add-ons are considered unofficial and are reviewed less rigourously, so we will NOT guarantee that they will work in all future versions or don't have any logic errors. Add-ons also need to be manually installed by pressing the "Install" button or loading a save file with it installed. If an add-on is ever found to crash the site, we will remove it until the original creator fixes it.
Bug fixes
- should pretty much always be directly contributed
Small features
- if it fits well with LCEdit such that people can have the option by default & you're willing to make sure it works more rigourously: direct contribution
- if it doesn't quite fit well with LCEdit (e.g. a rejected suggestion), script is probably better
Bigger features, utility mods, etc.
- usually works better as a script
- if you want to contribute bigger stuff directly, please coordinate with us so we know and can prevent merge conflicts, and stuff like that
Random fun stuff, MDM-style things, etc.
- almost always works better as a script/add-on
Contributing directly will grant you the Contributor role in our Discord server, while contributing an add-on will grant you the Script Developer role. Both are greatly appreciated and please note that they are just roles, neither gives any special perks in the server.
- Review code posted by others to make sure they are safe before running them
- Fix any critical issues/bugs we find with your code
- Make backups of your save files before installing or testing anything in case you get affected by any bugs
- Keep contents appropriate
- Contribute anything that serves no meaningful purpose (e.g. adds distractions, intentionally makes the site annoying to use, rickroll, meaningless edits that don't actually change or improve anything)
- Contribute code that is difficult to read (e.g. minified, contains misleading function and variable names, any attempts at obfuscation)
- Plagiarize
🚫 Additionally, we will under NO circumstances approve of any of the following AND you may receive a permanent ban from contributing and from our Discord server:
- Practical jokes meant to intentionally annoy or mislead users
- Anything that redirects users off-site or does anything suspicious
- Advertisements, scams, or self-promotion
- Anything that contains material otherwise deemed inappropriate for Livecountsedit, including but not limited to: NSFW, offensive and hurtful language, illegal content, and political or religious messages