Astray in browser

Game files

No own files requested before Level 1

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-16)

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

Level 1 loaded and a short Up-key input visibly moved through the opening passage. Other directions, exits, saving and mobile remain unverified; no sign-in appeared before that response.

Project type: Native browser game

wwwtyro's original repository and linked demo identify a WebGL maze using Three.js and Box2dWeb. This is the original browser project, separate from Astray 2.

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

This Astray browser guide covers wwwtyro's original maze, reached from the author's repository rather than another site's mirror. The linked demo opened directly to Level 1, with a lit ball, brick walls and a small instruction hint. A short Up-key input visibly changed the ball's position relative to the passage while the camera followed. We did not reach the maze exit. That makes this a verified opening scene and limited movement check, not a solved-level walkthrough or a comparison of every game called Astray.

The visit and source review are dated October 16, 2026. The original repository names Three.js and Box2dWeb as its main rendering and physics libraries. We use that source to identify the browser project, not to infer a guaranteed frame rate or precise physical behavior from a brief input. The screenshot is the actual Level 1 view after movement. It includes the source ribbon's visibly missing image because that decorative issue occurred during the same visit; it was not removed to make the scene appear more complete.

Guide published 2026-10-16. Source reviewed 2026-10-16. Author release-page publication: Not established. The reviewed original repository did not establish the first publication day of its browser demo.

Game files

The original demo entered Level 1 without a ROM, archive, upload button or request for commercial game data. The ball, walls and floor textures loaded from the web. We did not inspect a cache, disconnect the network or export files, so this does not establish offline support or a transfer budget. The file condition applies to the demonstrated browser entry. The repository's developer instructions for running a local copy are a different route and were not followed. Visitors do not need to interpret those development commands as part of the checked online path or install the project's libraries to reproduce our opening-scene observation.

Controls

The scene showed an instruction hint referring to the I key. We held Up for approximately 650 milliseconds and compared the visible maze before and after: the surrounding walls shifted relative to the ball as the view followed its movement through the opening passage. That response supports a keyboard category, but it is not a complete directional-control test. Other arrows, the source's alternative keys and the instruction overlay were not separately exercised. We did not measure speed or acceleration. Short inputs are useful when checking a confined passage because an unchanged position against a wall can otherwise be mistaken for a dead keyboard.

Account

The original page did not ask for an account, player name, password, payment or email before displaying the maze and responding to Up. We created no profile and submitted no score. This is an entry observation, not an audit of everything linked from the repository or any later service a visitor might open. A visible level label is game state, not proof of an account or persistent progress. Similarly, the directory's saved-project control bookmarks this page only; it was not used to store a maze, retain a level or recover a previous run.

Mobile gameplay

Not tested. The checked route used a desktop keyboard. We did not establish touch steering, a phone layout, external keyboard behavior on a tablet or orientation handling. A WebGL scene rendering in one desktop environment does not prove it will initialize on every phone or browser. The site guide can fit a narrow screen without the external game becoming touch-playable. No device recommendations, minimum graphics-memory figures or battery claims are inferred from this short visit. The original instruction hint should be treated as a keyboard-oriented starting point, not a substitute for a mobile test.

Full session

We stopped inside Level 1 after the single short movement. An exit, transition, higher-level layout and completed run were not verified. No restart, save, reload recovery or extended stability check was performed. The camera-follow behavior made movement visible even though the ball stayed near the middle of the screen; judging only the ball's absolute screen coordinate would miss that response. Our screenshot records the nearby passage at the stop point, not a complete map or the shortest path out. The generated arrangement and the visitor's own later route may differ, so this guide does not give a sequence of turns that it has not actually completed.

HTTP link check

An independent HTTPS request to https://wwwtyro.github.io/Astray/ returned HTTP 200 with zero redirects on October 16, 2026. Keep the capital A in the documented project path rather than assuming a different URL is equivalent. Certificate validation remained enabled. The document response and rendered maze are distinct observations: a healthy HTML response alone would not prove WebGL or its textures initialized. In our browser the game textures did render while the separate GitHub corner-ribbon image did not. That limited missing decoration is recorded without calling the entire game unavailable or claiming every resource was healthy.

The source link identifies wwwtyro/Astray. The separately named Astray 2 project is not covered by this visit. Our scene was a lit ball in a maze with a following camera; we did not observe mouse-look shooting, a character inventory or a console-emulation interface. Do not transfer controls, release dates, performance claims or screenshots from similarly named projects. This page's project category describes the original browser game. It does not claim that the source libraries are the newest available releases or that we audited the implementation. The source publication day remains unknown rather than borrowing a date from a directory listing.