Armored Flight

Explore

Games

A browser-based 3D flight-combat game with procedural Blender-generated assets.

bygisele gamache

PlayableOpen source

Armored Flight media is blocked

Allow external media to connect to the provider and play this content.

Description

A high-tech powered armor flight-combat game featuring a destructible city, drones, and boss battles. Built using a one-shot prompt in Claude Code, it features a sophisticated procedural pipeline generating 3D assets via Blender scripts, Rapier physics, and a diegetic HUD.

Descriptions, tags, and model credits may be AI-generated or inferred from public sources and can be incomplete or wrong. Learn more.

Details

Why this is interesting: An ambitious one-shot build featuring a complete 3D engine, custom physics, and a fully automated Blender asset…
Attributed to: gisele gamache@crocone
Built with: Sonnet 5.5
Links: coders.talk
View tweet
View GitHub repo
Tags: #flight-combat #threejs #blender #rapier

Discovered: X
First posted: X · Sep 29, 2026
Listed: Added yesterday
Build: Strong
Models: Strong

Prompts

Prompt 1

* player flying between buildings
* strong sense of speed and altitude
* visible hand and foot thrusters
* missiles crossing the battlefield
* enemy drones surrounding the player
* rooftop turrets
* destructible city props
* explosions, smoke, debris, sparks
* large boss encounter above the city
* readable diegetic-style HUD
* cinematic but performant lighting

Do not build this as a greybox.
Do not use placeholder geometry in the final game.
Do not use downloaded third-party 3D models.
Do not instruct the user to replace assets later.
Every required visual asset must actually exist and be generated as part of the repository.
Mandatory Technology
Use:

* Vite
* TypeScript
* Three.js
* `@dimforge/rapier3d-compat`
* Rapier WASM
* HTML/CSS for HUD
* Blender for all authored 3D assets

The game must run entirely client-side.
No server.
No backend.
No database.
No external runtime API.
After installation and asset generation, this must work:

```
npm install
npm run dev
```

Production build must work:

```
npm run build
```

Blender Asset Pipeline
Blender is installed on the machine.
Create Blender Python scripts using `bpy`.
Store them in:

```
/tools/blender/
```

Run them with commands such as:

```
blender -b -P tools/blender/build_player.py
```

Export all finished assets to:

```
/public/assets/
```

or another Vite-compatible static asset directory.
Use glTF / GLB.
Prefer `.glb`.
Create a master asset build script:

```
/tools/blender/build_all.py
```

or shell/npm equivalent so that all assets can be regenerated automatically.
For example:

```
npm run assets
```

The asset-generation pipeline must be deterministic and reproducible.
Do not manually create essential assets outside the scripts.
Art Direction
Use an original visual design.
Do not directly reproduce copyrighted characters or recognizable commercial armor designs.
Powered armor should have:

* angular low-poly / mid-poly plating
* strong humanoid silhouette
* metallic armor surfaces
* darker mechanical joints
* emissive cyan / blue-white reactor surfaces
* readable chest reactor
* palm repulsors
* foot thrusters
* shoulder weapon mounts

The result should visually communicate:
fast armored aerial combat over a city.
Use a coherent material palette across the project.
Do not make everything flat-shaded primitives.
Use bevels, weighted normals, inset panels, layered armor plates, mechanical joints, emissive strips, and silhouette variation where appropriate.
Keep geometry suitable for a browser game.
Player Armor
Create a complete powered armor model.
Required separate meshes:

```
PlayerRoot
├── Helmet
├── Torso
├── Arm_L
├── Arm_R
├── Forearm_L
├── Forearm_R
├── Hand_L
├── Hand_R
├── Leg_L
├── Leg_R
├── Boot_L
├── Boot_R
├── ChestReactor
├── PalmReactor_L
├── PalmReactor_R
├── FootThruster_L
└── FootThruster_R
```

Use emissive materials for reactors and thrusters.
Create three usable poses:

1. standing
2. flight
3. hover/combat

The game must visibly transition between flight/hover behaviour.
The player must not simply be represented by a capsule or box while rendered as an unrelated model.
Physics and visual orientation must match.
Enemies
Create original Blender-generated models for:
Drone
Aerial combat drone with:

* compact armored body
* visible propulsion system
* emissive sensor
* weapon ports
* readable forward direction

Ground Turret
Create:

* base
* rotating yaw assembly
* pitch/elevation weapon head
* missile launcher geometry
* emissive targeting sensor

Turret visual rotation must match its aiming logic.
Boss
Create a large armored aerial combat unit approximately:
2.5–3.5× the player's visual mass.
It must look substantially more dangerous than normal enemies.
Create:

* large armored torso
* heavy arms
* large thrusters
* weapon hardpoints
* emissive core
* separate shield sphere mesh

Shield must be rendered separately so it can:

* pulse
* flash when hit
* distort/fade when damaged
* disappear when broken

Projectile Assets
Create Blender-generated:
Missile
Include:

* body
* fins
* engine
* emissive exhaust region

Mini Missile
Smaller and visually distinct.
Both should have a clear forward axis.
City Kit
Build enough city geometry that the player can fly through an actual combat space.
Create at least:

* 8 building modules
* road module
* intersection
* sidewalk
* rooftop utility objects
* street lamp
* car
* barriers
* rooftop antenna

Buildings must vary in:

* height
* footprint
* rooftop shape
* facade structure
* s…

Source

Prompt 2

You are building a complete playable browser-based single-player 3D action game, not a prototype, tech demo, proof of concept, or collection of disconnected systems. Working title: Armored Flight. The game should feel like controlling a high-tech powered armor suit flying through a destructible modern city while fighting drones, missile turrets, and a giant armored boss. The visual target is a polished indie action game with the readability and spectacle of a third-person superhero flight combat game: * player flying between buildings * strong sense of speed and altitude * visible hand and foot thrusters * missiles crossing the battlefield * enemy drones surrounding the player * rooftop turrets * destructible city props * explosions, smoke, debris, sparks * large boss encounter above the city * readable diegetic-style HUD * cinematic but performant lighting Do not build this as a greybox. Do not use placeholder geometry in the final game. Do not use downloaded third-party 3D models. Do not instruct the user to replace assets later. Every required visual asset must actually exist and be generated as part of the repository. Mandatory Technology Use: * Vite * TypeScript * Three.js * @dimforge/rapier3d-compat * Rapier WASM * HTML/CSS for HUD * Blender for all authored 3D assets The game must run entirely client-side. No server. No backend. No database. No external runtime API. After installation and asset generation, this must work: npm install npm run dev Production build must work: npm run build Blender Asset Pipeline Blender is installed on the machine. Create Blender Python scripts using bpy. Store them in: /tools/blender/ Run them with commands such as: blender -b -P tools/blender/build_player.py Export all finished assets to: /public/assets/ or another Vite-compatible static asset directory. Use glTF / GLB. Prefer .glb. Create a master asset build script: /tools/blender/build_all.py or shell/npm equivalent so that all assets can be regenerated automatically. For example: npm run assets The asset-generation pipeline must be deterministic and reproducible. Do not manually create essential assets outside the scripts. Art Direction Use an original visual design. Do not directly reproduce copyrighted characters or recognizable commercial armor designs. Powered armor should have: * angular low-poly / mid-poly plating * strong humanoid silhouette * metallic armor surfaces * darker mechanical joints * emissive cyan / blue-white reactor surfaces * readable chest reactor * palm repulsors * foot thrusters * shoulder weapon mounts The result should visually communicate: fast armored aerial combat over a city. Use a coherent material palette across the project. Do not make everything flat-shaded primitives. Use bevels, weighted normals, inset panels, layered armor plates, mechanical joints, emissive strips, and silhouette variation where appropriate. Keep geometry suitable for a browser game. Player Armor Create a complete powered armor model. Required separate meshes: PlayerRoot ├── Helmet ├── Torso ├── Arm_L ├── Arm_R ├── Forearm_L ├── Forearm_R ├── Hand_L ├── Hand_R ├── Leg_L ├── Leg_R ├── Boot_L ├── Boot_R ├── ChestReactor ├── PalmReactor_L ├── PalmReactor_R ├── FootThruster_L └── FootThruster_R Use emissive materials for reactors and thrusters. Create three usable poses: 1. standing 2. flight 3. hover/combat The game must visibly transition between flight/hover behaviour. The player must not simply be represented by a capsule or box while rendered as an unrelated model. Physics and visual orientation must match. Enemies Create original Blender-generated models for: Drone Aerial combat drone with: * compact armored body * visible propulsion system * emissive sensor * weapon ports * readable forward direction Ground Turret Create: * base * rotating yaw assembly * pitch/elevation weapon head * missile launcher geometry * emissive targeting sensor Turret visual rotation must match its aiming logic. Boss Create a large armored aerial combat unit approximately: 2.5–3.5× the player's visual mass. It must look substantially more dangerous than normal enemies. Create: * large armored torso * heavy arms * large thrusters * weapon hardpoints * emissive core * separate shield sphere mesh Shield must be rendered separately so it can: * pulse * flash when hit * distort/fade when damaged * disappear when broken Projectile Assets Create Blender-generated: Missile Include: * body * fins * engine * emissive exhaust region Mini Missile Smaller and visually distinct. Both should have a clear forward axis. City Kit Build enough city geometry that the player can fly through an actual combat space. Create at least: * 8 building modules * road module * intersection * sidewalk * rooftop utility objects * street lamp * car * barriers * rooftop antenna Buildings must vary in: * height * footprint * rooftop shape * facade structure * silhouette Do not create eight differently scaled copies of the same cube. Generate a city layout large enou…

Source

Explore

Games

Armored Flight

A browser-based 3D flight-combat game with procedural Blender-generated assets.

bygisele gamache

PlayableOpen source

Armored Flight media is blocked

Allow external media to connect to the provider and play this content.

Description

Descriptions, tags, and model credits may be AI-generated or inferred from public sources and can be incomplete or wrong. Learn more.

Details

Why this is interesting: An ambitious one-shot build featuring a complete 3D engine, custom physics, and a fully automated Blender asset…
Attributed to: gisele gamache@crocone
Built with: Sonnet 5.5
Links: coders.talk
View tweet
View GitHub repo
Tags: #flight-combat #threejs #blender #rapier

Discovered: X
First posted: X · Sep 29, 2026
Listed: Added yesterday
Build: Strong
Models: Strong

Prompts

Prompt 1

* Vite
* TypeScript
* Three.js
* `@dimforge/rapier3d-compat`
* Rapier WASM
* HTML/CSS for HUD
* Blender for all authored 3D assets

The game must run entirely client-side.
No server.
No backend.
No database.
No external runtime API.
After installation and asset generation, this must work:

```
npm install
npm run dev
```

Production build must work:

```
npm run build
```

Blender Asset Pipeline
Blender is installed on the machine.
Create Blender Python scripts using `bpy`.
Store them in:

```
/tools/blender/
```

Run them with commands such as:

```
blender -b -P tools/blender/build_player.py
```

Export all finished assets to:

```
/public/assets/
```

or another Vite-compatible static asset directory.
Use glTF / GLB.
Prefer `.glb`.
Create a master asset build script:

```
/tools/blender/build_all.py
```

or shell/npm equivalent so that all assets can be regenerated automatically.
For example:

```
npm run assets
```

Use emissive materials for reactors and thrusters.
Create three usable poses:

1. standing
2. flight
3. hover/combat

* compact armored body
* visible propulsion system
* emissive sensor
* weapon ports
* readable forward direction

Ground Turret
Create:

* base
* rotating yaw assembly
* pitch/elevation weapon head
* missile launcher geometry
* emissive targeting sensor

* large armored torso
* heavy arms
* large thrusters
* weapon hardpoints
* emissive core
* separate shield sphere mesh

Shield must be rendered separately so it can:

* pulse
* flash when hit
* distort/fade when damaged
* disappear when broken

Projectile Assets
Create Blender-generated:
Missile
Include:

* body
* fins
* engine
* emissive exhaust region

Mini Missile
Smaller and visually distinct.
Both should have a clear forward axis.
City Kit
Build enough city geometry that the player can fly through an actual combat space.
Create at least:

* 8 building modules
* road module
* intersection
* sidewalk
* rooftop utility objects
* street lamp
* car
* barriers
* rooftop antenna

Buildings must vary in:

* height
* footprint
* rooftop shape
* facade structure
* s…

Source

Prompt 2

Source

Armored Flight

Description

How it grew

Armored Flight

Description

How it grew