Skip to content

KCDS 1.0.5

Choose a tag to compare

@github-actions github-actions released this 11 Nov 23:19
27f6284

KCDS 1.0.5.

KCDS 1.0.5

New netcode built for crowds: a server keeps up with hundreds of players in one place, sends what is
near more often than what is far, and checks movement and melee reach by itself. Other players no
longer spin, scripts can put web pages on screens in the world, and KCDS gets its own page in the
game's settings.

Servers and players both need 1.0.5: a client and a server of different versions refuse each other
when joining. The launcher updates itself on the next start; servers update from their update
channel, the new packages or the Docker image ghcr.io/kcd-synced/kcds-server:1.0.5.

Netcode

  • Crowds: players near you are updated more often than players far away, motion travels in
    fewer bytes, and a busy tick gives the snapshots what time it has left. Large gatherings stay
    smooth for everyone.
  • Combat: each attack is sent once for everyone who sees it, not once per viewer.
  • Corrections: a short correction of your position glides in instead of jumping.
  • Checks: the server checks movement and melee reach and puts back a player who moves or hits
    farther than possible (a single hitch is only logged). Set KCDS_SERVER_MOVEMENT_CHECK or
    KCDS_SERVER_MELEE_REACH_CHECK to observe or off to only log or turn a check off.
  • Game updates: a client whose game build lacks combat or riding starts with that part off and
    says so, instead of not starting. Scripts read it from Player.clientNatives.

Other players

  • No more spinning: another player who turned no longer spun or swung back and forth, and no
    longer started a run sideways.
  • Standing and walking players keep their place between updates, and a crowd walks at an even pace.
  • Crowds keep their clothing colours (past about 200 dressed people, new ones were drawn in white).

Player women

  • The inventory shows a woman with a weapon worn (only the weapons were drawn).
  • Switching between a man and a woman keeps the sword, bow and quiver on the body (they stayed on
    the ground).
  • In first person her view stays level while she opens a door (it rolled and tilted).

Camera and keys

  • F5 steps through three third-person distances before going back to first person.
  • B (pointing) no longer draws the weapon.
  • Key bindings: a KCDS group holds push to talk, whisper/normal/shout, Point and Third person
    view, all of them free to change.

Settings

  • KCDS page in the game's settings, with its own title and headings: voice chat and the
    browser's volume, in one place.

Animations

  • An animation a script plays that has no clip for that body (a fragment with tags that match none)
    is refused at once: the body no longer stands with its arms spread until the script stops it.

Web pages

  • Screens in the world: a script puts a page on a screen in the world, in perspective or drawn
    into a screen model's texture, with its own pointer. Web.nearestWorldScreen finds the screen
    to focus, and Escape gives the mouse back. An address bar above the page shows any site.
  • Sound: pages play at the player's Browser volume, and the server sets each player's share with
    Player.webVolume and Player.webMuted.
  • Item icons: any page can show an item's inventory icon from kcds://icons/item/<name or GUID>.

World

  • Snow: the far forest is white too, and the grass comes back everywhere when the snow goes
    (places reached while it snowed stayed bare).
  • Doors: NPCs walk around a door a script keeps locked instead of waiting at it.
  • Dogs: the level's dogs run the game's own brain with levelPeople, and dogs walk a round.
  • The world's pace holds while a player is in the inventory or another game screen.
  • Fixed crashes: a dialogue with a person who has no stand-in, and another player leaving the server.

World Architect

  • Story states: the game's maps keep every state the campaign puts a place in (Nebákov's yard
    before and after the siege, a forge broken and rebuilt) as layers. The new Story tab lists the
    states of the places around the camera and switches each one on or off, so a map can mix them:
    one fortress before its siege, the village beside it after. The choice is kept with the work, in
    saves and in Export for server, so every player on the server sees the places that way.
  • Servers switch a story layer for all players of a dimension with
    LevelEdit.apply({ kind: 'layer', name, hidden }); players who join later get it too.
  • MCP: story_layers, set_story_state and set_story_layer.
  • To ground fits a thing's whole footprint on a slope (no corner floats), and the MCP has
    to_ground.

For scripts

  • Hud.setXpNotices: the game's own level and XP notices are off on KCDS until a script turns them
    on.
  • Npc.playVoice plays a voice line from an NPC's body; Npc.nameShown leaves its name out of the
    HUD's corner.
  • World.snapToGround(null, position): any ready player answers, and answers are kept.
  • Door.lock: the lock kind of any door (bolt, key, both or none).
  • Inventory.beforeCommit transactions keep a unique id and settle with
    playerInventoryTransaction.
  • Items.info names a registered item type; the Player screen's list takes settings of its own.
  • Runtime.apiVersion and serverVersion carry the KCDS version on both sides.

Server owners

  • Monitoring: GET /metrics gives Prometheus numbers (tick time, players, refused checks), and
    dynamic.json carries the server's health (tick time, missed ticks, CPU). A Grafana dashboard
    comes with the Docker files.
  • Favourites by address: players keep a private server as a favourite by its address; the game
    port answers its public card.
  • Resource files: many small files download at once, and icon checks no longer walk the resource's
    files each time.
  • The licence check reads the network interfaces once per 30 seconds, not on every join.
  • Proof of origin: gh attestation verify <file> --repo KCD-Synced/KCDS.

Downloads (public):

Unpack the Client zip anywhere and follow its README.txt.