Skip to content

Quake 2 Re-release TypeScript v1.1.1

Latest

Choose a tag to compare

@mgd34msu mgd34msu released this 06 Sep 15:56

Quake 2 Re-release TypeScript v1.1.1

Play-test fixes across both rulesets, LMCTF end to end, a rebuilt multiplayer front end, and a play-through test gate.

Added

  • Bots for the re-release module: the game-agnostic bot brain shared with
    quake-1-re-ts (src/qcommon/bot_brain, lifted at its commit f57aadb with
    three stuck-bot fixes made here) bound over the kex edicts' sv_entity
    projection, the NAV3 navmesh mapped onto the brain's graph, synthesized
    weapon/item/monster/interactable knowledge tables (the re-release ships no
    bots/*.txt for Quake II), socketless bot client slots seated like local
    splitscreen players, addbot/kickbot/bot_skill/bot_count. On retail
    q2dm1 two bots roam the navmesh, pick up items and fight. Legacy-module
    bots need the sv projection synthesized (see src/server/bots/bot_game_view.ts).

Play-test fixes (Call of the Machine under the re-release module)

  • Alpha-tested world surfaces (the re-release's SURF_ALPHATEST flag:
    Call of the Machine's foliage and roots) render with their cut-outs in
    both renderers instead of black or pink rectangles.
  • A real model can no longer land on model index 255, the wire's "draw
    the player model" slot; a map that precached more than 254 models drew
    one monster as the player.
  • The help computer's text centers inside its panel: the kfont width
    measure now scales with the HUD like the draw does, which also fixes
    every centered or right-aligned re-release string at HUD scale 2x.
  • The view weapon draws at any field of view in play (vanilla hid it
    above fov 90; the reference and the re-release only do that for
    compatibility demo playback).
  • Hitscan and projectiles hit monsters again after a level change, and
    items are picked up: entities kept their area-grid links across a map
    change and the grid ring was severed on the first relink (532 solid
    entities linked, 89 reachable on a session's second map); the
    collision box hull also lacked the merged contents the re-release
    trace reads. Every item on Wastelands, Too Deep, Uplink Tower and
    Outer Base is now reachable and picks up (575 items swept).
  • All-maps sweep (2,567 launches, every map under every module,
    server messages classified against the original game code): a
    point-entity trigger no longer drops the level under The Reckoning,
    Ground Zero, CTF and LMCTF (outbase and four other maps); the
    re-release module's warnings carry the entity position like the C++;
    a BSP whose entity lump runs past the file end (three third-party
    maps) loads as vanilla does instead of erroring out.
  • Client CPU time per frame on the largest re-release maps is down by
    about a quarter (Strogg Gateway: 25.1 to 19.0 ms of engine work per
    frame): world surfaces draw as vertex arrays, frustum culling passes
    its results down the tree, the image lookup is indexed, the pak name
    lookup is indexed (a missing file no longer scans every pak entry per
    probe), the entity sync skips empty slots, and the per-frame
    allocations in the world walk and relighting are gone. This is what
    the 40 Hz animation and monster movement were losing to.
  • Two third-party classic maps with long level names dropped the client
    with "Illegible server message" on connect: the server compressed the
    very first message, which no reference client can decode before the
    server data arrives, and the client dispatched that opcode by a codec
    it had not negotiated yet. Both fixed. A map with corrupt surface
    edges (amine) is refused with a clean error instead of a crash; the
    original engine crashes on it too.
  • Walking off a step or small ledge under the re-release module no
    longer drops the view in one frame: the re-release's step-down moves
    the player up to 18 units in a tick and the client's prediction only
    smoothed steps up, so the eye teleported down; the reference's
    step-smoothing rule (magnitude, accumulated, clamped) is ported.

Second play-test round (classic module on re-release data, LMCTF)

  • Returning to a level you already left (Outer Base to Installation and
    back) no longer hangs the game on the way back in: the monsters' sight
    client search read the entity-state number of the cleared player edict
    (vanilla drops player edicts from the level save on purpose) and never
    reached its stop condition. It now uses the edict's index like the C.
  • Changing level no longer crashes the client: client-side prediction
    kept clipping against the previous map's brush models after the
    collision model the local server shares with it had been reloaded, and
    a stale node index is not addressable here the way it was in the C's
    static arrays. Prediction skips brush entities until the client has
    refilled its clip table for the new map.
  • Level and server save files are looked for and read in the write
    directory only, as the C's fopen(FS_Gamedir()) does. A stale save in
    another mounted root (the basedir while the home directory was the
    write root) made the engine try to restore a level it then could not
    open.
  • Loud static when stepping into or out of water: the re-release's
    footstep sets (splash, carpet, grass, snow, tile) and one klaxon are
    24-bit PCM, which the 1997 loader has no path for and decoded as
    noise. The reference's 24-to-16-bit conversion is ported.
  • LMCTF (Loki's Minions CTF) sends every connecting client the
    +hook/-hook aliases its own game code stuffs, so bind mouse2 +hook works as documented. Its rotation list is found through the
    search path (the console printed "Can't find lmctf/maplist.txt").
  • The menu names LMCTF correctly, no longer offers LMCTF or CTF as
    single-player content, and the multiplayer start-server screen gains a
    game selector: each mod's own map list and rules (CTF for CTF mods,
    deathmatch otherwise) with the vanilla fields kept. Launching a mod
    from the menu applies the game directory after the server is torn
    down and before the map loads; it used to latch and the map was not
    found.
  • Firing under the re-release data no longer spams "no such frame 1":
    the one-frame muzzle flash models were added to the scene twice, the
    second time at frame 1.
  • The classic module on re-release data shows the map's messages as
    text: centerprints that arrive as localization keys are localized and
    the re-release's leading bind tokens are dropped for the classic HUD.
  • New cl_drawfps (1 draws the frames per second top-right at HUD
    scale).
  • Picking up an armor shard under the CTF and LMCTF modules dropped the
    game with "Pickup_Armor: item.info is not a GitemArmorT": the armor
    info was validated before the shard branch that never reads it (the
    shard's info is NULL in the C).
  • LMCTF scores again: a flag capture, frag or assist adds to the player's
    and team's score. The mod keeps per-player statistics in a record it
    creates when the client connects (or finds again by name after a drop);
    the port cleared that record at connect and never created one, so every
    score add was silently dropped and the HUD stayed at zero.
  • LMCTF assigns the player a team skin the way the mod does: the skins
    file's list when it is loaded, else the skinset's built-in team-colored
    set, on connect, on team join and on respawn from spectator. The client
    kept whatever skin it arrived with, so the HUD portrait lookup printed
    "Can't find pic: grunt_i" every frame. The mod's line-based files
    (skins.ini, maplist.txt, menus) are read the way the Windows builds read
    them: the CR of their CRLF line endings is dropped, so "[blue]" matches
    and rotation entries carry no stray character.
  • The start-server screen gains a ruleset row (Classic 3.21 / Re-release
    2023) under the game row, and every game offers both: deathmatch, The
    Reckoning, Ground Zero and CTF under the re-release ruleset run the
    re-release module on the re-release data, LMCTF under it runs LMCTF's
    own code on the re-release wire family. The map list, rules and server
    options follow the resolved pair, and the "kex" module name no longer
    appears as a game choice. A "-kex" selector now mounts and writes
    the mod's own directory and the launch keeps the classic tree as the
    fallback root, so LMCTF under the re-release ruleset finds its maps,
    skins file and rotation list (verified: lmctf41 loads with the 43-entry
    rotation under the re-release module family).
  • LMCTF under the re-release ruleset puts the player where the server has
    them: the re-release wire format carries the player's position as
    floats, LMCTF's movement code fills only the classic fixed-point pair,
    and the binding between them never mirrored one into the other, so the
    client was told it stood at the world origin (spawning outside the
    level, every sound heard from far away).
  • Menus scale at high resolutions and take the mouse. Menus and the
    console lay out on a virtual 640x480-class canvas drawn at the same
    tier the HUD picks (ui_scale, 0 = auto, named after the reference
    client's cvar; a "menu scale" row on the video screen applies it live),
    so at 1280x960 every screen is the 640x480 layout at 2x instead of an
    8-pixel-font block. The pointer hovers and selects, left click
    activates, right click backs out, sliders click and drag, spin values
    cycle by half, lists select on hover and scroll by wheel or scrollbar,
    fields focus on click; keyboard navigation is unchanged and the Keys
    screen still binds mouse buttons.
  • Server browser redesigned as a dense screen: it renders one tier below
    the menu scale (native on a 720-line display) with a source tab strip,
    a boxed toolbar (refresh, favourites, address book, masters, hide-empty
    and hide-full chips, a text filter, direct address and connect), a framed
    table with a header bar, zebra rows, a highlight selection bar and a
    drawn sort triangle, a footer with counts and key hints, and a framed
    two-column detail card (server info, player list). Every control is
    reachable by keyboard with the status bar naming what Enter does. Sort
    by players lands most-first, by ping lowest-first, and choosing the same
    column again reverses. Servers that never answered are not listed.
    Switching sources sends nothing for a source already loaded; only the
    refresh row asks again; each master is queried once and each host probed
    once per refresh; nothing the browser receives reaches the console. The
    server settings screen uses the same framed, two-column layout.
  • Multiplayer screens rebuilt. Join Server is a server browser: a
    full-width table with sortable columns (server, map, players, ping,
    game, mode), sources (local network, address book, favourites, master
    servers, all), filters, favourites, a direct address field, and an
    always-visible detail panel with the selected server's full settings
    (dmflags decoded to words) and its current player list with scores
    and pings. Each server is queried once per manual refresh and once
    when selected; there is no timer and no traffic while the screen sits
    idle. Create Server has one scrolling settings screen per game with
    every server setting the game reads: capture limit and the CTF and
    LMCTF essentials are on the start screen itself, LMCTF's sixteen
    ctfflags bits, runes, banned weapons and match settings, CTF's
    competition and admin settings, Ground Zero's and The Reckoning's
    extra flags, and the re-release module's rules. Moving the game row
    no longer prints pak mounts to the console. The console has its own
    scale row (con_scale), separate from menu and HUD scale.
  • LMCTF gains a capturelimit server setting (off by default, so the
    mod plays exactly as shipped): when set, the level ends once a team's
    captures reach it. LMCTF itself had no capture limit.
  • LMCTF under the re-release ruleset showed the re-release's Threewave
    flag and its runes drew with the wrong skeletons: the renderer took the
    re-release pak's high-resolution MD5 replacement for any model with the
    same path, even when the mod's own model sat above it in the search
    path. A replacement is now accepted only from the same or a higher tier
    than the model it replaces, so a mod's deliberate asset wins and the
    re-release's own models keep their upgrades.
  • LMCTF under the re-release ruleset: crouch and jump work. The
    re-release wire carries crouch and jump as button bits and has no
    up/down move value, and LMCTF's classic game code only reads the
    latter, so the server never ducked or jumped while the client's own
    prediction did and snapped back. The bits are translated to the move
    value a classic client would have sent before they reach the mod.
  • Start server: a mod's shipped server.cfg is the source of its default
    settings. LMCTF's offhand hook (ctfflags bit 16), its dmflags, banned
    weapons, runes and limits come from lmctf/server.cfg (ctfflags 13396)
    the moment the game row lands on it, the way the mod's own launcher
    execs that file; the compiled-in defaults had left the hook off.
  • Menu over a cinematic (Escape during the id logo or a mission
    intro): the frame is blacked out over the whole render buffer again.
    The scaled-menu work sized that fill by the 640x480-class canvas, so
    at 1280x960 only the top-left quarter was repainted and the rest
    showed two alternating stale frames of the video, old menu pixels and
    every previous pointer position (flicker, ghosting, pointer trails).
    The gate now also grabs the real window across several frames on a
    virtual display and checks the frames stay identical with exactly one
    pointer, which is the check that would have caught this.
  • Join server: a real ping column (each host re-probed every three seconds
    while the screen is open, rolling average, loss mark), sorting by ping,
    name or players, and a source row for the local network, the address
    book, or master servers (the reference client's list formats: plain and
    binary lists over file, http and udp sources). A "master servers" screen
    edits the list (16 slots, saved to the config like the address book,
    restore defaults), pre-populated with the masters verified live on
    2026-09-06: the q2servers.com list over https and the quakeservers.net
    and itbacon.com UDP masters, which answer a bare query; kingpin.info
    (Kingpin servers) and the dead netdome.biz are left out; an
    unreachable master degrades to an empty list with a note.
  • Host names resolve everywhere an address is typed: connect, rcon,
    packet, the address book and pingservers, the join screen, master
    servers, and the server's setmaster heartbeats (re-resolved when a
    master's address goes stale). The address parser accepted only dotted
    quads where vanilla called gethostbyname. Lookups run off the frame loop
    with a short cache, so retransmits and retries stay synchronous, and a
    bad name prints vanilla's "Bad server address" without entering the
    connecting state. Verified live by hostname against an internet server. Re-release
    map titles from mapdb.json fill the picker, builder and join lists
    wherever maps.lst has no long name (194 titles).
  • Map lists respect the mode. Every reachable map is classified from its
    entity lump (flag or team spawns make a CTF map, deathmatch spawns a
    deathmatch map, a lone player start a single-player map) and campaigns
    come from the campaign's own lists. Cooperative shows the campaign in
    play order and nothing else (Quake II 39, The Reckoning 18, Ground Zero
    15); deathmatch shows single-player and deathmatch maps and drops
    CTF-only maps; capture the flag shows flag maps only, and CTF and LMCTF
    share each other's maps: the sibling mod's maps, textures and skies
    mount as a read-only tier under the host game's own files, plus only the
    exact sounds a borrowed map's speakers name. Flags, banners, techs,
    skins, HUD art and capture sounds always come from the mod being played
    (both ship different files under the same names), verified per file in
    both directions. Both list the same 195 flag maps. The single-player New
    Game screen is unchanged.
  • Multiplayer section rework. The map picker lists every map the chosen
    game and ruleset can actually load, not the first list it found: maps.lst
    and the mod's own list first in their order, then every bsp in the
    mounted paks and directories including the base tier and the data trees
    the launch mounts (Quake II 39 to 343 maps, CTF 5 to 356, The Reckoning
    25 to 372, Ground Zero 29 to 375, LMCTF 43 to 524). A scrolling list
    control (keyboard, page and wheel, scrollbar, position readout) replaces
    the fixed spin rows and a filter field searches names. A map-list
    builder assembles a rotation, saves and loads named lists under the
    home directory, and on begin writes what each module reads: sv_maplist
    for the classic family, g_map_list and its shuffle for the re-release
    module, and LMCTF's own maplist_file as well. The join-server screen is
    one scrolling list of every server that answered plus the address book,
    with a round-trip time column; recorded servers no longer all collapse
    onto the last responder. ESC backs out one level everywhere.
  • The multiplayer "deathmatch flags" screen is now "server options" and
    follows the game selected on the start-server screen: baseq2 and The
    Reckoning keep vanilla's fifteen rows, Ground Zero adds its four, CTF
    adds a "ctf rules" sub-screen (capture limit, instant weapons, force
    join, competition, match lock and timers, election percent, admin menu,
    unbalanced warning, advertise, zombie timeout), LMCTF adds ctfflags,
    runes and skin set, referee set and disabled weapons sub-screens, and
    the re-release module gets its own g_dm_* and teamplay settings (it
    never reads dmflags). Every row writes the cvar or bit the game code
    reads, seeded with that module's default so the screen shows the real
    values when opened from another game.
  • Console variable and command parity audit against the 3.21 source,
    the re-release game code, LMCTF 6.0 and the reference client, with
    the gaps ported: the re-release module's coop respawn messages used
    scrambled state codes (every "waiting/no lives/blocked" message was
    the wrong one) and teamplay never ended a level on the frag limit;
    LMCTF gains its MOTD file, skins file, log rename, server file,
    revision and funky-gravity cvars with the behavior behind them;
    vanilla's z_stats, noipx and download are registered; the
    reference client's toggle, inc, dec, reset, resetall,
    seta, sets and setu commands exist.