NamelessMC: a website and forum for a Minecraft server

A community site first, with Minecraft as the identity layer

NamelessMC is described in the README as free, easy to use and powerful website software for a Minecraft server, and the project is version 2 with the default branch on develop. The v2 feature list starts with forums and custom pages, where you can create your own HTML pages and even restrict access depending on group, then social logins that let users register and log in with services such as Discord and Google. The Minecraft integration covers three things: displaying the status of your Java edition or Bedrock servers, verifying accounts using MCAssoc or the NamelessMC plugin, and the in-game plugin itself. The in-game plugin list is the part that decides the relationship between the site and the game, and it includes requiring in-game verification for NamelessMC accounts, allowing registration for accounts in-game, whitelisting players who have a website account, banning players who are banned from the website, and showing PlaceholderAPI placeholders on website user profiles or in leaderboards. The project site is namelessmc.com/ and the licence is MIT.

The rank sync runs in one direction, and the Discord sync runs both

The integration details are more precise than the marketing summary, and the direction of synchronisation is the part that will surprise people. The NamelessMC plugin synchronises Vault ranks with NamelessMC groups unidirectionally, from game to website, so a rank set in Minecraft appears on the site but a group changed on the site does not come back as a rank. The Nameless-Link Discord bot is the opposite: it links Discord accounts with NamelessMC accounts and synchronises Discord roles with NamelessMC groups bidirectionally. So a server that wants the site and Discord to stay in step needs the bot, and a server that wants its in-game ranks to appear on the site needs the plugin, and mixing the two expectations is the most common source of confusion in this setup. The plugin also displays website announcements in chat, so announcements posted on the site reach players without leaving the game. The plugin supports BungeeCord, Paper, Spigot, Sponge and Velocity, and the README points to the plugin repository for the feature list and installation instructions.

Modules, templates, widgets and the queue

The extensibility story is four separate mechanisms, and each answers a different need. The module system is described as a new powerful system allowing further NamelessMC integration, and it is where third-party features live. The template and language systems allow for total customisation, with developer documentation for template and widget work described as coming soon. Widgets let modules create blocks that can be displayed on most user-facing pages and can show almost anything, which is how a module adds a panel to the site rather than replacing a page. The queue schedules tasks to happen at a certain point in the future, which is how a delayed action such as a temporary ban expiry or a scheduled announcement is handled. There is also an API, documented separately, for writing your own integrations or using one of the maintained ones, and the README says you can write your own or use the provided Discord bot. The wiki article on module documentation is the entry point for the developer workflow.

Installing means PHP, MySQL and a host, not a plugin folder

The installation instructions live on the wiki rather than in the README, which is the honest arrangement for a piece of software with this many moving parts. What the repository does contain is a development setup, and the Compose file states at the top that it is for development and points at the Nameless-Docker repository for production. Its instructions are worth reading anyway, because they show the shape of the deployment.

# Set up:
# sudo mkdir /opt/namelessmc
#
# Run:
# docker compose up
#
# Update:
# docker compose pull

The stack is two services plus a database, with a web container on port 8080 and a PHP container behind it.

    web:
        image: namelessmc/nginx:dev
        ports: ['8080:8080']
        volumes:
            - type: bind
              source: .
              target: /data
        user: '1000:1000' # set this to your user id!
        depends_on: [php]

Everything the site needs is passed as environment variables, including the database credentials, the site name, the admin account and the debugging switch.

            NAMELESS_HOSTNAME: localhost
            NAMELESS_DATABASE_ADDRESS: db
            NAMELESS_DATABASE_NAME: nameless
            NAMELESS_DATABASE_USERNAME: nameless
            NAMELESS_DATABASE_PASSWORD: nameless
            NAMELESS_SITE_NAME: 'Development'
            NAMELESS_ADMIN_USERNAME: admin
            NAMELESS_ADMIN_PASSWORD: password
            NAMELESS_DEBUGGING: 'enabled'

Note the user directive, set this to your user id, which exists so the container writes files as your account rather than root, and note the auto-install flag, which is why the development stack can come up with an admin account already created. Those defaults are for a local development container, not for a public deployment.

The repository layout of a classic PHP application

The top level tells you the framework conventions in use. There is index.php as the entry point, install.php for the installer, 403.php and 404.php for error pages, and .htaccess alongside web.config.example and nginx.example, so the project expects to be deployed behind Apache, IIS or nginx and ships a configuration example for each. The core/ directory holds the framework, modules/ holds the extensions including the Core module, custom/ is for your own pages, and uploads/ is where user content lands, with cache/ alongside for generated assets. The dev/ directory carries the development scripts, which the Compose file uses to run the installer, the reinstall path and the static analysis. composer.json and package.json sit at the top, and the npm side is mostly front end libraries, with the package.json naming jQuery, Bootstrap 4, Fomantic UI, DataTables, Chart.js, TinyMCE and CodeMirror, plus a postinstall script that runs node ./dev/scripts/postinstall.js. The presence of a semantic.json, a Dockerfile.phpdoc and a .styleci.yml alongside the code says the project takes its code style and its generated API documentation seriously.

Translations, support channels and the project's shape

The community around the project is organised in a few visible ways. Translations are provided by the community and there are over 20 languages in the Core module's language directory, with a translation platform at translate.namelessmc.com and a dedicated Discord server for translators, and the README notes plainly that not all translations may be up to date. Support comes from Discord, the official support forum, and a SpigotMC thread. Feature requests go to the forum or to GitHub Discussions, and bugs go to the GitHub Issues tab, with a security policy kept in .github/SECURITY.md. The project takes part in Hacktoberfest, which is a reasonable signal about how it recruits contributors, though it is not a signal about the code itself.

The version history shows a mature line rather than a burst. The recent releases are v2.2.5 from 2026-05-31, v2.2.4 from 2025-08-10 and v2.2.3 from 2025-05-22, with the last push to the repository on 2026-10-12. The default branch being develop rather than master tells you the branching model, and it means a fresh clone gives you the development line rather than the last stable tag, which is a detail worth remembering before you deploy.

Where a full site is more than you need

Three cases point elsewhere. The first is a server that only needs players to be able to sign in with an existing identity, where a Minecraft plugin and a Discord bot do the job without a website, a database and a second thing to keep patched. The second is a community that already has a forum or a website and needs only the link between the two, in which case the account verification and rank sync pieces of NamelessMC are the interesting part and the surrounding site is overhead. The third is a team with no capacity to own a PHP application that holds player accounts, since the security surface of a login system, an upload directory and a web-facing admin panel is a real commitment, and the README points to a security policy for the details of how to report issues rather than how the project handles them day to day.

A fourth consideration is the age of the stack. The front end dependencies are from the Bootstrap 4 and jQuery 3 generation, and a self-hosted site in that stack needs a maintained PHP and MySQL environment. The project does keep releasing, with v2.2.5 published on 2026-05-31, but a self-hosted PHP application is a recurring maintenance job rather than a one-off install, and that is the cost the README does not mention.

Editorial conclusion

NamelessMC fits a Minecraft server owner who wants a proper community site with forums, ranks and a website login, and who is prepared to run PHP and MySQL on a host and keep the software updated. It does not fit a server that only wants a Discord link or a simple whitelist, and it does not fit a team unwilling to own a PHP application that touches player accounts, since account verification and rank synchronisation are the features that make it worth running. Before you install, read the installation wiki page rather than trusting the Compose file, because the Compose file in the repository is explicitly marked as for development, and check which Minecraft plugin you will use, since the MCAssoc route and the NamelessMC plugin route give different group synchronisation behaviour.

Frequently asked questions

Official sources

1. License: MIT
2. NamelessMC/Nameless on GitHub
3. Project website
4. README
5. Releases