You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The usual convention is to limit a bottle to one game [...]. For Steam games, you can create one shared Windows game library that you use between all of your bottles. This helps keep your game installations detached from your bottle instances, so you won't have to re-download everything if your bottle mucks up.
It then tells you how to set up a bottle with Steam, and choose a directory outside of the bottle for your game library.
However, I believe this does not yet create separate bottles for all games, like the guide says you should do. It feels like there is a final step missing from the guide. After downloading a game via Steam, should I now search for the game .exe files in the newly created Steam library folder, and then create separate bottles to run them?
The text was updated successfully, but these errors were encountered:
Arrived here with the same question – it seems like the implication is to run each game through its own bottle, but … how? Do I install Steam in each bottle and point it at the same shared "drive"?
I'm confused about the recommended way to set up a Steam library with Whisky.
Under https://docs.getwhisky.app/#when-should-i-make-a-new-bottle in the documentation, it currently (https://github.com/Whisky-App/whisky-book/blob/6aa0aed5a1de791769bac92d4e62a94f90284cd9/src/guide.md) says:
It then tells you how to set up a bottle with Steam, and choose a directory outside of the bottle for your game library.
However, I believe this does not yet create separate bottles for all games, like the guide says you should do. It feels like there is a final step missing from the guide. After downloading a game via Steam, should I now search for the game .exe files in the newly created Steam library folder, and then create separate bottles to run them?
The text was updated successfully, but these errors were encountered: