1. Forum
  2. FidoNet
  3. SYNC PROGRAMMING

  • xtrn/syncmoo1/README.mdxtrn/syncarcade/README.md lobby.js xtrn/syncdoo

    From Rob Swindell (on Debian Linux)@1:103/705 to Git commit to main/sbbs/master on Mon Jul 27 20:26:18 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/e56d75dcf446e21086e0aa57
    Added Files:
    xtrn/syncmoo1/README.md
    Modified Files:
    xtrn/syncarcade/README.md lobby.js xtrn/syncdoom/README.md xtrn/syncivision/lobby.js xtrn/syncmoo1/getdata.js xtrn/syncnes/lobby.js xtrn/yumenikki/README.md getdata.js
    Log Message:
    xtrn: make .md references resolve from an installed door directory

    A door's xtrn/<dir>/ is what a sysop installs; the Synchronet source tree
    need not be there at all. Several doors nonetheless pointed their README
    and their script comments at documentation under src/doors/ or docs/superpowers/ -- and four of those pointers named the file bare (GAMES_INI.md, LAUNCHER.md, M2_INPUT.md, M3_MULTICORE.md), as though it
    sat beside the file citing it, which it never did.

    Drop those references. Where the sentence carried something a sysop
    needs, re-point it at something the installed door actually has:
    SyncDOOM's multiplayer note now cites the [net] comments in syncdoom.example.ini, and SyncArcade's per-game note cites games.ini's
    own header comments -- each documents precisely what was being referred
    to. Build-instruction pointers name the source directory rather than a
    file inside it.

    syncmoo1 had no README at all, the odd one out among the newer doors, so
    its getdata.js reached for src/doors/syncmoo1/README.md and DESIGN.md
    section 15 to explain that the sysop must supply the game data. Give the installed door its own README instead, in the style of the SyncDOOM and SyncArcade ones, and cite that. It leads with the two things a sysop has
    to settle before the first player -- a sixel-capable terminal, and sysop-supplied Master of Orion data files -- and names two failures whose
    cause is otherwise obscure: MoO1's copy protection is armed unless
    syncmoo1.ini disables it, and a *.LBX copy pattern silently misses
    v11.lbx, the one lower-case data filename and 1oom's own v1.3 marker.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)