This is a list of guidelines for Polymart. However, this is not a legal document,
and this list is not exclusive or exhaustive.
This list of rules
is for convenience purposes only, and does not require that Polymart moderate, police, or otherwise
monitor submissions. Polymart specifically disclaims any such requirements.
Your use of Polymart is governed exclusively by the
Terms of Service, and not by this list of rules. Please see
polymart.org/terms.
TL;DR Version:
-
Treat others like you want to be treated.
-
Any resource you post must be entirely your own work.
-
People should know exactly what they're getting when they download your resource. Write clear, high-quality, English descriptions for resources, and accurately describe all of the relevant features and necessary intstallation steps
-
Don't password-protect resource files — it won't stop leakers, because they'll just share the file after they get the password. Use Polymart's anti-piracy tools instead
-
If you want to post on Polymart, don't refer people elsewhere to download or purchase your product. Upload everything for your resource directly to Polymart — A readme file with download links is not allowed.
-
We know it's a lot, but you really should read all the rules — it'll help you thrive on Polymart!
All The Rules:
- Just be a good human
-
General Rules
- Keep all content respectful and appropriate.
- Racism, sexism, or other forms of bigotry are strictly prohibited.
- Any form of trolling, flaming, flame-baiting, or being overly aggressive towards other users it not permitted.
- Discussion or distribution of illegal content is not permitted in any form.
- Any photos you post or upload as your user profile picture, profile header, resource thumbnail, or resource header must be rated G or PG.
-
Rules for All Resources
- All resources you post must be entirely your original work, or you must have obtained explicit permission
from the original author before posting the resource
- All resources should be high-quality, and have a high-quality, in-depth description (especially for paid resources). Take a look at some of the most downloaded resources for inspiration
- If your resource requires an internet connection to work (this includes
license servers), you must specifically and visibly notify users in your resource
description. We recommend that you use Polymart's Developer API
- You may not post any resources that are harmful to servers in any way.
This includes forceop plugins or plugins that purposefully slow down the server.
- Uploaded files may not be password protected. Password-protecting a zip file doesn't do anything to deter leakers, because they'll just get the password and remove it before leaking your resource. If you would like to prevent leakers, use Polymart's Advanced placeholders and Developer API
-
Resources without updates for a continuous period of 6 months may be designated as inactive, leading to the restriction of further purchases.
-
To eliminate this designation, a request for reactivation must be made through the provided contact form, alongside an update release before the request.
-
Resources designated as inactive may have new purchases disabled after a minimum of 3 months of remaining inactive. Buyers will always retain access to hidden / inactive resources.
-
Within a timeframe of two weeks preceding the potential designation of a resource as inactive, the respective author shall receive formal notification. The author is strongly encouraged to utilize this period to update and revise the resource in question. This proactive approach aims to prompt the author's action towards maintaining the resource's active status on the platform.
-
Valid reasons must be provided for requesting the removal of a resource. In most cases, buyers retain access to deleted resources.
-
Rules for Premium Resources
- "Low Effort" resources may be rejected. This includes:
-
Resources with a small amount of code
-
Resources with little new functionality
-
Resources with basic code or code produced by tutorials
-
Setups or configurations which heavily rely on default settings/configuration given by the plugin author
- "Common" resources may be rejected. For example, this includes:
-
Resources which are widely offered as a free resource, or does not have any unique functionalities.
-
Resources should never contain illegal or restricted content, such gambling with real money or NSFW content
-
Resources must support the latest stable version of the listed server software or must mention clearly they only support a specific version.
-
The resource download button must directly provide access to the bought resource. You may not upload any required files externally, except for cases where certain resource files are auto-loaded without any interaction from the user (such as resource packs).
-
The use of obfuscation on Java-written resources is permitted, however you must release the original source code of a resource to moderators upon request.
-
You may use external licensing systems to guard your resources for unauthorized use. However, you must:
-
Provide moderators with access to execute the resource in this case, and
-
Clearly state that you use external licensing software in the resource description, along with any requirements for the licensing (i.e, only works on one IP address at a time).
- If you have any form of an anti-piracy system, your plugin must not damage the server in any way, even
if it is detected that the resource is pirated. For example, sending messages to players or disabling the
plugin is fine, but corrupting worlds or other damage is NOT ok
-
You are free to choose an appropriate price for your resource, as long as it is within the allowed range. Resources with a higher price may undergo more thorough checks to ensure that they meet a high-quality standard. If you believe your resource should be priced higher than the max allowed amount, please contact us with a valid explanation of why you believe it should be offered at a higher price.
- Uploaded files may not be password protected. Password-protecting a zip file doesn't do anything to deter leakers, because they'll just get the password and remove it before leaking your resource. If you would like to prevent leakers, use Polymart's Advanced placeholders and Developer API
- If you want to post on Polymart, don't encourage potential users to download or purchase your resource elsewhere. Of course, you can link to another page to
show that your resource is reputable, or to provide more details about your resource, just use common sense.
Examples
-
It's NOT OK to have a "buy" button on your resource page that re-directs to another marketplace or a personal
website to purchase the resource. Instead, use Insert > Purchase Button in the description editor to insert
a Polymart purchase button
-
It's NOT OK to have a "click to see more products" banner on your resource page that re-directs to another marketplace
or personal website to purchase or download the resource. Instead, link to your personal Polymart profile! The one exception is
if you're linking to a personal website / portfolio, and that website links back to Polymart for purchasing or downloading your resource.
-
It IS OK (and encouraged!) to include a link to a wiki, image gallery, video walkthrough, or other place that showcases your resource.
Just make sure to include a link back to your Polymart page to download / purchase the resource!
-
In general, it's ok when it's clear that the sole purpose of the link is to provide more information or more context about your resource.
But, if it's obvious that the link is just trying to get traffic to another website, that's not ok. If you want to post on Polymart, use
Polymart to its full potential!
-
Rules for Resource Descriptions
-
Every resource description must at least contain an English version of the description.
-
Every resource description must be written clearly and with few to no spelling mistakes.
-
With some exceptions, installation instructions must be in the description of every resource. Installation instructions are a series of actions that must be applied to install the resource on the intended platform/software.
Referring to installation instructions inside the resource without providing complete installation instructions in the description is not permitted — people should know what they're getting BEFORE the download it!
The following resources do not need installation instructions:
-
Resources with a single plugin JAR file that do not require ANY setup. If further ANY setup is required (like changing settings in a config file), then installation instructions are required
-
Maps if they use a commonly used format. For example: the minecraft ANVIL format, the SCHEMATIC format
-
Models that include configuration files for popular items-adding plugin, AS LONG AS the compatible plugins are listed in the description.T
-
Resource Packs or Resources that only include a 3D/2D model, image, or generic asset not tied to a specific software system and using a commonly accepted format. For example: 3D model of a hammer, or an item image for a shop.
-
Every resource description must contain a written list of all the main features of that resource, so the people knows exactly what they are downloading.
-
The configuration options/settings and the behavior of these configuration options/settings of the software in a resource must be clearly explained, either in the configuration file or in the description
-
Rules for Chat
- Just be a good person, and you should be fine
- All images must be rated G or PG. If you post a NSFW image, you may be permanently IP banned.
- Don't spam or flood chats with random or useless messages
- Do not advertise anything unless it is directly related to the discussion.
- If you do advertise something, make sure to mention that you are advertising it. And, if you created it, make sure to mention that as well (no shilling)
These rules may be updated from time to time, with or without notice.
This list is not exclusive or exhaustive. Your use of Polymart is governed exclusively by the
Terms of Service. You must read and agree to the Terms of Service before
signing up for an account or posting a resource.