+
+ PumpkinMarket Review Guidelines
+ High-quality plugins for a high-quality community.
+ Last Updated: June 11, 2026
+
+
+
+
+ Plugins are a great way to extend the functionality of PumpkinMC servers. Our goal is to provide a safe experience for users
+ and a great opportunity for every developer to succeed. We’ve developed these Review Guidelines to help you through
+ the development process.
+
+
+
Before You Submit
+
+ - Ensure your plugin is complete and functional.
+ - Test for crashes and server performance impact.
+ - Check that all links, icons, and metadata are accurate and final.
+ - Verify that your plugin follows all security best practices.
+
+
+
+
+
+ 1. Safety
+ When users download a plugin from PumpkinMarket, they need to be certain that it is safe to do so. Your plugin should not contain self-replicating code, backdoors, or any features that could harm a server or its data.
+
+
+
1.1 Objectionable Content
+
Plugins should not include content that is offensive, insensitive, upsetting, intended to disgust, or in exceptionally poor taste. Examples of such content include:
+
+ - 1.1.1 Defamatory or Discriminatory: Content that is defamatory, discriminatory, or mean-spirited, including references or commentary about religion, race, sexual orientation, gender, national/ethnic origin, or other targeted groups.
+ - 1.1.2 Violence: Realistic depictions of physical harm or violence against people or animals. Content that encourages self-harm or illegal acts.
+ - 1.1.3 Sexual Content: Overtly sexual or pornographic material, including "adult-themed" plugins.
+ - 1.1.4 Harassment: Features designed to facilitate doxxing, stalking, or targeted harassment of server players.
+
+
+
+
+
1.2 User Protection
+
PumpkinMarket is dedicated to the prevention of "griefing" and malicious exploitation at the platform level.
+
+ - 1.2.1 Malware: Plugins must not contain any malicious code. This includes viruses, backdoors, hidden "OP" commands, or any code that performs actions without the server owner's knowledge.
+ - 1.2.2 Phishing: Plugins must not attempt to steal user credentials, tokens (like Discord tokens), or any sensitive configuration files from the server host.
+ - 1.2.3 Remote Execution: Plugins must not download and execute arbitrary code from external sources that was not included in the original WASM binary approved by the market.
+
+
+
+
+
1.3 Data Privacy
+
Data privacy is a fundamental right. Plugins must be transparent about data collection.
+
+ - 1.3.1 Transparency: If your plugin sends data to an external server (e.g., for analytics or licensing), you must disclose this clearly in the description.
+ - 1.3.2 Opt-out: All telemetry or external reporting must provide a configuration option to be disabled.
+ - 1.3.3 Sensitive Files: Plugins must not access or upload files outside of their designated data folder without clear justification and disclosure.
+
+
+
+
+
+ 2. Performance
+ Users expect plugins to be reliable and efficient. Unoptimized plugins can crash servers or cause significant lag, leading to a poor user experience.
+
+
+
2.1 Plugin Completeness
+
PumpkinMarket will reject plugins that are not yet complete. We do not accept "placeholder" plugins or versions that are non-functional.
+
+ - 2.1.1 Minimum Functionality: Plugins must provide a meaningful extension to the server experience. "Empty" plugins or those that only print a message to the console will be rejected.
+ - 2.1.2 Stability: Plugins that cause the server to crash or hang during normal operation will be removed.
+
+
+
+
+
2.2 Accurate Metadata
+
The information you provide about your plugin must be accurate and honest.
+
+ - 2.2.1 Screenshots: Screenshots must accurately reflect the plugin's interface or effects in-game. Do not use generic or "stock" images that are unrelated.
+ - 2.2.2 Categorization: Plugins must be placed in the most relevant category. Mis-categorizing to gain visibility is a violation.
+ - 2.2.3 Descriptions: Do not include irrelevant keywords or "tag spam" in your description to manipulate search results.
+
+
+
+
+
2.3 Resource Management
+
PumpkinMC servers run in high-concurrency environments. Performance is critical.
+
+ - 2.3.1 CPU usage: Avoid blocking the main server thread. Use asynchronous tasks where possible.
+ - 2.3.2 Memory leaks: Ensure your WASM binary does not leak memory over long runtimes.
+
+
+
+
+
+ 3. Business
+ monetization on PumpkinMarket should be transparent and provide clear value to the user.
+
+
+
3.1 Payments
+
+ - 3.1.1 Integrated Payments: All transactions for plugins must go through the PumpkinMarket system. Linking to Patreon, PayPal, or other external payment sites within the plugin or description is not allowed.
+ - 3.1.2 Digital Goods: Plugins must not unlock features via external "keys" or "codes" purchased outside the market.
+
+
+
+
+
3.2 Business Practices
+
+ - 3.2.1 Bait and Switch: Plugins must not change their primary purpose after approval or hide essential features behind unexpected paywalls.
+ - 3.2.2 Fake Reviews: Developers found to be inflating their own ratings or reviews will be permanently banned.
+ - 3.2.3 Scamming: Any plugin found to be a scam or "vaporware" will result in an immediate permanent ban and possible refunding of all affected users.
+
+
+
+
+
+ 4. Design
+ A great plugin is more than just code; it's also about how it's presented and how users interact with it.
+
+
+
4.1 Copycats and Spam
+
+ - 4.1.1 Originality: Do not simply "clone" another popular plugin. While similar features are allowed, your plugin should offer unique value or a different implementation.
+ - 4.1.2 Spam: Do not upload multiple near-identical plugins. Consolidate features into a single, high-quality plugin with configuration options.
+
+
+
+
+
4.2 User Experience
+
+ - 4.2.1 Consistency: We recommend following standard command patterns (e.g., /pluginname help) to ensure a familiar experience for users.
+ - 4.2.2 Documentation: Provide clear instructions in your description or a linked wiki. Plugins that are impossible to configure or use will be rejected.
+
+
+
+
+
+ 5. Legal
+ You are responsible for ensuring your plugin complies with all applicable laws and regulations.
+
+
+
5.1 Intellectual Property
+
You must be the original author of the code or have the legal right to distribute it. Using leaked or stolen code ("leaks") will result in an immediate ban.
+
+
+
+
5.2 Open Source Licenses
+
If your plugin includes open-source components, you must adhere to the terms of those licenses. Include necessary attributions and license files within your plugin archive.
+
+
+
+
5.3 Right to Remove
+
PumpkinMarket reserves the right to remove any plugin at its sole discretion if it is determined to be detrimental to the market's reputation or user safety, even if a specific guideline has not been technically violated.
+
+
+
+
+