Skip to content

games.yaml: a relative mod_path is used verbatim, never joined to install_path #313

Description

@dyoung522

Surfaced while building the Unit R (#305) review's twin-binary fixture: mod_path from games.yaml is used verbatim everywhere; a relative value is resolved against the process CWD, not install_path. Identical on base and head (pre-existing).

Decide one of: (a) normalise — join a relative mod_path to install_path at load time (and document it); (b) reject — validate on load / lmm game add / lmm game detect and refuse relative values with a clear error. Either way lmm game detect must never write a relative mod_path. Check whether any code path today can produce one; if none can, (b) is the cheaper insurance.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions