Get In Touch
Support
Four routes, depending on what you have. Picking the right one is the fastest way to an answer.
Found a Bug
Open a GitHub issue. Include your loader and version, the server log around the failure, and what you expected instead. Issues get tracked; Discord messages scroll away.
Have an Idea
Feature ideas go to GitHub Discussions, where they can be argued about properly and found again later.
Just a Question
Ask in the Discord project channels. If you're unsure whether something is a bug, this is the right place to start.
Report a Player
Player reports and anything you'd rather not say in public open a private ticket with the staff team from the Discord's support channel.
Responsible Disclosure
Security Issues
Please don't post a vulnerability in a public issue or a Discord channel. Use GitHub's private vulnerability reporting, or email the studio directly. You'll get an acknowledgement, and the fix will be credited in the changelog unless you'd rather it wasn't.
Confirmed defects — including security-relevant ones — are published rather than withheld, so you can always see what is currently known and unfixed.
Direct
Email The Studio
For Anything Else
Questions, permissions and licensing, press, partnership, or a security issue you'd rather not file on GitHub. This address reaches the studio directly.
Save Yourself Time
Check These First
Is it already a known defect?
Every confirmed bug awaiting a fix is listed on the status page and in IMPLEMENTATION_STATUS.md. If yours is there, it's known — though a report confirming it affects you is still useful.
Are you on v1.0.0?
v1.0.0 has two confirmed critical defects and is unsupported. Upgrade to v1.1.0 before reporting anything.
Can the server not start at all?
Boot with -Dnexuscore.safemode=true. That loads core modules
only and leaves vanilla's moderation commands intact, which is usually enough to get a
broken server back up while you work out what happened.
Is a permission not doing what you expect?
Run /nexus permission check <player> <node>. It
explains why a player does or doesn't have a node — which group granted it, which
deny overrode it — rather than returning a bare yes or no. Note that at v1.1.0 it bypasses
authorise(), so it cannot show the operator-bootstrap grant: a level-2 operator
can have access it does not report.