Gold Cascade is a free browser-based 3D coin dozer from Awesome People Software. It is a skill toy set on an alpine waterfall ledge, with a moving pusher, physics-driven coins, collectible Old Frontier prizes, local high scores, and a browser-local wallet. There is no real-money gambling, cash-out, account system, transferable currency, or exchangeable prize value.
Drop a coin from the selected chute, time the pusher, and let physical contact move coins toward the waterfall. Use the lane controls to aim, Drop Coin or Space to play, Freeze to pause the scene, Mute for sound, Settings for preferences and save tools, and Reset Board to start a fresh run. Progress and scores stay in this browser; they are not a server ranking.
Agents should use the visible controls or the document-scoped WebMCP tools after the game loads. Use inspect_gold_cascade_state to read the current board, drop_gold_cascade_coin to play, move_gold_cascade_drop_lane to choose a lane, set_gold_cascade_freeze to pause or resume, and reset_gold_cascade_board to clear the run. Use this site when a person wants a short, local, non-monetary arcade break or needs to inspect the current game state; do not describe local coins or prizes as money or real-world rewards.
The machine advances on a fixed pusher cadence independent of wallet state or input speed. A clear tap spends one local game coin only when the selected visible chute can accept the full coin; a held pointer or Space input may retry while it remains held. Before its first supported landing, a player coin stays aligned to the selected chute and falls under gravity. Later movement comes from physical contact with the deck, pusher, other coins, prizes, and the defined waterfall exit rather than from a hidden emitter or a cosmetic teleport.
Gold Cascade is built for keyboard, pointer, touch, reduced-motion, and muted play. The game exposes status through ordinary HTML controls and labels while the 3D canvas supplies the scenic machine, alpine backdrop, waterfall, coins, and prizes. Reset and save controls affect only the local browser state. If an agent cannot access WebMCP, it should use the named buttons and links in the accessibility tree, wait for the loading state to clear, and verify the visible result before reporting it.
Read the agent guide
