SYSTEM STATUS: IN DEVELOPMENT
Let your code
do the fighting.
Build a combat vehicle. Program its instincts.
Then let it loose in the arena.
A retro programming game where every move is yours to write — and every battle is a chance to write it better.
if contact and missiles.ready():
missiles.aim(contact.bearing)
if on_target:
missiles.fire()No joysticks. No reflexes.
Just your machine, and your thinking.
THE LOOP
Build. Code. Battle.
Get a little smarter.
Your vehicle fights on its own. Your job is to give it a plan — then figure out how to make that plan better.
Build your machine.
Fit radar, a missile launcher, a drive and an optional shield. Work within a shared build budget. Speed, firepower, defence: every choice has a cost.
HARDWARE IS A STRATEGYWrite its instincts.
Start with a working program. Change a few lines in the game's own scripting language, BCAS. Tell your vehicle how to search, move, aim and fire.
A SMALL LANGUAGE. BIG IDEAS.Learn from the fight.
Watch autonomous battles. Pause, step through the replay and inspect the timeline. Find the missed shot or wasted energy. Change your code. Run it again.
EVERY REPLAY IS A CLUEFROM THE CURRENT BUILD
A little retro.
A lot to figure out.
Phosphor green. Tracked vehicles. Radar sweeps. A whole workshop of tools to turn a good idea into a better fighter.
See what your code actually did.
Pause the action, step through a tick at a time, and follow either vehicle. Radar overlays and recorded program memory help you understand the decisions behind the battle.
A few lines. A different fighter.
Start with a working vehicle program. Edit in BCAS, with autocomplete, line-by-line errors, undo and a built-in command reference. The equipment you fit determines the libraries you can use.
Build a machine with a plan.
Choose your equipment within the build-point and mass limits. Save different vehicles, copy a promising design and experiment with its hardware. Export and import vehicle packages to share your work.
Find the moment it went wrong.
Read the result and the facts behind it. Follow hits, misses, rejected commands and your own debug messages in the event timeline, then jump straight to that moment in the replay.
Which version comes out on top?
Run a local round-robin between saved vehicles and training opponents. Each pairing fights with swapped starts on the same seed. Compare standings, then watch any battle again.
THE INTERESTING PART
The best upgrade
might be a better idea.
A faster drive draws more power. A rapid launcher builds more heat. A shield spends energy you might need for your next shot. Your hardware and your program have to work together.
And your opponent's position isn't handed to you. You only know what your radar finds. Search intelligently. Turn the turret. Pick your moment.
MEET THE TRAINING OPPONENTS
Sentry
A stationary shooter. Find your feet, find your target.
Hunter
An aggressive chaser. Give your code a moving problem.
Evader
An evasive fighter. Getting a shot away is only the start.
Or battle your own saved vehicles — and find out whether your latest idea beats your last one.
BUILDING THE FIRST VERSION
The arena is
taking shape.
Battle Code Arena is in early development for Android and iOS. The first playable build focuses on local, single-player battles, replay tools and tournaments between saved vehicles and training opponents.
Interested in playtesting, or have a question about the game? We'd like to hear from you.
Get in touch support@inuvera.comThe core loop is playable.
Vehicle building, a BCAS editor, autonomous battles, detailed replays and local round-robin tournaments.
More testing. More refinement.
Real-device playtesting, balance and preparing the apps for their first store release.
A bigger arena.
More equipment and chassis, and asynchronous online competition are part of the longer-term concept.
Not yet available on the app stores. Screenshots show an early build; features and appearance may change.