Player-detector-Beta
This, my first project. Allows you to send a pop-up in; Achivements, visual pop-ups, in-game messages! Currently in Beta!
About this Mod
📥 Installation Guide
Player-Detector is built for Fabric Loader. You also need Fabric API – the mod will not function without it.
Install Fabric Loader (most third‑party launchers like Prism, MultiMC, or Modrinth can do this automatically).
Download Fabric API and Player-Detector from Modrinth / CurseForge / GitHub.
Place both .jar files into your mods folder.
Launch Minecraft. To verify correct installation, ask a friend to join your world (open to LAN) or connect to your server – you should see a pop‑up and/or chat message.
You don’t need to tweak anything unless you want to. Default settings show a toast pop‑up (top‑right corner) plus a chat message for every join and leave. To change behaviour, edit the config file or use ModMenu (if installed).
✨ Features
Visual pop‑ups – Vanilla‑style toast notifications (same as advancements / recipe unlocks).
Join / leave messages – Fully customisable text, with placeholders like {player} and {server}.
Achievements on login – Grants a temporary or permanent advancement to the joining player (e.g. “Detected!”).
Toggle per player type – Show notifications for friends, ops, or everyone.
Cooldown & filtering – Prevents spam during server reloads or rapid reconnects.
All features work client‑side (single‑player) and server‑side (multiplayer). On dedicated servers, only the server needs the mod for chat messages, but visual pop‑ups require each client to also have Player-Detector installed.
✅ Requirements & Compatibility
Minecraft: 1.19.2 – 1.21+ (check file page for exact version)
Mod Loader: Fabric Loader 0.14.21 or newer
Dependency: Fabric API (any recent version)
Optional: ModMenu (for in‑game configuration)
Player-Detector is designed to be compatible with the wider modding ecosystem. It does not touch rendering, world generation, or low‑level networking. You can safely use it alongside Sodium, Lithium, Iris, OptiFabric, and most content mods.
Known issues: None reported. If you encounter a bug, please open an issue on our issue tracker.
🐛 How to Report Issues
Please use the issue tracker linked at the top of this page. Include:
Minecraft version, mod loader version, and Fabric API version.
A full list of other mods you have installed.
Any crash report or latest.log file (paste to a gist or attach as a text file).
Note: Visual pop‑ups may be slightly delayed on low‑end hardware or under severe server lag, but core detection remains reliable.
📊 Performance Note
Player-Detector is extremely lightweight. It only runs code when a player logs in or out – typically a few microseconds per event. Even on a server with hundreds of players joining and leaving constantly, the overhead is negligible. No tick‑loop operations, no extra network traffic beyond the standard Minecraft join event.
Available Versions
How to Install Player-detector-Beta on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (1.21.11).
Install Mod
Open the mod browser in the dashboard and search for "Player-detector-Beta". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.21.11
Server-side
✗ UnsupportedRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Player-detector-Beta server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.21.11). You can switch loaders with one click in the panel.
Is Player-detector-Beta compatible with fabric?
Player-detector-Beta officially supports fabric for Minecraft 1.21.11. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Player-detector-Beta – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Player-detector-Beta consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Player-detector-Beta with just one click on your server.