ACTION / BROWSER PROJECT

OpenTyrian in browser

pelya's OpenTyrian browser port reached the first Tyrian level and responded to rightward ship movement. It requested no own files on this path; weapon bindings, completed episodes, saves and mobile remain unverified.

pelya.github.io

Desktop checkFirst-level movement checked
Actual OpenTyrian first-level scene with the player ship, scrolling terrain and weapon and shield panels
Actual Tyrian level after a short Right input. Ship movement was checked; visible shots were already present before that input and do not establish a tested fire binding, completed level or recovered save.

At a glance

Game files
No own files requested before the first level
Controls
Keyboard controls
Account
No sign-in in checked entry
Mobile gameplay
Not tested
Full session
Not tested
HTTP link check
HTTP 200; 0 redirects (2026-10-21)

Basis: project instructions and limited desktop entry observation. Observations: Oct 21, 2026. Conditions organized: October 21, 2026.

Return and Down reached the first Tyrian level, where Right moved the ship. No own files or sign-in preceded it. Shots were already visible before movement; Space firing, completion, saves and mobile were not verified.

Source & instructions (opens in a new tab)

Project type: Browser port

pelya's repository identifies an Emscripten/asm.js OpenTyrian port of DOS Tyrian. The maintainer's upstream issue links this exact browser demo. No own files were requested before the checked first level.

Classification organized October 21, 2026 from the recorded source and check notes; not a new gameplay test.

Compare classic browser ports

Before you open it

Getting started

  1. Allow the splash to finish, then use Return through the single-player, episode and difficulty selections. We kept the default selections unchanged.
  2. In Game Menu, choose Play Next Level, then Tyrian. The first return from the menu is not yet the scrolling scene.
  3. Our short Right input moved the ship in the level. We stopped without testing fire bindings, upgrades, later episodes, saving or phone input.

What we checked

On October 21, 2026, the maintainer-linked demo passed its splash and main menu. Return selections reached 1 Player Full Game, Episode 1: Escape, the unchanged difficulty selection and Game Menu. Down and Return selected Play Next Level, followed by Tyrian. The scrolling level displayed a ship and shots before our movement input. Holding Right for 200 milliseconds moved the ship from near the center to the right. We did not press Space to establish firing, change weapon mode, buy upgrades, use multiplayer, finish a level or recover a save. No own-file, registration or payment step preceded this path; mobile was not tested.

Desktop browser · Oct 21, 2026

The repository identifies an OpenTyrian fork using Emscripten and asm.js; a KaiOS project name does not verify touch play. The maintainer's April 24, 2021 upstream post links this exact demo, but is not an established launch date for the current build. This directory hosts notes and its own screenshot, not a game-data archive or an alternative playable copy.

Current instructions on the original project (opens in a new tab)

Independent editorial pick; not attributed to Radiant Optimizer.

Which OpenTyrian project?

This OpenTyrian browser guide covers pelya's opentyrian-kaios demo, rather than treating every web build with the same game name as interchangeable. The maintainer linked this exact destination in the upstream project's issue 24. Our desktop visit passed the splash, selected a single-player full-game path and entered the first Tyrian level. A short Right input shifted the ship across the scrolling terrain. That is a concrete movement observation, distinct from simply reaching a title or reading a control list. We did not inspect another maintainer's build or install the separate KaiOS package.

Source review and the browser check are dated October 21, 2026. The source identifies a DOS-game port compiled for the browser, including asm.js context; we do not silently rename this build a newly released WebAssembly edition. During our opening scene, shots were already visible before the explicit movement test. We therefore describe the ship's rightward response without claiming a separate fire-key test. The screenshot shows a real level rather than a menu poster or an image from another port. No completed mission, campaign, recovered save or mobile session is implied.

Guide published . Source reviewed . Author release-page publication: Not established. The maintainer's April 24, 2021 upstream post identifies this demo, but does not establish the first-publication day of the current deployment.

pelya's OpenTyrian source, keyboard controls and KaiOS build notes (opens in a new tab)

Six conditions for OpenTyrian in browser

Game files

The hosted demo did not ask us to choose a local folder, upload an archive, supply a disc image or locate a ROM before the first level. It loaded its own resources over the network. The repository's separate native-build data instructions do not mean that our browser path contained an upload step. Conversely, the absence of that prompt does not establish an offline edition, a complete resource inventory or permission to redistribute a package. This guide links the maintainer's host and records its own check image; it does not provide a data download, executable installation, replacement server or mirrored game.

Controls

Return selections reached the player, episode and difficulty menus, followed by Game Menu. Down and Return were used to choose Play Next Level, then Tyrian. Once the scrolling scene appeared, a 200-millisecond Right hold moved the ship from near the center toward the right side. The source also documents arrows for movement, Space for firing, Enter for rear-weapon mode and Ctrl or Alt for sidekicks. Those additional bindings were not exercised. Visible projectiles preceded our Right test, so they cannot prove that we pressed or verified Space. Menu navigation and gameplay movement are recorded as separate responses.

Account

No email address, account, name submission, registration or payment appeared before the single-player level and rightward movement. The menu also offered other modes, but we did not use a network game, connect to another player or change a server setting. A fictional in-game balance and upgrade option were visible in Game Menu; we did not enter the shop or purchase an upgrade. This limited account observation does not establish the requirements of every alternative build or service. Bookmarking this guide in the directory is unrelated to the external ship state, game balance, campaign progress or any player identity.

Mobile gameplay

Not tested. The repository name and its KaiOS instructions identify a development target, not a verified phone session in this visit. We used a desktop browser and physical-key events, not a touch surface, mobile keypad or store package. We did not rotate a device, install an app, compare memory limits or exercise simultaneous touch movement and firing. A guide that remains readable at phone width is not proof that the external game supports that input. The source's device-specific build and audio notes should therefore remain historical implementation context rather than promises about a visitor's present mobile browser.

Full session

The check entered an actual scrolling first level and moved the ship, but did not finish that level or an episode. The first menu transition led to a level-selection screen before the scene itself, which matters when describing how far a visit reached. We left the difficulty selection unchanged and did not compare modes or establish a preferred difficulty. Shots, changing terrain and HUD counters were visible, but we did not isolate damage, a defeated boss, an upgrade effect or a later unlock. No save was exported, imported or recovered after a restart, so sustained progression and persistence remain unverified.

HTTP link check

A separate HTTPS request to pelya.github.io/opentyrian-kaios/ returned HTTP 200 with zero redirects on October 21, 2026. Certificate validation stayed enabled. The upstream issue supplies a maintainer-authored link to this exact destination, while the repository supplies implementation and control context. That document response is not a gameplay result by itself; the later level and ship movement provide separate evidence. It also does not validate every optional mode, future resource request or another OpenTyrian deployment. No certificate warning was bypassed and no game state was changed through injected code to create the observed movement.

From Game Menu to the first Tyrian level

The checked route has more than one confirmation screen. Selecting the single-player path and the first episode eventually reached Game Menu, not immediate scrolling play. Choosing Play Next Level then showed Tyrian and Exit to Game Menu; selecting Tyrian reached the terrain and ship. This sequence is useful when comparing an apparent loading pause with a menu that still expects a selection. Our visit does not establish every timing condition or diagnose a different visitor's black screen. Keep the exact maintainer and destination attached to any report, because another web port may have different menus, bundled resources or input behavior. The April 2021 upstream post is source provenance, not a current release announcement. We did not follow its separate multiplayer instructions, use command-line networking or infer that a visible mode works in this browser. The narrow verified result remains entry into the first scene and responsive rightward movement.

GOOD TO KNOW

OpenTyrian browser FAQ

Which OpenTyrian browser port was checked?

pelya's opentyrian-kaios demo, linked by the maintainer in upstream issue 24. Other web builds and the KaiOS package were not checked.

Does this browser entry require my own game files?

No own-file prompt appeared before the first level in our visit. The online demo loaded its resources itself; this is not an offline or redistribution promise.

How did you reach the scrolling level?

The single-player, episode and difficulty selections led to Game Menu. Play Next Level then Tyrian reached the first scrolling scene.

Were movement and firing both tested?

Rightward movement was confirmed. Shots were already visible before that input, and Space, rear-weapon mode and sidekick bindings were not independently tested.

Were complete episodes, saves, multiplayer or mobile verified?

No. We did not complete a level, recover a save, connect another player or test a phone. The KaiOS name alone does not verify mobile gameplay.