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 current system of redirects works well if only the portion of a game path before the game itself varies across installs. For instance, if a path is /home/dane/game-foo/saves on one machine and /home/deck/game-foo/saves on another, redirects can easily handle that.
However, redirects do not help if a portion of the path after the game directory varies. For instance, Wine may create paths like this on two machines:
/home/dane/game-foo/drive_c/users/dane/saves
/home/deck/game-foo/drive_c/users/deck/saves
The only way to accommodate this today would be to have a separate redirect for every game / wine prefix.
A better solution might be for redirects to support regexes with capture groups as described here: #194 (comment)
The text was updated successfully, but these errors were encountered:
What's your idea?
The current system of redirects works well if only the portion of a game path before the game itself varies across installs. For instance, if a path is
/home/dane/game-foo/saves
on one machine and/home/deck/game-foo/saves
on another, redirects can easily handle that.However, redirects do not help if a portion of the path after the game directory varies. For instance, Wine may create paths like this on two machines:
/home/dane/game-foo/drive_c/users/dane/saves
/home/deck/game-foo/drive_c/users/deck/saves
The only way to accommodate this today would be to have a separate redirect for every game / wine prefix.
A better solution might be for redirects to support regexes with capture groups as described here: #194 (comment)
The text was updated successfully, but these errors were encountered: