Skip to main content

Nightbreak Account Linking and Tokens

Nightbreak-managed content downloads now use a shared token flow through MagmaCore.

  1. Open your Nightbreak account page.
  2. Generate your server token by clicking on the Generate New Token button.
image
  1. Copy the command from the account page and run it in-game:
/nightbreaklogin <token>
  1. Once you have run the command, you should restart the server to finish token setup.

Once that succeeds, compatible MagmaGuy plugins on the same server can use the shared token for Nightbreak access checks and downloads.

The shared permission registered by MagmaCore for this command is nightbreak.login, which defaults to server operators unless a server admin changes it.

  1. Open your Nightbreak account page.
  2. Scroll down to the Linked Accounts section and click on the Link button for the service you would like to link.
image
  1. You will be taken to the service webpage where you will be asked to log in if you are not already, then taken directly to the authorize window where you will be asked to allow Nightbreak to access the necessary data to link your accounts.
  2. After you have linked your accounts, you should have access to the content acquired through the service on your Nightbreak account and in-game if the token was set up correctly.

Where The Token Lives

The token is stored in:

plugins/MagmaCore/nightbreak.yml

under the token key, not inside each plugin's private folder.

That means:

  • you do not need to register the token separately for every plugin
  • reinstalling one plugin does not necessarily lose the token
  • deleting the shared MagmaCore config may require you to register the token again

What The Token Unlocks

A linked token is used for:

  • checking whether the server account can access a content package
  • checking remote version metadata for managed packages
  • downloading content directly into plugin import folders
  • detecting whether installed packages are out of date
  • enabling Nightbreak-aware setup-menu states

It does not bypass plugin-specific requirements such as:

  • installing a resource pack
  • enabling a content package in the setup menu
  • keeping dependencies installed

Security Notes

  • Treat the token like a server credential.
  • Do not post it in public chat, screenshots, or support logs.
  • If you think it has leaked, revoke it from the Nightbreak account page and generate a new one.
  • MagmaCore warns if the token does not look like a Nightbreak token prefix, but it still attempts to save it.

Troubleshooting

"No token registered"

The plugin is not seeing a valid shared Nightbreak token yet. Run /nightbreaklogin <token> again and confirm that plugins/MagmaCore/nightbreak.yml now contains a real token instead of a missing or placeholder value.

"You don't have access to this content"

The token is valid, but the linked Nightbreak account does not currently unlock that package.

One plugin works, another does not

Check the plugin-specific setup page. Some plugins still need:

  • a first-time setup menu completed
  • a reload after imports
  • a resource pack installation step
  • an optional dependency such as FreeMinecraftModels or ResourcePackManager