Shared Whitelist between multiple Servers/Modloaders
Per the title. I host several different Minecraft servers, including modded, using the Pterodactyl Panel (i.e., each server is in its own docker container) on my own machine out of my home. Some servers use Forge, some NeoForge, some Fabric. Each server is whitelist controlled.
All of the servers are played on by the same community. So, from a practical perspective, every whitelist is (supposed to be) the same.
However, when someone new joins, I have to go through each console and add them to every server. TL;DR, I'm getting tired of it and decided to take a look at this again.
Last time I looked into this, those solutions I found were limited in that modloader incompatibility, or "player not found" (despite said player ID absolutely existing) issues, made them non-starters.
However, I've realized that through Pterodactyl, it's possible to set up a shared mount between each of those docker containers.
Before I go through the effort of testing that out, I figured I'd ask here to see if there's any unforseen hurdles in saving a single whitelist in this shared mount and then linking the whitelist file in each server to the mounted whitelist.
Does Minecraft actively monitor the whitelist files, such that every client would pick up additions to the file, or do servers only update if you issue a whitelist command on them? etc.
Thanks!
4 Replies
It’s relatively easy to check if mc actively monitors the whitelist files
Start a server, edit the whitelist file while it runs and then try join (e.g. if you removed your entry from the whitelist and the above is true, you shouldn’t be able to join)
I don't believe it will reload the whitelist files at runtime unless you run /whitelist reload
Thanks, yeah, I know I can test it, and will probably double check tonight once I'm back from work - figured I'd take a quick poke to see if it's even worth trying
i mean its still worth trying
you could just have a datapack reload it every so often