• xtrn/syncalert/install-xt

    From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Fri Jul 10 03:28:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/6556a01a918af7b229ec2dc2
    Modified Files:
    xtrn/syncalert/install-xtrn.ini
    Log Message:
    syncalert: install with XTRN_NODISPLAY

    Set XTRN_NODISPLAY so Synchronet spawns the door with CREATE_NO_WINDOW
    rather than CREATE_NEW_CONSOLE: no console window appears on the BBS
    machine, not even the brief flash before the door's own FreeConsole() (37de0f1035 / arrivals-29-noon) closes it. The two compose --
    CREATE_NO_WINDOW still gives the process a console, so the door's GetConsoleProcessList() == 1 test holds and it simply frees an already-invisible one. The door keeps calling FreeConsole() because a DOOR32.SYS door can be run by a BBS that has no such setting. Nothing is
    lost either way: the door draws to the client's terminal and freopen()s
    stderr onto data/syncalert/syncalert_n<node>.log.

    Existing installs keep their current flags -- this only affects a fresh install-xtrn run; a registered door is changed in SCFG -> External
    Programs -> SyncAlert -> Disable Local Display.

    XTRN_NODISPLAY resolves via 3e7e3aec6d (fist-4-node), which added it to sbbsdefs.js -- install-xtrn.js eval()s this settings line.

    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Wed Jul 22 20:38:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/1ae3fc97a8776971c69108ca
    Modified Files:
    xtrn/syncalert/install-xtrn.ini xtrn/syncarcade/install-xtrn.ini xtrn/syncdawn/install-xtrn.ini xtrn/syncdoom/install-xtrn.ini xtrn/syncduke/install-xtrn.ini xtrn/syncivision/install-xtrn.ini xtrn/syncnes/install-xtrn.ini
    Log Message:
    xtrn: don't claim sixel is required for the doors with a text tier

    The previous desc pass overclaimed: it said "Requires a sixel-capable
    graphics terminal" for every graphics door, but only the pixel-art adventure/strategy titles actually have no text fallback. The framebuffer
    doors render a character/block tier (half/quadrant/sextant glyphs in ANSI color) and are playable on a plain ANSI/CP437/UTF-8 terminal -- exactly
    the distinction the SyncSCUMM README already draws ("Unlike the
    framebuffer action doors (SyncDOOM, SyncRetro), SyncSCUMM has no
    text/ANSI fallback tier").

    Correct the seven that have a text tier -- syncdoom, syncduke, the
    SyncRetro consoles (syncivision, syncnes, syncarcade), and the Command & Conquer doors (syncalert, syncdawn) -- to "Best on a sixel/JPEG-XL
    graphics terminal (e.g. SyncTERM), also playable on any ANSI/CP437/UTF-8 terminal via block characters", keeping each one's mouse note.

    Left as graphics-required (verified against their READMEs -- these render pixels only, no text present path): the seven ScummVM adventures (syncbass/queen/lure/drascula/spacequest0/cascadequest/betrayedalliance), yumenikki (SyncRPG), and syncmoo1 ("renders sixel only... a terminal
    without sixel gets no picture").

    Config text only.

    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Wed Jul 22 20:38:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/a76e3bdd5bad3e654548a0b5
    Modified Files:
    xtrn/syncalert/install-xtrn.ini xtrn/syncdawn/install-xtrn.ini
    Log Message:
    xtrn: mark the SyncConquer doors graphics-required, not text-playable

    The prior commit lumped syncalert/syncdawn in with the framebuffer doors
    that have a usable text tier, but Command & Conquer is not actually
    playable as block characters -- an RTS needs the real picture to read
    units and terrain. The intent is for these doors to reject a text-only
    terminal outright, the way SyncSCUMM already does. Put their descs back
    to "Requires a sixel-capable graphics terminal (e.g. SyncTERM); mouse supported."

    syncdoom, syncduke, and the SyncRetro consoles keep the text-tier wording
    -- those genuinely play as block glyphs on an ANSI/CP437/UTF-8 terminal.

    Config text only.

    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Mon Jul 27 20:26:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/99bb9d1ac4d389a86afd67e0
    Modified Files:
    xtrn/syncalert/install-xtrn.ini xtrn/syncdawn/install-xtrn.ini xtrn/syncdoom/install-xtrn.ini xtrn/syncduke/install-xtrn.ini
    Log Message:
    xtrn: correct stale installer text in four game doors

    SyncDawn's installer told sysops the opposite of what it now does. Its
    Desc and its per-program note both sold it as the "single-player
    (campaign)" launcher, and a comment stated outright that classic Tiberian
    Dawn "is CAMPAIGN-ONLY for a solo caller -- it has no skirmish-vs-AI
    mode". The commit that took Network off the multiplayer menu established otherwise and corrected the deferred-features note: the vendored engine
    carries Skirmish for Tiberian Dawn as well, played against Red Alert's base-building AI, so a lone caller gets a full game exactly like
    SyncAlert's. The installer was simply the copy nobody updated -- and it
    is the copy a sysop reads while deciding whether to install. Say what is
    true, and why the AI behaves as it does. A second comment there claimed
    the door builds "once the vanilla/tiberiandawn/ engine is vendored"; it shipped, and both titles build by default.

    All four doors also pointed at deploy.sh and deploy.bat for installing a freshly built binary. Neither has ever existed in either source tree --
    both syncduke and syncconquer ship deploy.js, which is what COMPILING.md documents and what actually works on Windows as well as *nix. A sysop
    following the comment lands on a missing file at exactly the point they
    have a binary to install.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net