From df96e6fd0e51047388ccbabec4f5027522935df9 Mon Sep 17 00:00:00 2001 From: Ikko Eltociear Ashimine Date: Tue, 17 Sep 2024 23:02:19 +0900 Subject: [PATCH] docs: update README.md arguements -> arguments --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d56d3477..59df98a6 100644 --- a/README.md +++ b/README.md @@ -63,7 +63,7 @@ Right now protonfixes packages a folder of 'gamefixes' however it could likely b ### What is the basic plan of putting this into action? 1. We build a database containing various game titles, their IDs from different stores, and their correlating umu ID. -2. Various launchers then search the database to pull the umu ID, and feed it as the game ID to `umu-run` alongside the store type, Proton version, wine prefix, game executable, and launch arguements. +2. Various launchers then search the database to pull the umu ID, and feed it as the game ID to `umu-run` alongside the store type, Proton version, wine prefix, game executable, and launch arguments. 3. When the game gets launched from `umu-run`, protonfixes picks up the store type and umu ID and finds the appropriate fix script for it, then applies it before running the game. 4. protonfixes has folders separated for each store type. The umu ID for a game remains the exact same across multiple stores, the only difference being it can have store specific scripts OR it can just symlink to another existing script that already has the fixes it needs.