Set up backgammon on this computer

Setting up backgammon on this computer means giving Windows a clean extracted folder from GitHub Releases, not sprinkling shortcuts from three different mirrors. Take windows_build.zip from Final-Release on qawse3dr/Backgammon, extract every file, and run build.exe from that folder.

This page is the desk checklist after you already know the safe door. Soft parks for macOS and Linux stay parked. Home: board.

Pick a folder you will still recognise next month

Create a games folder under your user profile or on a shared drive the club already backs up. Extract the zip there so build.exe, build_Data and UnityPlayer.dll, and the full windows_build folder stay together. Avoid Desktop piles that get cleaned by login scripts without warning during backgammon season.

If you use OneDrive Desktop redirection, prefer a non-synced games path when antivirus fights cloud placeholders. Local extract reduces odd launch failures that look like broken board binaries but are really sync stubs.

Launch and prove the window

Double-click build.exe or start it from PowerShell with a working directory set to the extracted folder. Confirm the board appears and that sound plays if speakers are on. Upstream says sound files must share the folder; missing build_Data and DLLs are the most common self-inflicted backgammon setup mistake.

Play one short game or at least move a piece and undo via whatever menus the build exposes. Save a test local session files if you plan to teach resume habits. Save details: save and replay.

Permissions and redistributables

Upstream targets Windows XP or newer with Visual C++ Redistributable 2015-2019 x86 when missing. Modern Windows usually already has that runtime. If the exe fails immediately, install the x86 redistributable from Microsoft and retry before you blame the board zip.

Standard users should not need admin rights for a portable extract. If your image blocks unsigned exe files, escalate with the exact Releases URL rather than disabling SmartScreen globally for every installer.

Document the door on the machine

Write the Releases URL and zip filename on the machine ticket beside the OS version. Include the extract reminder so the next volunteer does not invent a naked exe download for backgammon. Update path: update and uninstall.

Keep built-in browser backgammon available until the local habit sticks. Comparison: vs browser backgammon. Switch plan: switch from browser backgammon.

Multi-user and lab images

For shared club PCs, put the extracted folder in a read-execute location and keep saves in per-user documents if profiles are separated. Do not rely on a single Desktop shortcut that one student deletes during cleanup.

For imaged labs, bake the extract into the golden image only after you verify the zip from Releases on a clean VM. Re-download on each rebuild rather than copying mystery folders between semesters of board teaching.

First-hour habits: installed. First run narrative: first run. Offline expectations: offline play.

What not to configure yet

Skip unrelated browser extensions, skip store board packs, and skip other board clients with different rule sets until one local GPL-2.0 board game works. Adjacent freecell and chess installs belong on their own tickets so this computer’s board path stays auditable.

No winget or brew id was found for this project. Do not add invented package commands to the setup script. Prefer the zip extract documented on releases and download safely.

Sound, saves, and everyday friction

Turn speakers on for the first board launch so you can tell whether build_Data and DLLs loaded. If the board opens silently, re-extract rather than downloading a second mirror. Keep test saves in the same folder during the first week so paths stay obvious to the next volunteer.

When Windows Search indexes the folder, build.exe may appear under different labels depending on shortcuts. Prefer opening from the extracted directory until everyone recognises the real board binary.

Travel days benefit from a USB copy of the whole folder after one successful game. Do not copy only the exe. Zip extract notes: zip extract. Releases proof: releases. GitHub reading: board on GitHub.

If you also maintain freecell or chess on the same computer, keep separate folders and separate tickets. The cluster only covers the board phrase and the Backgammon zip path.

Finish setup by bookmarking Releases and proving one board capture move so you know mouse targeting works on this display scaling. Then stop installing extra board packs the same afternoon.