Release v0.1.18 2026-07-19
This commit is contained in:
@@ -41,11 +41,16 @@ platform tools and a connected Thor, build and install it with:
|
||||
pnpm android:install
|
||||
```
|
||||
|
||||
The first Android milestone uses the complete single-display fallback. Press
|
||||
Select (or Tab with a keyboard) to switch between the main game surface and the
|
||||
620 × 540 tactical surface. Native routing to both physical Thor displays is the
|
||||
next milestone; it needs two Android display contexts backed by one shared game
|
||||
state rather than two independent WebViews.
|
||||
The Android host routes the main and tactical surfaces to separate physical
|
||||
Thor displays while preserving one authoritative game state. If only one
|
||||
display is available, Select (or Tab with a keyboard) opens the tactical surface
|
||||
over the main game view.
|
||||
|
||||
PC and handheld browsers use the Thor top screen as a responsive, full-viewport
|
||||
game surface. The compact ability strip keeps combat controls visible; Select
|
||||
or Tab opens party, map, inventory, and other tactical detail. Use
|
||||
`?layout=thor-preview` to restore the stacked dual-screen hardware mockup for
|
||||
browser QA.
|
||||
|
||||
## TrueNAS deployment
|
||||
|
||||
@@ -140,6 +145,7 @@ outside the repository.
|
||||
- `Q` and `E` / D-pad: cycle party target
|
||||
- `1`–`6`: cast Smite, Renew, Shield, Purify, Radiance, Flash Heal
|
||||
- Gamepad: PlayStation `□`, `△`, `○`, `✕`, `L1`, `R1` map to those abilities
|
||||
- `Select` / `Tab`: open or close the tactical interface on one-screen devices
|
||||
- `M`: tactical map
|
||||
- `I`: inventory and item tooltip
|
||||
- `Enter` / `START`: begin or reset encounter
|
||||
@@ -185,6 +191,6 @@ build. Remove the switch to return to modular rendering.
|
||||
- Android layout targets: approximately 960×540 CSS pixels top and 620×540 CSS pixels bottom
|
||||
- Lower-screen typography scales against its own container, never the main page viewport
|
||||
|
||||
Current Android build is an installable single-display test host. Shipping to both
|
||||
physical Thor displays still needs distinct Android display contexts that project
|
||||
one authoritative game state.
|
||||
The Android build uses distinct display contexts that project one authoritative
|
||||
game state across both physical Thor displays. PC and Steam Deck use the same top
|
||||
surface with an adaptive tactical overlay.
|
||||
|
||||
Reference in New Issue
Block a user