CubeCrasher FAQ

The objective of CubeCrasher is to swipe or click on cascading 3D cubes to destroy them before they pass the bottom boundary of the screen. Slicing blocks awards points, and letting target blocks pass the boundary in Ranked Mode results in a Game Over. In Casual Mode, letting blocks drop reduces your score by 25 points instead.

Destroying blue wireframe blocks charges the slow-motion gauge. Once charged, the game speed slows down temporarily. This allows you to plan your moves and clear dense clusters of blocks more easily.

Pink blocks are high-durability targets that require 3 hits to destroy. Slicing them awards points for each hit, and destroying them completely yields denser fragment particles and higher bonus points.

CubeCrasher is built using vanilla JavaScript and HTML5 Canvas, making it compatible with any modern web browser. Supported browsers include Google Chrome (v80+), Mozilla Firefox (v75+), Apple Safari (v13+), Microsoft Edge (v80+), and Opera. No external plugins, WebGL support, or WebAssembly downloads are required to run the game.

The game achieves high frame rates by using an entity pooling pattern for blocks, fragments, and particle effects. This avoids the memory allocation overhead of creating new objects, reducing garbage collection pauses to near zero. We also optimize our 3D mesh rendering by sharing vertices between adjacent faces, reducing transformation calculations.

Your high scores and local leaderboard standings are stored directly on your device using the browser's Local Storage API. The game runs entirely on the client side, meaning no gameplay statistics or personal data are sent to external servers, protecting your privacy.

Yes, CubeCrasher is fully responsive and supports mobile devices. The game uses pointer events to handle touch inputs, ensuring low latency on smartphones and tablets. It also uses passive event listeners to prevent default browser behaviors like scrolling during gameplay.

The gameplay mechanics, physics, block health settings, and scoring criteria are identical on all devices. Touch sensitivity is scaled based on screen resolution to ensure a consistent experience across desktop and mobile screens.