How Collision Physics Work in Frenzy Ball
Every bounce in Frenzy Ball is a math problem solved sixty times per second. You do not need a physics degree to enjoy matches — but understanding collisions helps you tune wilder simulations.
Rigid bodies in plain language
Boots, balls, marbles, and walls are rigid bodies: shapes with position, velocity, mass, and rotation. The engine steps forward in small time slices. After each step, it detects overlapping shapes and applies impulses to separate them while conserving (or adjusting) energy.
Restitution: the bounce slider
Restitution ranges from 0 (no bounce) to 1 (perfect elastic bounce). Footballs in Frenzy Ball use moderate restitution so headers and volleys feel lively without endless ping-pong. Raise it in settings and posts become dangerous — shots that should die in the net rebound back into play.
Friction and sliding
Friction slows tangential motion when objects touch. Low friction boots slide after tackles, creating space. High friction grips the floor — useful in Wrestling Royale where ring positioning matters. Marble Race uses tuned friction so balls roll but do not stick on slopes.
Collision filtering
Not every object collides with every other. Goal sensors detect scoring without blocking play. Pickups use trigger zones. Walls belong to categories that balls bounce off but cameras ignore. These filters prevent glitches like boots stuck inside nets.
Continuous vs. discrete detection
Fast objects can tunnel through thin walls if time steps are too large. We cap velocities and use conservative wall thickness in Circle Clash so balls do not escape the arena. Tunneling bugs are the classic physics-engine headache — fixing them is ongoing work.
Angular momentum
Off-centre hits spin the ball. Spin affects subsequent ground bounces — a rolling ball curves slightly on contact. Arena Fight saw pickups add effective radius, changing which collision manifold applies first when two fighters overlap.
Stability vs. spectacle
Extreme settings stress the solver. Too many high-speed bodies in one pile can jitter. We clamp forces and use sleep states for resting objects to save CPU. On mobile, fewer trail particles and lower DPR keep the solver stable.
Experiments to try
- Max restitution + long Pitch match = goalkeeper nightmares
- Low friction + fast boots = slide tackles across half the pitch
- Team Race with many marbles = bottleneck jams at the first obstacle
Further reading
Matter.js documentation explains engines and constraints in depth. Our how to play guide covers player-facing settings. For mode-specific behaviour, see the game modes page.
Mass and impulse
Heavier bodies resist acceleration. A fast light ball can still knock a heavier boot slightly because impulse transfers through contact normals. Wrestling bodies use higher mass values so throws feel impactful without launching wrestlers off-screen.
Sleeping bodies
Resting objects stop simulating until disturbed — saving CPU. A ball rolling slowly may sleep early; the next collision wakes it. Occasionally a sleeping ball near the line creates tension as viewers wait for a boot to nudge it.
Debugging physics feel
When tuning, change one variable at a time. If both bounce and speed increase, outcomes explode nonlinearly. Document presets that feel good so you can return to them after experiments go wrong.
Reading the canvas
When debugging a weird goal, trace contacts mentally: boot-ball, ball-post, ball-keeper. Each contact exchanges momentum along the collision normal. Once you see the chain, the goal feels inevitable rather than random — and you can explain it to viewers who cry scripting.
Constraints and joints
Some arena elements use constraints for rotation — the Circle Clash outer ring spins on a motor joint. Wrestlers bounce off ropes implemented as stiff boundaries. Understanding which objects are free bodies versus constrained helps predict long-term motion.
Tuning exercise
Run identical teams three times: default physics, high bounce, low friction. Note goal frequency shifts. Naming your favourite preset helps you return after experiments go wrong.
Mobile solver limits
Phones use the same math with tighter CPU budgets. Sleep states and velocity caps keep framerate stable. Rare jitter in huge piles is a tradeoff for smooth performance on mid-range devices.
Teaching moments
When a child asks why the ball went in, walk through the last three touches. You teach vectors without naming them. Physics simulators accidentally educate — explain in captions for parents seeking wholesome gaming content.
Compare simulations to real highlight reels. Both contain chaos. The simulator just removes human intent from player movement while keeping contact chaos intact.
Energy loss
Simulators approximate real energy loss via damping and restitution below one. Tuning prevents infinite ping-pong while keeping matches lively enough for highlights.
Summary
Collisions are impulses, friction, and tuned material properties — not magic. Understanding restitution and contact order helps you tune wilder sims and explain goals to sceptical viewers. Experiment in Settings and name your favourite presets for next time.