Host
Needs VerificationPeer-to-peer hosting means the most stable and consistently online player is the sensible campaign host.
Working database
Needs VerificationMultiplayer & Saves keeps the useful rows close to their evidence.
A practical co-op reference for 1–8 players, P2P hosting, portable characters and World-specific progress.
Database section
Co-op frame
The public design supports solo play, online co-op up to eight players and seamless drop-in / drop-out as an intended flow.
Character
Needs VerificationLevel, Equipment, Inventory, Spells and Personal Progression travel with you.
World
Needs VerificationStory Progress, Buildings and Recruited Allies stay with the current World.
Scaling
Needs VerificationHistorical patches confirm party-size scaling existed; the EA formula remains unknown.
Database section
Progression boundary
Use this table when deciding whose save should own a long campaign.
| Character travels | World stays | Evidence |
|---|---|---|
| Level | Story Progress | Needs VerificationSource details |
| Equipment | Buildings | Needs VerificationSource details |
| Inventory | Recruited Allies | Needs VerificationSource details |
| Spells | World-specific Quest state | Needs VerificationSource details |
| Personal Progression | Host network / session state | Needs VerificationSource details |
Database section
Three independent multiplayer permissions
Community guidance separates drop visibility, building ownership and Crafting Bench access. Test these settings independently rather than calling every chest private.
| Setting | What it controls | Practical rule | Evidence |
|---|---|---|---|
| Personal Loot | Controls whether a player sees loot belonging to that character | Does not make every chest private | Needs VerificationSource details |
| LockBuildtoOwner | World setting for access to player-built objects such as chests and doors | Building ownership and chest visibility; test separately from loot | Needs VerificationSource details |
| Chest Public / Private | Whether contents remain available to Crafting Benches | Not a replacement for LockBuildtoOwner | Needs VerificationSource details |
Database section
World creation and safe handover
World difficulty is reported as a creation-time choice. If the original host is unavailable, move the complete World file only after making a recoverable backup.
| Record | Current guidance | Safety check | Evidence |
|---|---|---|---|
| World difficulty | Choose at creation; community/developer discussion says it cannot be changed later | Some players reported Moderate loading as Hard; exit and re-enter immediately to confirm before investing | Needs VerificationSource details |
| World file | %USERPROFILE%/AppData/LocalLow/Mudtek/Dimraeth/Worlds/<world_name>.jrwf | One .jrwf is a complete World; same-name copies overwrite the recipient's file | Needs VerificationSource details |
| Automatic backups | <world_name>.jrwf.bak1 and <world_name>.jrwf.bak2 | Copy the main file and both backups before moving or replacing anything | Needs VerificationSource details |
| Safe takeover | Rename or back up an existing same-name World before copying; third-party sync is optional | Do not delete the original; keep a recoverable backup | Needs VerificationSource details |