How Duck Rush works

1. Set up the entries

1. Open the English race page and choose Edit entries.
2. Enter one name per line. Blank lines are removed; duplicate names, control characters, and lists outside 2–12 entries are rejected.
3. Optionally assign a duck color to each name. A blank color choice is randomized for that round.
4. Save the entries, then start the draw. The list is locked while a race is running.

2. Automatic-only race and fairness

The public version accepts no player input that can steer a duck or change the outcome. The browser’s cryptographic random source shuffles names onto duck IDs. Names do not change course physics, and there is no preset winner, name-based boost, hidden catch-up acceleration, or result animation selected in advance. Every duck starts without its own forward propulsion and is moved by the course flow; bends, narrow sections, collisions, obstacles, waterfalls, airborne motion, and landings can change the order.

Duck Rush records ducks as they actually cross the finish line and keeps the official times fixed while they continue floating into the lake.

This is a transparent casual draw, not a certified random-number service or proof that every physical duck ID has identical odds across all courses and browser implementations.

3. Cameras, pause, and results

• Overview: drag to orbit and scroll or pinch to zoom.
• Follow: the view-only camera stays behind the selected duck and attempts to avoid terrain and scenery. It cannot change the race.
• Pause: freezes simulation, animation, completed-duck drift, and the arrival presentation timer.
• Results: open the complete ranking after finish, copy it as text, or run the same list again. Previous winners are not automatically removed.

4. Courses and shareable state

The course menu sets the track URL parameter. Generated mountain geometry uses seed. These parameters represent state on the same language page; canonical links and the sitemap do not create separate indexable URLs for every combination. Development-only parameters such as debug and inspect are also excluded from the sitemap.

5. Browser requirements

The 3D race needs JavaScript, WebGL, and enough GPU memory for the scene and model assets. If WebGL or an asset fails, the readable homepage guide and this document remain available. Sound is off by default, and the public build does not request microphone access.