ModSync
Why should you use ModSync?
ModSync is a client-server setup that adds transparency to the client's Mods and Texture packs.
Here are more ways ModSync might turn out helpful:
-
Anti-Cheat: Instead of the server running continuous checks for cheats, ModSync presents a 1 time check solution. ModSync doesn't just check your mod directory; It checks all the threads running inside Minecraft.
-
Auto-Authorisation: No need for fancy auth plugins, ModSync generates a unique authorisation key for every device. This will link with the player's username once he joins the server. If someone with a different key tries to log in with the user's account, ModSync will kick them for a mismatched auth key.
-
Modlist & Packlist: All the Mods and Texture packs installed on the client will be listed in the username's log file.
-
Screenshot Player's Gamescreen: Admins can use a command to take a screenshot of screenshots of players gamescreen to ensure texture pack legitimacy. (mainly used to detect Xray packs)
🛡️ Core Security
ModSync doesn't just "ask" the client for a list; it uses a secure challenge-response handshake:
Dynamic Hashing: Every handshake is secured with SHA-512 using a server-side pepper and a unique challenge UUID to prevent packet spoofing.
Privacy-First: Players are prompted to agree to data reporting on their first join, ensuring compliance with privacy standards.
⚙️ Technical Features
Categorized Resource Reporting: Unlike basic list-reporters, ModSync distinguishes between Active (enabled), Inactive (in folder), and Deleted resource packs.
Intelligent Mod Consolidation: Automatically collapses library dependencies (like fabric-api sub-modules) into single entries to keep admin modlists readable.
Historical Audit Logs: Every player gets a dedicated .yml log tracking their mod/pack history across sessions—including timestamps of when a mod was removed.
Remote Diagnostics: Admins can request remote screenshots or even "dump" specific mod/pack files directly from a client to verify suspicious files.
Bedrock Support: Native compatibility with Geyser/Floodgate to skip verification for Bedrock players while maintaining strict security for Java players.
💻 Commands
/modsync modlist
/modsync packlist
/modsync screenshot
/modsync dump
/modsync authreset
/modsync reload – Hot-reload all configurations and banned/required lists.
🚀 Setup
- Install the Plugin on your Spigot/Paper server.
- Install the Mod on your Fabric client.
- Configure your required-mods and banned-mods in the server's config.yml.
_Developed by DarkYoddha — Built for Integrity.
All Versions
+ Add Version- bugs fixed
- bugs fixed
- added scrollable requirement list
- matched compatibility with Modsync Server 3.0
- added 2 folders called 'required mods' and 'banned mods'.
- added Anti-Ghost Client/ Anti-3rd party thread check.
- enhanced auth security
- enhanced verification process
- skip verification for bedrock players. (can be changed from config)
- Implemented additional security to prevent spoofing.
- refined packlist registry
- refined player download file management
- Implemented additional security to prevent spoofing.
- Bugs Fixed
- Bugs Fixed
- Added a terms and conditions screen.
- reworked on instance.dat so it won't change if the user deletes it.
- Added force-installed.
- Added required-mods and required-resporcepacks.
- Enhanced Authorisation feature
- Add auto Authorise on cracked servers
- Added **/modsync authreset <username>** to unlink account from client
- Added Encryption authorisation
- Better logging
- Added command **/modsync screenshot <username>**
- Download player's mods & resourcepacks to check for server-banned mods & packs
- Download player's live screenshot (only ingame screenshot: f2)
- 🔧 Previously: players with high pings weren't able to join the server.
- ✅ Now: admins can adjust the kicking delay, giving modsync time to establish connection with the client. Added commands to bypass players.**
- 🎨 Admin commands — /modsync ignore <player> and /modsync monitor <player>**
- Cross‑server compatibility patch:
- 🔧 Previously: the client mod prevented players from connecting to non‑ModSync servers.
- ✅ Now: the client mod only activates when the server has the ModSync plugin, ensuring smooth compatibility across different servers.**
- Improved client verification timing
- 🔧 Previously: the verification window was too short, causing false kicks or missed checks if the client took slightly longer to respond.
- ✅ Now: the verification delay has been increased, giving the server enough time to properly confirm the client’s presence before enforcing rules.**
## Key Features:
✅ **Instant enforcement** — kicks players using banned mods or resource packs
🛡️ **Client verification** — requires the ModSync client to connect successfully
📁 **Audit logging** — generates per‑player .log files showing current and deleted mods/packs with timestamps
⏱️ **Configurable delays** — control grace period for client verification and log generation
🎨 **Admin commands** — /modsync modlist <player> and /modsync packlist <player> with filters and color‑coded output
🗂️ **Persistent storage** — logs saved in plugins/ModSync/players/ for long‑term accountability
## Key Features:
📡 **Automatic reporting** — sends modlist and packlist to the server on join
🔍 **Seamless integration** — works silently in the background, no manual setup required
🛡️ **Fair play guarantee** — ensures admins know exactly what mods/packs are in use
⚡ **Lightweight design** — minimal performance impact, designed for compatibility with other Fabric mods
