Disabling Shared Quests on a Windrose Server

Not every group plays at the same rhythm. Some players burn through objectives, others wander off to chop trees for two hours, and the rest get stuck reading lore. With shared quests enabled, a single fast-moving player can close out a co-op quest for the entire session, leaving the rest staring at a checkmark they never earned. The fix lives in one line of a JSON file, and the change is reversible at any time.

What Shared Quests Actually Does

With the option turned on, any co-op quest that one player finishes is automatically marked complete for everyone else who currently has that same quest active. The tutorial quest is included in this behavior, so if one teammate finishes it first, the rest never see it appear in their journal. Disabling the setting gives every player an independent quest track, meaning each one needs to complete the objectives personally for progress to register.

Turning the Setting Off

The value sits inside a config file buried several folders deep. Always stop the server before opening it, otherwise the live process will overwrite your edits when it next saves state.

1. Open your control panel and stop the server. Wait until it reports as fully offline.
2. Open the FTP file manager and sign in with your FTP credentials.
3. Enter the R5 folder.
4. Go into Saved, then SaveProfiles.
5. Open Default, then RocksDB.
6. Enter the version-numbered folder (for example, `0.10.0`), then open Worlds.
7. Find the folder for your active world. The folder name is a long random string of letters and numbers, so confirm it before editing if you have more than one.
8. Open WorldDescription.json and locate the entry:

``` "{\"TagName\": \"WDS.Parameter.Coop.SharedQuests\"}": true, ```

Switch `true` to `false`, save the file, and start the server again. Once it boots, every connected player is on their own quest timeline.

Switching It Back On

The steps are identical. Stop the server, open the same `WorldDescription.json` file, and flip the value from `false` back to `true`. Save, restart, and shared quests are active again.

Frequently Asked Questions

Does this reset any quest progress?

No. Quests already marked complete stay complete for everyone who had them done. The setting only governs how future completions behave after the next restart, so flipping the value is safe to experiment with.

How do I figure out which world folder is active?

If you have multiple world folders and cannot tell them apart, head to the R5 root and open `ServerDescription.json`. The `WorldIslandId` value listed in that file matches the folder name of the currently loaded world.

Will players notice the change immediately?

Not until the server restarts. The JSON file is read at boot, so any edits you make are queued until the world reloads.

Closing Thoughts

Individual progression is a small change with a big quality-of-life impact for mixed-pace groups. Everyone gets to feel the satisfaction of ticking off objectives themselves, instead of receiving a silent completion from across the map. If anything looks off after restarting, double-check that you edited the correct world folder and that the JSON still parses cleanly. A stray comma or missing quote is a more common culprit than the setting itself.