Mahjong

Mahjong installed: first hour

By Porcelain Lattice editorial team Current release, published September 12, 2026

Close detail of the tile-pair connector between two matching upright tiles.
Tile-pair detail for the mahjong mark used across this install guide. Porcelain Lattice original tile-pair geometry for factory-mahjong (not an ffalt/mah logo).

You installed Mah. The next hour is about proving a local clear, choosing a tile set carefully, and writing the update door so the next mahjong bump stays honest.

Success is a board that accepts matches on hardware you control. Skip Softonic “repair” downloads. Stay on the Releases filename you already used.

Eight first-hour steps

  1. Launch Mah. Confirm the solitaire window opens before you chase themes or Android apks.
  2. Start a classic board. Turtle or Dragon is enough for the first clear on this mahjong desk.
  3. Match free tiles. Prove selection, undo if needed, and one completed layout or a solid partial clear.
  4. Optional tile set. Try one of the thirteen tile image sets after the first clear, not before.
  5. Optional zen mode. Hide chrome only after you know where the main controls live.
  6. Optional timer. Enable the clock if you want paced runs; leave it off for a calm first hour.
  7. Optional daily challenge. Turn it on once the classic loop feels familiar.
  8. Write the update door. Record win-mah-*-x64.msi, the DMG, or the .deb beside the OS version.

Windows notes

SmartScreen may appear on first launch of the MSI. Prefer the GitHub Releases URL you typed. No winget id was found, so do not invent a package manager repair path.

macOS notes

Open the aarch64 DMG from the reviewed tag. Gatekeeper prompts are UNVERIFIED here; still refuse renamed mirrors that only rank for mahjong.

Linux notes

If you used the .deb, keep apt as the removal door. If you used AppImage, keep the chmod +x habit documented. Commands remain UNVERIFIED on a real machine in research.

What not to do

  • Do not download a second portal installer to “fix” a prompt
  • Do not chase every challenge type before one classic clear
  • Do not mix .deb and AppImage without notes on the same user

Next reads

First-run guide: first run. Boards: boards and tiles. Safety: is it safe. Updates: update uninstall.

Porcelain Lattice maps filenames for people who searched for a local mahjong client and need an MIT Mah path. Upstream remains at ffalt.github.io/mah and ffalt/mah under MIT.

  • Keep one installer door forever on each machine ticket.
  • Prove one short local clear after every reimage.
  • Ask for the GitHub Releases URL instead of vague “best download” links.

Why filenames beat portals

People searching for mahjong often land on advertising pages that wrap a browser game or a renamed installer. Those pages can change overnight, hide the real filename, and ship toolbars beside the setup you thought you chose.

  • Prefer win-mah-*-x64.msi on Windows from ffalt/mah Releases
  • Prefer the aarch64 DMG or amd64 deb on the same tag when those desks matter
  • Refuse Softonic-style mirrors that hide the filename

No winget package id was found on this review date. Inventing one would send shared labs to the wrong mahjong product.

Repeatable lab rhythm

Club machines, classroom images, and family PCs all benefit from the same boring checklist. Write the OS version beside the asset name. Prove one short mahjong clear after every reimage.

  1. Match the GitHub filename character for character.
  2. Launch Mah and prove a local clear.
  3. Document the update door on the machine ticket.

Travel bags should separate phone apks from desk MSI files so a hurried restore never grabs the wrong binary. Shared tickets should say whether the room standard is deb or AppImage on Linux.

Closing discipline

Ask for the GitHub Releases URL whenever someone pastes a vague “best download” link into chat. Match characters in the filename. Prove a clear. Document the update door for this mahjong client.

Asset checklist before imaging

Before you image a lab for mahjong, confirm the live Releases tag still lists the Windows primary MSI together with the Linux and macOS builds you need. Prefer one tag for every desk in the room so support tickets stay short.

  • Windows: win-mah-*-x64.msi (EXE alternate on the same tag)
  • macOS Apple silicon: macos-mah-*-aarch64.dmg
  • Linux: linux-mah-*-amd64.deb or AppImage or rpm

Android apks help travel phones, yet they do not replace the desk MSI when you rebuild a shared mahjong image.

Support ticket lines that work

Write three lines on the machine ticket: OS version, exact asset filename, and the date you proved a local clear. That record beats another Softonic search when SmartScreen returns next month.

  1. Record the GitHub Releases URL you typed.
  2. Record the filename character for character.
  3. Record “cleared one board” with the date.

Family PCs and classroom images both benefit from that boring mahjong paperwork. It keeps the next bump on the same honest door without inventing a winget id that was not found.