R2NorthstarTools / R2NorthstarTools/FlightCore
Roadmap
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
- General
- Icon
- CI builds
- Self updating
- ensure version sync with tauri.conf.json, cargo.toml
- CI release
- some scripts to create release JSON file
- Self detect if outdated
- Self update delivery
- CI/CD
- Option to disable self-update (for Flatpak and Chocolatey)
- #97
- Chocolatey (maybe?)
- Display current version in UI window
- Crash report uploading (sentry.io)
- Show own version number somewhere in application
- Link main webpage as well as Wiki and Discord in main UI
- Northstar install/launch support
- 1-click to get to running Northstar
- Detect game install path
- Steam
- Origin
- EA App (check if install path is program files and throw warnings)
- Handle read-only filesystem
- Check if Northstar install is up-to-date
- 1-click updating Northstar
- Support for multiple release channels (Thunderstore)
- #93
- Read-out current version from
- #579
- mods
- #200
- Mod support
- Install mods via Thunderstore
- Uninstall/delete mods
- Show ns mod version (#159)
- Show ns mod folder name
- Prevent toggling (disabling) Northstar mods
- exception for dev mode
- ThunderstoreView
- Initial implementation
- Query Thunderstore API from backend (instead of frontend)
https://github.com/R2NorthstarTools/FlightCore/pull/168 - Show tags
- Show warning for server-side only mod (generally don't want to install that on client)
- Sorting
- Some way of "exploring"
- Button to open Thunderstore (the main page not just for the mod)
- Handle enabling/disabling mods (via
enabledmods.json)- General support
- Handle edge cases where
enabledmods.jsonmight be missing (e.g. fresh install) - Handle edge cases where mod might be missing from
enabledmods.json(manually installed before game launch)
- Check mod validity
- Mod update detection
- Install the dependency of a mod specified in it's manifest instead of newest (maybe we already do that?)
- #123
- Game repair functionality
- Force reinstall Northstar
- Button to disable all mods except core Northstar mods
- Generate "system report" (OS, Titanfall2 install location, FlightCore version, etc)
- Check filesystem permissions (we wanna look for admin owned files etc)
- Northstar crash detection
- CloudFlare blocking debugger (in particular make sure to check IPv4)
- Check Windows firewall rules
- calling
dxdiagand having an easy way of storing results somewhere so that they can be uploaded to tickets
- Accessibility:
- #172
- Papercuts
- #4
- Do not show "Unknown version" when Northstar not installed but "Not installed"
- #284
- Try to launch Origin if not running instead of only showing error message
- #12
- Move scrollbar away from edge (clicking scroll sometimes hits resize as well, makes things go wonky)
- Do not open PowerShell window on update (suggested by @uniboi, requires investigating possibility in framework)
- Do create new Desktop icon on update (suggested by @uniboi, requires investigating possibility in framework)
- Paginated loading for ThunderstoreView to speed up initial load time
- Extra
- #147
- Toggling mod enabled should also toggle mods enabled that it depends on
- Click icon in ModsView to open mod folder in explorer
- Dev tools
- "dev mode"
- Launch Northstar without update checks
- Launch Northstar without checking for Origin
- #139
- Dark mode
- Show list of Northstar (org) contributors and GitHub profile pics in some about menu, similarly to how it's done for releases
- Support multiple profiles
- get list of installed mods and export as TXT
- support r2mm links
- Open common config files
- Linux specific
- #383
- Proton install from PlayView
- Read output of
ldd --versionto determine use of nsproton (should be>=2.33) (#10)
- Add some easter egg (e.g. pressing
N5 times displays hidden nessie maybe?) - Generate and upload log file on panic to Sentry
- Bring back maximise button
- Security
- Ensure when loading mod title, description etc from Thunderstore to escape HTML tags
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
This is a broad roadmap rather than a single implementation task; review the unchecked items and their linked issues, starting with the relevant UI areas such as ThunderstoreView, ModsView, and PlayView. Use tauri.conf.json and cargo.toml for application configuration, then choose one item with a defined scope and verify completion against its specific behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, tauri
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100