AuthMe Configuration

The editor lets you configure AuthMeReloaded through ordinary fields and switches. The result is a downloadable config.yml file for your Minecraft server.

It is intended for Minecraft Java server administrators using AuthMeReloaded. It is especially useful when manually editing YAML or finding settings in a large file is inconvenient.

Click New config, wait for the official 6.0.1 template to load and select a section. Edit the necessary settings, then download the file using the export button.

No. The editor provides an AuthMeReloaded 6.0.1 template for new configurations. For an existing server, import its current file after making a backup.

You receive a downloadable YAML file named config.yml. This does not install the plugin: AuthMeReloaded must already be installed separately, and the configuration must be transferred to the game server.

The editor accepts .yml and .yaml files. It checks whether the YAML can be parsed but does not guarantee that every option is supported by your installed AuthMeReloaded version.

Imports are limited to 512 KB. If the file is larger, check whether it contains logs or unrelated data; do not blindly remove settings you do not understand.

DataSource.backend supports SQLITE, MYSQL, MARIADB and POSTGRESQL. Choosing another backend does not automatically migrate existing player accounts; plan data migration separately.

With PASSWORD, the player chooses a password. With EMAIL, AuthMe generates a password and sends it to the supplied email address; that mode requires working email delivery.

The editor checks selected values and conflicting combinations, such as forcing login while kicking the player after registration. Correct the highlighted setting and review related options; this is not a complete plugin-behaviour validator.

The configuration targets AuthMeReloaded on Minecraft Java server platforms. Do not assume the same settings work on Bedrock; the actual server software must be checked separately.

The built-in template targets AuthMeReloaded 6.0.1. There is no version switcher yet. Older imported files may have valid YAML while still containing settings that are incompatible with this release.

You may import a file that satisfies the YAML and size limits. However, the editor does not automatically upgrade or convert configuration keys between AuthMeReloaded versions.

Availability depends on the server platform. According to the 6.0.1 config.yml comments, postJoin requires Minecraft 1.21.6+ on Spigot or 1.21.11+ on Paper; on other versions the setting may be ignored.

The editor includes Hooks settings related to proxy integration. It does not install AuthMe Proxy or configure Velocity or BungeeCord themselves. For automatic login, the shared secret must match across the relevant proxy and backend servers.

Use the Show YAML button in the result panel. Preview is initially hidden because the configuration may contain database passwords and other secrets. Hide it again before sharing your screen.

After loading or importing a configuration, click Download config.yml. If nothing was changed, the editor preserves the original file bytes; after edits, it generates updated YAML.

On the game server, AuthMeReloaded normally uses plugins/AuthMe/config.yml. Stop the server, back up the current file and replace it with the downloaded configuration.

Inspect the Minecraft server console for AuthMe loading errors, then test registration and login with a test account. With a proxy, also check transfers between servers and repeated authentication.

Edit the required option, download config.yml again and inspect the new version before installation. Keep the previous working configuration separately for a quick rollback.

YAML import, editing and export run locally in your browser. The configuration file itself is not sent to the website backend for processing. Do not publish its contents in messages or screenshots.

No. This editor version does not save configurations to your website account. After closing the tab, rely on a local copy that you downloaded earlier.

A configuration mistake may prevent players from logging in. Before replacing config.yml, copy the working file to a safe location; if the new configuration fails, stop the server and restore the previous one.

Recognized secret fields are masked and can be revealed by a separate click. Never put real passwords in public messages or show an unmasked YAML configuration during a stream.

Common causes include invalid syntax, duplicate keys or exceeding the size limit. Check the problematic section and retry; do not share a configuration containing actual secrets.

Valid YAML only means the file can be parsed. The plugin may reject an unsupported option, an invalid value or a setting unsuitable for the server version. Check the console and documentation for your installed build.

It does not run a Minecraft server, connect to your database, verify email delivery or test authentication. Field warnings and validation cannot replace running AuthMe in the actual environment.

Make sure a configuration was loaded into the editor and try exporting again. Check browser download restrictions; do not replace the working server file until you have successfully saved config.yml.

Use the AuthMeReloaded 6.0.1 documentation in the AuthMe/AuthMeReloaded GitHub repository, especially docs/config.md. Verify uncertain settings against the comments for the build actually installed on your server.

Describe the steps to reproduce, page language, setting name and expected outcome. Include your AuthMe version and server platform; attach only a sanitized example without passwords, IP addresses, tokens or secrets.