BlastBlastBlast

Blast any webpage to pieces! Fire a cannon, shoot soldiers, watch elements explode with real physics. Pure chaos, pure fun.

🔥 BlastBlastBlast — Turn any webpage into your personal demolition zone! Install it. Open any website. Click the extension. Watch the chaos begin. A fully armed tank cannon drops onto the bottom of ANY webpage. You aim, you drag, you fire — and everything EXPLODES. Text flies apart letter by letter. Images shatter into fragments. Buttons spin through the air. The physics are real. 🎮 TWO WEAPONS: • 💣 CANNON MODE — Drag from the tank to aim, set the power, release to fire. The cannonball arcs through the air in slow motion and lands EXACTLY where you aimed. Boom. • 🔫 GUN MODE — Switch to the pistol, move your crosshair, and click to rapid-fire straight tracer bullets. Multiple shots, real ballistics. 🪖 TOWER DEFENSE MINI-GAME: Soldiers raid your webpage from the top and sides! They walk in, steal buttons, icons, images, and text — and run away with them. Shoot them with the cannon or the gun before they escape. Blood drops, ragdoll deaths, helmet flying off — all included. 💥 WHAT EXPLODES: • Every single character of text flies away individually • Images shatter into real fragments • Buttons, icons, SVGs — all flung into the air • Blast marks stay permanently on the page until you leave • Craters, shockwaves, fire particles, smoke 🏆 SCOREBOARD: Kill soldiers → earn points → beat your best score → score is saved to your browser. 🎯 HOW TO PLAY: 1. Open any normal website (works on news, blogs, docs, GitHub, YouTube, anywhere) 2. Click the BlastBlastBlast extension icon 3. Click "Launch Cannon" 4. In CANNON mode: click the tank and drag to aim, then release 5. Switch to GUN mode (top right button): click anywhere to fire 6. Press Escape or click "Remove Cannon" to restore the page ✅ 100% private — no data collected, no network calls, no tracking. Runs entirely in your browser. ✅ Page is fully restored when you close the cannon or refresh. Works on virtually any website. Does not work on Chrome's own pages (chrome://...) or the Chrome Web Store — that's a Chrome security rule, not a bug.