Somebody already wrote the road. Clone it.

Every desert starts with a few scripts in ~/dunerider. The dunerider-starters repository on GitHouse has five, each in its own folder with a README that says how to drive what it builds. Three are new; pave-ahead is the helper your desert already has, and stairway is a wider one that turns to face you:

stairway: a three-wide flight of 45-degree steps, turned to face the way you face.

pave-ahead: lays road two cells ahead of your wheels while you drive.

chasm-bridge: finds the drop ahead with scan ground and bridges it.

spiral-tower: a square tower of flights and landings, in pure Bash.

spiral-slide: a round road spiralling down to the sand. awk works out the circle.

Every script builds from wherever your buggy stands, so it works in any desert.

1. Clone the repository

Use Git inside the CLI-Games terminal:

git clone https://forge.cli-games.com/cli-games/dunerider-starters.git ~/scripts/dunerider-starters
cd ~/scripts/dunerider-starters
ls
git log --oneline

Cloning never runs a script. Guests can clone, edit and commit locally; an account comes in only when you want to publish. If you already cloned it, cd into the existing folder instead: Git refuses to clone over a folder that is not empty.

2. Bridge a chasm

Start the game and drive to a chasm. Seed 4417 has one about 300 metres north of the start pad: choose From a seed, type new 4417, and drive north over the dunes. Stop a little before the edge, facing across, then run the bridge from the game's terminal:

dunerider
cd ~/scripts/dunerider-starters/chasm-bridge
./chasm-bridge.sh

The script reads the sand ahead with scan ground, finds where it drops away and where it comes back, and lays a three-wide road across the gap. The road runs level with the higher rim. When the far side is higher than you, it starts with a short climb: keep your speed up. If you stopped too close for that climb, it tells you how many cells to back up.

Ctrl+B, then T reaches the terminal; Ctrl+B, then G goes back to the desert.

3. Climb the tower, then ride the slide

On open sand:

cd ../spiral-tower
./spiral-tower.sh

Four flights of 45-degree steps rise between flat landings, turning right. Hold Space up each flight and ease off at the top. Keep rolling at walking pace while you turn right across the landing, then hold Space up the next flight. Do not stop at the foot of a flight: the wheels can drop into the crease where the landing meets the first step. If you stick, try a hop (Shift); B takes you back to the start.

At the top landing, face the open side and build the way down:

cd ../spiral-slide
./spiral-slide.sh

The slide turns left, away from the tower, and drops one cell every four cells of road. Roll off at 25 to 35 km/h and steer with the curve: each step down is a small jump.

4. Change a script

Each script takes its sizes as arguments. ./spiral-slide.sh 14 6 builds a wider, gentler slide; ./spiral-tower.sh 8 climbs two laps. To change one for good, edit it:

nano ~/scripts/dunerider-starters/spiral-slide/spiral-slide.sh

Change RADIUS=${1:-10} to RADIUS=${1:-12}, save with Ctrl+O, press Enter, and leave with Ctrl+X. Run it again to see the difference. remove --all clears the desert if you want to start over; it asks first.

5. Record it with Git

Leave the game with quit, then:

cd ~/scripts/dunerider-starters
git switch -c wider-slide
git diff
git add spiral-slide/spiral-slide.sh
git commit -m "A wider slide"
git log --oneline

git diff shows exactly what you changed before you record it. A local commit stays in your home and publishes nothing.

To publish your branch, follow GitHouse from first visit to first pull request: verify your account, activate GitHouse, fork dunerider-starters, and push a signed-off branch to your fork. Maintainers review pull requests to the official repository. Anyone can then clone your fork and run your road where they are standing.

Keep LICENSE.txt and the attribution when you share. See Dunerider for the controls and every command the scripts use.