ASTROWORLDMC|Developer Applications

• Maintain plugins and supporting automation that keep the live server healthy.
• Keep docs and internal notes accurate so other staff can follow handoffs.
• Make production-safe changes instead of risky guesswork on a live server.
• Investigate issues with grounded debugging and evidence.

• Comfortable with Paper, plugins, and production-safe changes.
• Grounded debugging instead of guesswork.
• Can document changes for staff handoff so others can pick up the thread.

• Past plugin work, scripts, or tooling you have shipped to a live server.
• Examples where you debugged a real issue with logs or traces.
• Evidence that you write down what you change, not just what you fixed.

• Have links or summaries of past technical work ready before applying.
• Read the requirements page to gauge fit.
• Apply through the main Astroworld site once your examples are organized.

Why do you want this role?

Every role starts here, and the form asks you to be specific about what makes you a good fit. 600 characters is roughly a hundred words, so lead with the reason that is actually yours and one example that backs it up.

Portfolio, GitHub, or code samples

Repositories, plugins or projects. The listing asks for a GitHub link or actual code rather than a description of code, and the form says the quality of that code gets reviewed.

Languages and frameworks

A short list. The form's examples are Java, Kotlin, the Paper API and Skript, but the role itself is Java plugins only, and Skript on its own is not enough.

Have you built Minecraft plugins before? Describe them.

Give the plugin's name, what it does and whether it was published. That is the whole prompt, so three clear sentences about one real plugin cover it.

Java plugins only

The Developer listing opens with those words. Skript is not enough for this role, even though Skript shows up as an example on the languages question, so a background in scripts alone does not meet it.

At least one plugin that works

If you have never shipped a working plugin, the listing says this is probably not the right time to apply. The plugin does not have to be famous, but it has to exist and run.

Code, not a description of code

Link your GitHub or paste the code itself. Reviewers look at quality and not only at whether it runs, so pick a repository you are happy to have read line by line.

Four required answers

Developers explain why they want the role, share code samples, list their languages and frameworks, and describe past plugins. It is the only role where every proof question is required, so set aside more time for this form than the others need.