R2NorthstarTools / R2NorthstarTools/FlightCore
Cannot switch back to default profile if Northstar wasn't installed
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 94
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
To reproduce
- Select a valid Titanfall2 install (easiest is to fake one with just
touch Titanfall2.exein some directory) - Manually create a new profile in there (e.g.
mkdir --parents my-profile/mods) - Select that Titanfall2 "install" in FlightCore
- Switch profile to
my-profile - You can no longer switch back to
R2Northstar
Easiest solution would be to always consider have R2Northstar in the return of fetching profiles and always have R2Northstar be considered a valid profile.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the profile-fetching and profile-validation paths involved when FlightCore selects a Titanfall2 install and switches profiles. Reproduce the sequence with a manually created my-profile and no installed Northstar profile. Done means switching back to R2Northstar succeeds even when Northstar was not previously installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100