At present, gib attempts to work directly with Steam to automate adding Steam shortcuts, setting launch options, etc.
This is all very useful, but when gib fails to work with Steam correctly (typically due to a parsing issue when handling Steam client data), the user is kind of stuck until I update gib to fix whatever specific issue they encountered.
This does tend to mean I am making gib more robust by finding these failures and addressing - but only when a user actually reports the issue. Many users just give up if something doesn't work.
As such, it's probably a wise idea to add support back for how gib used to operate, i.e. expecting the user to add Steam shortcuts, edit Steam launch options, and testing BepInEx is working manually, guiding them through the process.
At present, gib attempts to work directly with Steam to automate adding Steam shortcuts, setting launch options, etc.
This is all very useful, but when gib fails to work with Steam correctly (typically due to a parsing issue when handling Steam client data), the user is kind of stuck until I update gib to fix whatever specific issue they encountered.
This does tend to mean I am making gib more robust by finding these failures and addressing - but only when a user actually reports the issue. Many users just give up if something doesn't work.
As such, it's probably a wise idea to add support back for how gib used to operate, i.e. expecting the user to add Steam shortcuts, edit Steam launch options, and testing BepInEx is working manually, guiding them through the process.