PRO GAMING COORDINATION CHALLENGE

Core Ball Game
Spatial Coordinate Precision

Shoot pins into the central rotating core. Avoid collisions over 130+ procedurally generated levels with alternating speeds, direction shifts, and stutter patterns.

🎯 VECTOR TIMING CONTROL
Sound ON
Level 1
Current Stage
0 / 0
Needles Shot
Constant
Rotation Style
0.13r
Collision Threshold
🔮

Procedural Core Rotation Challenge

Press **Spacebar, Enter, or Click the central core** to shoot pins. Attach them to the rotating central mass without colliding with neighboring spokes.

Select Stage (1 to 130+) Level 1
130+
Procedural Levels
0.13r
Collision Radius
120Hz
Max Refresh Rate
3 Pattern
Motion Complexities
Sensory Integration

The Neurobiology of Visuomotor Timing & Spatial Coordination

The ability to coordinate physical movements with moving visual targets is a highly complex cognitive process. When playing **Core Ball**, your brain performs split-second calculations. The central rotating ball acts as a moving spatial target, requiring you to process its speed and direction, predict its future position, and execute a motor response within a tiny millisecond window.

This sensory-motor process involves several key neurological systems working in sync:

Sensory-Motor Timing Pathway

  1. **Retinal Input:** Foveal cells capture the rotational speed of the core and send information down the optic tract.
  2. **Parietal Mapping:** The **posterior parietal cortex** maps the coordinates of the rotating pins relative to the vertical shooting path.
  3. **Motor Execution:** The motor cortex fires commands down the corticospinal tract, directing the finger muscles to trigger the keypress.
  4. **Error Correction:** The cerebellum continuously monitors timing, modifying your next attempt if a collision occurs.

These neural networks are highly responsive to training. With practice, the pathways that process these spatial coordinates become more efficient, improving your reaction time and coordination.

Mathematical Physics

Trigonometric Calculations & Rotational Coordinate Mapping

Under the hood, the **Core Ball Game** relies on trigonometric equations to track objects on a rotating 2D plane. Rather than using Cartesian coordinates $(x, y)$, the game engine tracks attached pins using **Polar Coordinates** $(r, \theta)$, where $r$ is the radial distance from the center and $\theta$ is the current rotational angle.

When you fire a pin from the bottom of the screen, it travels vertically along the $y$-axis. Once the tip of the pin reaches the attachment radius ($r \approx 130$ pixels), the engine converts its vertical position into a fixed rotational angle on the core:

Relative Attachment Angle (θ) = π/2 - Active Core Angle (radians)

Once attached, the pin's position update is calculated using standard trigonometric conversions:

x = CoreX + r * cos(Active Core Angle + Relative Angle)
y = CoreY + r * sin(Active Core Angle + Relative Angle)

To detect collisions, the engine measures the absolute angular difference between your newly fired pin and every attached pin. If this angular distance falls below **0.13 radians** (about 7.4 degrees), a collision occurs, triggering the game-over state.

Technical Latency

The Technical Latency Stack: System Delay and Input Lag

Like any competitive reflex game, your test scores are heavily influenced by your device's hardware and system latency. A slow or poorly optimized setup can add several milliseconds of delay, causing you to make mistakes despite having perfect timing.

The technical latency stack introduces a series of delays that can affect your performance:

  • **Display Frame Lag:** A standard 60Hz monitor takes **16.67 milliseconds** to draw a new frame. At high rotational speeds, this delay can cause a pin to attach up to 4 degrees away from where you intended. Upgrading to a 144Hz or 240Hz screen slashes this lag, giving you much smoother and more accurate visual feedback.
  • **USB Polling Delays:** Standard computer mice check for clicks every 8ms (125Hz). Modern gaming mice increase this to 1000Hz or higher, dropping sensor scanning latency to just **1 millisecond**.
  • **Device Input Lag:** Mechanical key switches can introduce a debounce delay of **4ms to 12ms**. Opting for optical switches with zero debounce helps ensure your shots are registered instantly.
Level Architecture

The Level Scaling Structure of our Core Ball Engine

To keep gameplay engaging, our Core Ball engine uses a **procedural level generator** that scales difficulty over 130 distinct levels. The game dynamically adjusts several parameters to create unique and challenging stages:

Target Pin Density

As you progress, the game increases the number of pins you need to shoot (up to 20 pins), forcing you to pack them tightly together and leave minimal margin for error.

Initial Spoke Obstacles

Later levels start with up to 15 obstacle pins already attached to the core, limiting your target zones right from the start.

Variable Speed Patterns

The core's rotation changes from a constant spin to complex patterns, including sudden direction reversals, stuttering spins, and sinusoidal speed variations.

F.A.Q.

Frequently Asked Questions

Core Ball (also known as Coreball, or simply 'aa') is an arcade game focused on spatial timing and precision. Players must shoot smaller numbered balls into a central rotating core. The level is successfully cleared when all pins are attached without colliding with any existing spokes or attached needles.
This version of Core Ball features **130+ procedurally generated levels**. Each level increases in difficulty by adjusting parameters such as rotation speed, initial obstacle spokes, target balls, and complex speed patterns (e.g., stuttering or alternating directions).
Collision is calculated using polar coordinate angles. Because all spokes have a fixed radius, collision occurs when the absolute angular difference between any two attached pins drops below approximately **0.13 radians** (about 7.4 degrees).
System input lag can severely throw off your timing. At high rotational speeds, a 16.6ms display delay (typical on 60Hz monitors) can cause a pin to attach up to **4 degrees** away from where you intended, often resulting in a collision.