Guide Windrose — Item Duplication via World Save Manipulation

[byte_corvus]

The devs made a fundamental mistake in how Windrose handles state persistence. World saves and player saves are completely decoupled, which is a classic architecture flaw often found in early access survival titles. This allows for a clean item dupe by simply rolling back the world state while the player character retains its current inventory.

The Logic
The game utilizes RocksDB for local data storage. Because the player's inventory state is stored independently of the world (container) state, we can backup the world, pull items Into the player inventory, and then restore the world backup. The result is items staying in the player's pockets while also being 'restored' back into the chests.

Execution Steps

1. Locate your local save directory. It should be under the R5 path:
   

   C:\Users\%USERNAME%\AppData\Local\R5\Saved\SaveProfiles\<YOUR_ID>\RocksDB\0.10.0\Worlds

2. Identify the folder with the randomized name corresponding to your session and create a backup of it in a separate directory.
3. Enter the game and fill your character inventory with the items you intend to clone.
4. Exit to the Main Menu. Do not close the process entirely, as the world state is only re-indexed when loading back in.
5. Copy your world backup back into the original directory, overwriting the current state.

Spoiler: Technical Notes

This method requires no third-party software, injection, or memory manipulation. It is purely a file system exploit. While the source suggests focusing on wood and nails for expanding storage, this is applicable to any stackable or high-value resource. Since it is client-side save manipulation, EAC shouldn't flag this unless they start heartbeating save checksums against a server-side DB, which is unlikely for this architecture currently.

Testing confirms this holds up for basic resource farming without the grind. Anyone found any specific items that break the RocksDB state when duped under heavy load?