cetteup / joinme.click-launcher Goto Github PK

Since we aren't using Origin App anymore, this tool should update to start using the EA App.

As mentioned in Discord, would be cool to have a protocol handler that just allows starting the game. Should also consider any configured config.yaml settings.

i.e. bf2://launch would just end up opening the game.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update golangci/golangci-lint-action action to v6
• chore(deps): update softprops/action-gh-release action to v2
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency golang to v1.19.13
• fix(deps): update module github.com/rs/zerolog to v1.29.1
• fix(deps): update module github.com/stretchr/testify to v1.8.4
• chore(deps): update dependency golang to v1.22.3
• fix(deps): update module github.com/cetteup/conman to v0.2.0
• fix(deps): update module github.com/rs/zerolog to v1.32.0
• fix(deps): update module github.com/stretchr/testify to v1.9.0
• fix(deps): update module golang.org/x/sys to v0.20.0
• chore(deps): update actions/cache action to v4
• chore(deps): update actions/checkout action to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

If the handler detects a game as not installed, it does not do anything else for the game. Meaning if the handler is currently registered to launch URLs for the no longer installed game, it does remove itself.

Currently, bf2sf://127.0.0.1:16567?mod=bfp2 is considered a valid URL that will cause the launcher to BF2.exe with these flags:

+joinServer 127.0.0.1 +port 16567 +playerName [...]+playerPassword [...] +modPath mods/bfp2 +ignoreAsserts 1 +menu 1 +restart 1 +modPath mods/xpack +ignoreAsserts 1

The game will use the later flags, so it will start Special Forces, not the pirates mod. Expected behaviour would be to throw an error regarding an unsupported mod. Alternatively, stop tracking expansion packs (which are technically mods) as separate games.

The 1.5/1.41 patch creates the xpack folder in mods, which is currently enough for the launcher to consider Special Forces to be installed. However, that folder only contains some patched files. You cannot actually start Special Forces.

Battlefield 2 current fails to launch if the Documents folder has been moved from it's default location.

Since only the documents if moved and not the entire user home dir, the path construction [homeDir]\Documents does not work in these cases.

• investigate whether different environment variable always points to currently configured documents folder
• if not, investigate lookup via registry HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders