16 lines
1.4 KiB
Markdown
16 lines
1.4 KiB
Markdown
# Project Notes
|
|
|
|
- AYN Thor main display: 6-inch AMOLED, 1920 x 1080, 120Hz.
|
|
- AYN Thor secondary display: 3.92-inch AMOLED, 1240 x 1080, 60Hz.
|
|
- AYN Thor UI sizing must be designed against Android CSS/layout viewport, not physical framebuffer pixels.
|
|
- Approximate Thor CSS viewports: main display 960 x 540, secondary display 620 x 540.
|
|
- Test top-screen UI only against the main display viewport, and bottom-screen UI only against the secondary display viewport.
|
|
- User rebuilds app; do not rebuild APK unless explicitly requested.
|
|
- Separate admin model viewer app runs at http://127.0.0.1:4174/admin.html.
|
|
- Apply game changes to both web version and mobile app version.
|
|
- Keep gameplay systems modular and reusable. Do not fork core combat rules per game mode.
|
|
- Shared systems own spells, mana/resources, cooldowns, casts, buffs, boss phases, telegraphs, boss mechanics, mobs, and mob mechanics.
|
|
- Shared rendering systems own 3D combat visuals: character meshes, weapons, attack animations, projectiles, telegraphs, hit/heal/stun effects, and boss/mob models.
|
|
- Game modes should compose/configure shared systems as adapters, for example Dungeon = one party vs encounter and PVP Roguelike = two party-vs-encounter lanes.
|
|
- If a new mode needs changed behavior, add configuration or extension points to shared combat/render modules instead of duplicating spell, resource, enemy, mechanic, mesh, weapon, animation, projectile, or effect logic.
|