Mad Camel Studio game in development
.panic
One tap. One chance. but remember do't panic! At a glance it is one dot and one target. In your hand it becomes a tiny argument with timing, nerves, and the run you almost saved.
Visual direction
Black field. Sharp color. No place to hide.
The game should read in one second: where the dot is, where it has to be, what the last tap did, and whether the next mistake is yours. The UI stays lean because hesitation is already loud enough.
The crossing
The whole run narrows into one pass-through moment. Too early is a mistake. Too late is also a mistake. Useful design, frankly.
Risk choice
The game offers a bad idea with a button on it. Take the roll, skip the roll, then blame the next timing window like everyone else.
Same-seed result
The run leaves evidence: score, nickname, seed, and code. Enough to say "your turn" without pretending this is realtime multiplayer.
Gameplay shape
A simple rule that gets personal fast.
.panic is built around the kind of mistake you can feel before the result appears. The target is visible, the timing is fair, and the miss is usually your fault. That is the useful pain.
Precision timing
The dot is tiny on purpose. The real opponent is the clock, and the game should never hide that behind screen-size tricks or lucky physics.
Risk Orbs
Risk Orbs add the dangerous little thought every arcade game needs: maybe this helps, maybe this ruins me, maybe I press it anyway.
Survival scoring
A good run is not long because it is padded. It is long because the player kept winning one small argument after another.
Name and tone
A calm name for a nervous little game.
.panic should feel like a tiny command with a pulse. The title is short, a little strange, and easy to remember right after missing by a few milliseconds.
Competition design
Same seed, same pressure, fair comparison.
The multiplayer feeling comes from shared pressure, not from a lobby. Give two players the same seed and the question is clean: same route, same rules, who stayed useful under pressure?
Challenge Code
A code turns a run into a dare. Send it, replay it, beat it, send it back with just enough smugness.
Daily, weekly, monthly
The calendar becomes a shared target: one daily, weekly, or monthly route, and a clean reason to try again tomorrow.
Replay and ghost
Replay is the run's input trail. It can become a ghost, a local memory, or the proof that the score actually happened.
Server authority
The public board should not believe a screenshot. Ranked scores are meant to be rebuilt and checked from the run itself.
Modes
Short sessions, repeatable pressure.
The modes should feel like different excuses to keep the same tension alive: a safer drill, a cleaner duel with timing, or a shared seed that refuses to let go.
Classic
The main score chase: Risk Orbs, rising speed, tightening windows, and the pleasant feeling that one more tap might fix everything.
Pure Skill
No Risk layer, no excuse layer. Just timing, pressure, and the scoreboard looking at you.
Practice and challenges
Practice lets the hands learn. Daily, Weekly, Monthly, and Challenge Code runs give that learning somewhere public to misbehave.
Release direction
Built around mobile-sized panic.
The public platform note stays simple for now: mobile. The game belongs close to the thumb, where the mistake is instant and personal.
Player promise
Competition should not be for sale.
The clean rule is that competition is earned, not bought. Cosmetics can make the game feel different, but they do not get to make the run easier.
No ads
No rewarded ads, no banners, no ad-removal purchase pretending to be generosity.
No currency economy
No coins, gems, energy meters, paid rolls, battle pass chores, or tiny store crumbs dressed up as progression.
No paid advantage
Paid content cannot buy slower speed, wider windows, better odds, score multipliers, ranked revives, or leaderboard power.
Readable ranked play
Cosmetics can change the mood. Ranked play still has to stay readable, visible, and fair when the tap matters.
.panic FAQ
What is public for now.
This page is a signal, not a store listing. Release dates, store links, final screenshots, and public leaderboard claims should wait until they are real.
What kind of game is .panic?
A compact timing arcade game about one moving dot, one visible target, and the exact moment your thumb becomes suspicious.
Is it multiplayer?
Not realtime multiplayer. The competitive feeling comes from shared seeds, Challenge Codes, same-run comparison, and verified boards.
Where is it planned to launch?
The current public direction is mobile. Store pages and release details can wait until there is something worth clicking.