Minecraft plugin questions, clearly answered

PostPlugin.org is a browser-based workspace for creating and refining custom Minecraft plugins through a conversation with Swizie. It turns a clear feature request into a structured project you can review and download.

Swizie is PostPlugin.org’s plugin-focused assistant. It can answer Minecraft plugin development questions, plan a feature, create project files, explain the result, and revise a build in the same chat.

Yes. You can ask about plugin.yml, commands, permissions, event listeners, configuration, project structure, or a possible feature before deciding whether to create a plugin.

No Java experience is required to describe a plugin or ask a question. Reviewing generated source, diagnosing server-specific behavior, and making advanced changes is easier with Java and Paper API knowledge, so a developer should review high-impact plugins.

Describe what players or administrators should be able to do, the commands and permissions you expect, any configuration options, important messages, and unusual cases the plugin should handle. Clear examples help Swizie choose sensible behavior.

It is designed for Minecraft server owners, administrators, community builders, and developers who want to explore an idea, prepare a compiled project, or iterate on a focused server feature without beginning from an empty repository.

Generated builds currently target Minecraft Paper 1.21.4 with Java 21. PostPlugin.org does not label another platform or version as supported until it has a dedicated build template and validator.

Those are not validated build targets today. Swizie can answer general development questions about them, but PostPlugin.org will not present an artifact as compatible with Spigot, Bukkit, Fabric, or Forge without the matching project template and validation process.

Yes. A request can define player or administrator commands, subcommands, permission nodes, default access, usage messages, and permission-denied behavior. Include the exact command flow you want when possible.

Yes. Paper plugins can listen for relevant server and player events, such as joining, interacting, moving, breaking blocks, or defeating entities. The request should explain what happens, who is affected, and any limits or exceptions.

Yes. Swizie can create configuration-driven behavior for messages, limits, rewards, timings, feature switches, and other values that a server owner may want to change without editing Java source.

You can describe focused gameplay or server-management features such as quests, progression, rewards, economies, moderation utilities, lobby tools, minigames, custom commands, and quality-of-life systems. A smaller, well-defined first version is usually easier to review and test.

The current validated template does not add arbitrary external Maven dependencies, so third-party integrations are not currently presented as validated output. Swizie can still help plan an integration from public documentation.

A successful build provides a compiled plugin JAR and a source ZIP containing the Java project. The source archive lets you inspect the implementation, keep a backup, or continue development elsewhere.

Test it first on a separate Paper 1.21.4 server running Java 21. Stop that server, place the downloaded JAR in its plugins folder, start it, review the console and logs, adjust its configuration, and verify commands and permissions. Keep a backup.

Yes. Every generated project includes plugin.yml with the plugin name, version, main class, and API version Paper needs. Command, permission, and dependency declarations are added when the project uses them, and the file is packaged into the root of the built JAR.

Yes. Continue the existing conversation to describe a fix, change a message, adjust a command, or add a feature. Swizie uses that project context and shows the newest successful plugin when the revision is ready.

Yes. Download the source ZIP, open the Maven project in a Java development environment, review its dependencies, and continue editing it like another Paper plugin project.

The service checks the generated project, compiles it with the configured Paper and Java toolchain, and validates the packaged output before presenting a download. This catches many structural and compilation problems, but it is not a substitute for testing gameplay on a server.

No. Generated code can contain mistakes, incomplete behavior, security issues, or conflicts that only appear with a particular server setup. Review the source and test every revision before relying on it.

Use a separate test server first. Keep backups, verify commands and permissions, review logs, test with the same dependencies and configuration as production, and only deploy after the behavior is understood.

PostPlugin.org reports the failed build instead of presenting it as a validated download. You can clarify the request or ask Swizie to correct the problem and try another revision in the same chat.

Yes. Supported images and text files can provide visual references, existing configuration, code excerpts, or written specifications. Attach only material you are allowed to share and explain how it relates to the plugin.

Do not submit passwords, session cookies, private keys, payment-card details, private server credentials, malware, or another person’s confidential information. Replace secrets with safe placeholders before attaching a file.

No. Chats, prompts, attachments, generated projects, and downloads are scoped to their owner. They are not published as public plugin pages or included in the PostPlugin.org search sitemap.

No. PostPlugin.org does not expose another user’s conversations, attachments, projects, or downloads through Swizie. Ask about your own project or provide a reference you have permission to use.

Credits are based on generated output. The text and files you send as input are not counted as billable usage, and your account shows the remaining balance and recorded usage.

Yes. An account keeps chats and files attached to the correct owner and provides the credits required for answers and builds. New registrations currently receive 10,000 bonus credits in addition to the Free plan allowance.