Setup FAQ

Q: Why Client is also separated?

A: To decrease size of client mod folder by 14mb

---

Q: Why client-side mod is not up-to-date with server-side mod?

A: Client-side is rarely changed/fixed so even 3.0.0 client side can join latest 5.2.0 server

---

Q: I added mods to the whitelist/blacklist, but im still being kicked out/bypass

A: Notice that adding mods to whitelist or blacklist through config.yml must be 1:1 with mod id, like hand-shaker and not handshaker, so its recommended to add mods only with commands. Also notice that whitelist expects EXACT mod list, so you must list all mods with /handshaker whitelist_update <player name from which one take mod list>. Although in version 4 was changed and merged whitelist and blacklist together, case-sensitive names still persist.

---

Q: How I can make whitelisted-only mod server?

A: Join your server with your modpack, use command (3.0.0) /handshaker whitelist_update [your nickname] or if v4+ /handshaker add * required|allowed, then use command (3.0.0) /handshaker mode whitelist or in config.yml and set "Operation Mode: blacklist" to whitelist, if you use v4+, then change in config.yml Default Mode: allowed to blacklisted

---

Q: Why every update breaks previous versions?

A: Its because of mod origin. Mod was created to simply blacklist mods only without any future plans, and by people need was added whitelist, require mode (based on whitelist, available in 4.0.0 for old configs), after what I realized how complicated it became. Either you blacklist, either you whitelist, or only require mods from whitelist. So I merged all 3 modes together for better flexibility in 4.0.0. Also I tried to keep some kind of backwards compatibility, but keep in mind, old configs, without v2, support in 5.0.0 will removed.