Hydra Launcher

To build Hydra Launcher from source, you must satisfy the following environment requirements:

• Node.js & Yarn: For the core application logic and frontend.
• Python 3.9+: Required for the RPC layer. Install dependencies using pip install -r requirements.txt.
• Rust toolchain: Required for the hydra-native component.

Automatic Builds

• The postinstall script automatically builds the Rust native addon (hydra-native/hydra-native.node).
• Packaging scripts automatically trigger the Python RPC build.

# Install Python dependencies
pip install -r requirements.txt

# Build for specific platforms
yarn build:win
yarn build:mac
yarn build:linux
yarn build:unpack

When an imageUrl is not provided for a BigPictureToastCard, the fallbackVisual prop determines which icon is rendered in the media section:

• 'settings': Renders a GearIcon.
• 'downloads': Renders a DownloadSimpleIcon.
• Default (or any other value): Renders the Hydra brand icon.

When providing a list of discs to the DiscSelectionModal, the component automatically sorts them using the following priority:

1. Region Order: Discs are grouped by their SKU region (e.g., US, EU, JP, KR, ASIA). The order of regions is determined by their appearance in the provided discs array.
2. Label Numbering: Within the same region, discs are sorted numerically based on the first integer found in their label string (e.g., "Disc 1" comes before "Disc 2").

If a disc has no SKU/region, it is placed at the end of the list.

When interacting with the RPC, ensure your data adheres to these validation rules:

• Magnet URIs: Must start with magnet:, be under 8192 characters, and contain a valid xt parameter with a urn:btih: prefix followed by a 40-character hex or 32-character Base32 hash.
• Trackers: Must be a list of strings. Each string must be a valid URL with a scheme from the following set: http, https, udp, ws, wss.

The Python RPC entrypoint accepts arguments via command line to configure the torrent port, RPC password, and initial download/seeding payloads. It supports three distinct argument formats:

1. Legacy format (6 arguments): [script, torrent_port, http_port, rpc_password, initial_download, initial_seeding]
2. Stdio format with RPC password (5 arguments): [script, torrent_port, rpc_password, initial_download, initial_seeding]
3. Backward-compatible stdio format (4 arguments, no password): [script, torrent_port, initial_download, initial_seeding]

Communication occurs via stdin (receiving JSON requests) and stdout (sending JSON responses).

# Example using the Stdio format with RPC password
python python_rpc/main.py 6881 my_secret_password '{"game_id": 1}' '[]'

The main configuration block defines settings for the Electron main process. It includes source mapping for debugging and path aliases to simplify imports.

Path Aliases:

• @main: src/main
• @locales: src/locales
• @resources: resources
• @shared: src/shared

Plugins:

• externalizeDepsPlugin(): Used to externalize dependencies.
• swcPlugin(): Used for fast compilation via SWC.

main: {
  build: {
    sourcemap: true,
  },
  resolve: {
    alias: {
      "@main": resolve("src/main"),
      "@locales": resolve("src/locales"),
      "@resources": resolve("resources"),
      "@shared": resolve("src/shared"),
    },
  },
  plugins: [externalizeDepsPlugin(), swcPlugin()],
}

The preload configuration block manages the Electron preload scripts. Currently, it utilizes the externalizeDepsPlugin() to ensure dependencies are handled correctly in the preload context.

preload: {
  plugins: [externalizeDepsPlugin()],
}