> For the complete documentation index, see [llms.txt](https://walksy.gitbook.io/walksylib-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://walksy.gitbook.io/walksylib-docs/walksylibservermanager/overview/faq.md).

# FAQ

<details>

<summary>Can I switch off any mod?</summary>

No. WalksyLibControl can only switch off mods, and features of mods, that **opt in** on the client. Mods that don't use WalksyLib, or don't declare server opt-out, can't be touched.

</details>

<details>

<summary>Is this an anti-cheat?</summary>

No. The client applies the restriction itself, so a modified client can ignore it. WalksyLibControl is for asking honest players' mods to behave differently on your server, not for enforcement.

</details>

<details>

<summary>Where do I find a mod's ID and feature IDs?</summary>

* The **mod ID** is the `id` in the mod's `fabric.mod.json`, for example `shieldstatus`.
* **Feature IDs** are chosen by the mod author, in the mod's `allowOptOutFromServer` calls.

The easiest way to see them is `/wlcontrol status <player>` on a player who has the mod installed. It lists every mod that player's client lets you switch off, with its features.

Players can also run `/walksylib server` on their client to see what servers can switch off.

</details>

<details>

<summary>Do players need to install anything?</summary>

Only WalksyLib and the mods themselves. The plugin talks to WalksyLib over a plugin channel.

</details>

<details>

<summary>What do players see?</summary>

A notification such as "This server turned off part of Shield Status", with your reason if you gave one. When a restriction is lifted, including when they leave the server, they get a "back on" notification.

</details>

<details>

<summary>Does it work on a Velocity or BungeeCord network?</summary>

Yes. Install it on **each backend server**, not on the proxy.

</details>