Skip to content

v1.1.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 21:38
· 8 commits to main since this release

Client (Fabric mod, any server)

  • client_input holds key bindings across ticks, in steps (walking, sprinting, sneaking, double jumps, dashes, holding
    use or attack), and client_key holds one with hold_ms: the server gets them as from real keys.
  • client_trace records what the client has every tick (the player's position, velocity, flags and pose, nearby
    entities' boxes), keys held meanwhile, with a summary line first (ground and air ticks, height range, each entity's
    feet range); client_frames takes screenshots in a row as one contact sheet, after a command, the camera turning
    between frames; client_perf times the frames over a few seconds (FPS, lows, worst frame), after a command, to see
    what a change costs; client_stats a snapshot of what the client renders and holds; client_sounds the sounds
    played over a few seconds; client_pixels exact colours of the world without the HUD, or a region's mean colour,
    luminance spread and grid of cell means (stats); client_screenshot hide_hud.
  • client_connect joins a server (the last one by default) and waits until the player is in game, or leaves it.
  • client_test runs tests: steps over the client's tools, the server's Foreman tools, commands and waits, checked
    against what they return (texts, regexes, every number of a regex against bounds, arithmetic of captured values) and
    saved by name to run again, answering a line a step and the lines around a failure. keep_player puts the player
    back as they were; a death or a disconnect stops a test and says so. Any step, or group of them, can hold a network
    profile (network), ignore inbound packets (drop, both behind the server's foreman.test) and check the packets
    sent and received meanwhile (packets). The testing skill (action: guide, and a skill on servers with Foreman)
    says how to write tests that hold.
  • One agent drives the client at a time: the first acting call takes a lease that lasts 2 minutes past its last call
    (client_lock acquires it for longer, releases it, waits for it), other sessions' acting calls are refused
    meanwhile; /foreman-lock take|free for the player. MCP sessions get ids, and after the game restarts agents are
    told to start a new session, listing the tools again.
  • client_record and client_replay (and /foreman-record, a key): what the player does, recorded and saved with a test that
    replays it from where it started and says where its path left the recorded one.
  • Fast resource reloads (on by default, Debug → Resource packs): mipmaps for every sprite at once and on arrays,
    fonts' providers picked in linear time off the main thread, zip packs listed from an index, and no loading screen
    minimum or fade-out. A 70 MB pack reloads in about a second instead of ten, with the same resources.
  • Keep playing through reloads: the game stays on screen and playable under a thin progress bar; only the last step
    freezes it, without drawing it half done.
  • Each reload's time in chat, its steps in the hub, and in client_resource_packs with reload; /fastreload.
  • The last reload's warnings and errors in the hub, a row per kind, and a chat that finds their cause in the pack's
    sources and fixes it.

Server (Paper plugin)

  • test_player saves and restores players as a test found them, unhurt meanwhile; server_trace records the
    server's view of a player tick by tick, with the values plugins add through ForemanTools.registerTraceValues.