Freven DevKit v0.1.0-rc8

Freven DevKit v0.1.0-rc8 is a prerelease focused on making the DevKit distribution model explicit, shippable, and less confusing for both Vanilla-based authors and zero-Vanilla standalone authors.

This release also updates the bundled engine, SDK, and Vanilla references and ships upload-ready Linux, Windows, and macOS Apple Silicon artifacts.

Highlights

First-class distribution profiles

The DevKit packaging flow now treats the main product shapes as separate, explicit profiles instead of one implicit Vanilla-shaped artifact:

• vanilla-product — first-party Freven Vanilla product and Vanilla mod/modpack author profile.
• host-foundation — zero-Vanilla authoring foundation for standalone custom-game shells.
• standalone-game-product — player-facing shipped standalone product profile.

The packaged manifests, generated READMEs, smoke checks, and sanity checks now enforce these boundaries so the profiles do not silently drift.

Related work:

• frevenengine/freven-boot#54
• frevenengine/freven-boot#55
• frevenengine/freven-boot#56
• frevenengine/freven-boot#58
• frevenengine/freven-boot#62

Zero-Vanilla standalone authoring path

This release adds a dedicated standalone shell authoring template and keeps it separate from the shipped standalone proof product.

Authors now have a clearer starting point for building a custom game shell without inheriting Vanilla payload or Vanilla builtins. The shipped standalone-game-product proof remains a player-facing/product validation artifact, not the canonical authoring scaffold.

Related work:

• frevenengine/freven-boot#57
• frevenengine/freven-boot#62

Runtime-loaded Wasm authoring guidance

The DevKit templates and SDK docs now include concrete examples for runtime-loaded Wasm mod layout, mod.toml shape, experience wiring, and config ownership.

In particular, runtime mod config is documented as experience-owned config, not mod.toml payload.

Related work:

• frevenengine/freven-boot#59
• frevenengine/freven-sdk#48

World bootstrap and vertical contract hardening

The engine, SDK, and boot flow now treat authored world shape as explicit bootstrap/world metadata truth instead of deriving vertical runtime contracts from observed terrain.

This improves custom terrain/worldgen support, especially for worlds that use non-default vertical bounds.

Related work:

• frevenengine/freven-sdk#47
• frevenengine/freven-engine#227
• frevenengine/freven-boot#49
• frevenengine/freven-boot#51

Singleplayer stream radius config fix

Singleplayer now loads the in-process server streaming policy from the same server.toml config path as dedicated servers.

This fixes the case where local singleplayer stream radius could still be clamped by old hardcoded/default server settings even when the instance config requested a larger radius.

Related work:

• frevenengine/freven-engine#231
• frevenengine/freven-boot#61

SDK worldgen authoring improvements

The SDK now includes worldgen output builders for safer and more efficient terrain write authoring.

Worldgen authors can build SetBlock, FillBox, and FillSection output through checked helper APIs without changing the canonical worldgen wire contract.

Related work:

• frevenengine/freven-sdk#50
• frevenengine/freven-sdk#52

Expanded client input contract

The SDK and engine now support a broader backend-neutral physical input surface for runtime and client gameplay code, including number keys, physical letter keys, side-specific modifiers, arrows, function keys, numpad keys, and extra mouse buttons.

Related work:

• frevenengine/freven-sdk#51
• frevenengine/freven-engine#232

Fixes and reliability

• Queued input is no longer cleared on redundant Play-state churn; strong input reset is now tied to real load/stream/player barriers.
• World streaming diagnostics now distinguish loading-gate progress from runtime view-radius negotiation.
• Singleplayer and dedicated server boot paths now share server runtime config parsing.
• Non-Vanilla packaged profiles no longer ship template guidance that assumes missing freven.vanilla payload or Vanilla builtins.
• Vanilla lockfile metadata was refreshed to match the updated SDK dependency graph.

Related work:

• frevenengine/freven-engine#230
• frevenengine/freven-engine#231
• frevenengine/freven-boot#61
• frevenengine/freven-boot#62
• frevenengine/freven-vanilla#22

Bundled dependency tags

• freven-engine: v0.1.3-rc5
• freven-sdk: v0.1.2-rc5
• freven-vanilla: v0.1.2-rc4
• freven-boot: devkit-v0.1.0-rc8

Artifacts

• Linux x86_64: freven-devkit-v0.1.0-rc8-x86_64-unknown-linux-gnu.tar.gz
• Windows x86_64: freven-devkit-v0.1.0-rc8-x86_64-pc-windows-msvc.zip
• macOS Apple Silicon: freven-devkit-v0.1.0-rc8-aarch64-apple-darwin.tar.gz

Each archive has a matching .sha256 file uploaded next to it.

Validation

This release was validated with:

• full engine workspace formatting, tests, clippy, layer checks, boundary checks, and invariant checks
• full SDK workspace formatting, tests, and clippy
• Vanilla workspace tests and clippy after lockfile refresh
• DevKit workspace formatting, tests, and clippy
• smoke packaging for:
  • DIST_PROFILE=vanilla-product
  • DIST_PROFILE=host-foundation
  • DIST_PROFILE=standalone-game-product
• release archive builds for:
  • x86_64-unknown-linux-gnu
  • x86_64-pc-windows-msvc
  • aarch64-apple-darwin
• checksum verification for uploaded archives

DevKit 0.1.0-rc7

Freven DevKit 0.1.0-rc7

0.1.0-rc7 is a DevKit pre-release focused on the new explicit experience stack workflow, stricter session/admission correctness, workload-scoped Wasm capability policy, and release packaging hardening.

This release supersedes the aborted 0.1.0-rc6 build attempt. The dependency set is the same as rc6, but rc7 includes the DevKit init/profile fix needed for clean release packaging.

Highlights

Explicit experience stack composition

DevKit instances can now use experience.stack.toml as the preferred way to compose a local experience on top of a base experience.

This is the new recommended workflow for small overrides such as changing defaults.worldgen without copying the whole base experience payload.

The stack model keeps composition explicit:

• standalone experience.toml remains first-class
• a stack explicitly selects a base experience
• instance-local stacks can override selected defaults
• base content, content.manifest, assets, and authored mod refs are inherited through the resolved composition model
• no implicit partial experience.toml inheritance or arbitrary TOML merge was added

This replaces the old “copy the full base experience just to change one field” workflow with a cleaner long-term composition path.

Authoritative session and admission hardening

The DevKit now consumes the newer authoritative-vs-optional session model from the engine.

Notable behavior:

• canonical load plans use explicit authoritative and optional-client-local session lanes
• join/session admission uses explicit authoritative admission keys
• optional client-local content does not widen authoritative compatibility
• authoritative dual-side runtime-loaded mods include exact artifact identity in admission
• finalized authoritative schema identity is folded into the same admission gate
• mismatches are rejected before play/loading instead of surfacing later

This is mainly important for multiplayer correctness and long-term mod safety.

Optional client-local policy surface

Boot/server/client configuration now has explicit policy handling for optional client-local content.

Server-side policy can reject optional client-local presence at startup, while client-side policy can request a clean-client path. These policies narrow admissibility, but they do not rewrite canonical authoritative truth.

Workload-scoped Wasm capability limits

Wasm capability policy is now split by workload instead of using one flat limit surface.

Interactive callbacks and worldgen providers are treated differently:

• lifecycle/tick/action/message callbacks stay under tight interactive limits
• declared worldgen providers can request larger worldgen-specific limits
• worldgen capability keys require a declared worldgen provider
• worldgen limits do not weaken hot-path interactive callbacks

This makes the Wasm model more practical for heavy worldgen without turning every callback into a high-budget execution path.

Client profile generation fixed for DevKit init

Client identity is no longer treated as static template content.

freven_boot init client now generates profile.toml per instance through the shared client profile owner. The release sanity checks also reject accidentally shipping a generated profile.toml inside the client template.

This keeps packaged templates clean while still making initialized client instances immediately runnable.

Worldgen and runtime architecture updates

This release includes the engine/SDK/Vanilla worldgen ownership and runtime updates from the pinned component set:

• volumetric-owned worldgen contracts
• typed volumetric addressing and terrain-write surfaces
• worldgen provider concurrency contract
• canonical host-owned async/worldgen execution direction
• initial world spawn hint contract and persisted initial spawn metadata
• startup warmup and runtime worldgen aligned around the same execution path

Release pipeline hardening

The release flow now has dedicated documentation and was exercised across all packaged targets.

Packaging now includes:

• pinned component tags through DEVKIT_DEPS
• release checklist documentation
• manifest generation
• archive checksums
• native smoke init/list checks
• upload-ready artifact layout
• validation that client templates do not ship generated player identity

Included component versions

• freven-boot: devkit-v0.1.0-rc7
• freven-engine: v0.1.3-rc4
• freven-sdk: v0.1.2-rc4
• freven-vanilla: v0.1.2-rc3

Artifacts

This release includes:

• Linux: x86_64-unknown-linux-gnu
• Windows: x86_64-pc-windows-msvc
• macOS: aarch64-apple-darwin

Validation

Verified during release prep and packaging:

• Boot workspace fmt, test, and clippy passed
• Linux release archive built successfully
• Windows x64 MSVC cross-build archive built successfully
• macOS arm64 release archive built successfully
• native smoke init/list checks passed on Linux
• native smoke init/list checks passed on macOS
• Windows archive sanity checks passed during cross-build
• archive SHA-256 files were generated and verified
• all six release assets were uploaded successfully

Notes

This is a pre-release intended for development, integration testing, and continued release-pipeline hardening before later stable DevKit releases.

The experience stack workflow is the preferred path for small instance-local overrides. Full standalone experience.toml authoring is still valid when creating a real replacement experience.

DevKit 0.1.0-rc5

Freven DevKit 0.1.0-rc5

0.1.0-rc5 is the first DevKit release line built around the canonical mod-architecture update across Boot, Engine, SDK, and Vanilla. This pre-release also rolls in the latest engine-side transport/security refresh and exercises the full multi-platform packaging pipeline.

Highlights

Canonical public mod architecture

This release aligns the DevKit with the canonical public guest contract and authoring model:

• unified guest contract surface for Wasm, native, and external guests
• canonical activation/load-plan flow
• canonical lifecycle, runtime service, provider-family, and observability semantics
• reference vanilla experience updated to the same architecture

Runtime parity across guest transports

Guest hosting behavior is now much closer across:

• Wasm guests
• native guests
• external guests

That includes registration flow, runtime services, provider-family hosting, message routing, session semantics, and observability/logging behavior.

Reference experience alignment

The bundled Vanilla reference experience now targets authoritative camera hit semantics and the unified public API shape, so the packaged example stack better reflects the intended long-term architecture.

Packaging and release hardening

The DevKit packaging flow was exercised and hardened for repeatable release work:

• pinned dependency release inputs
• multi-platform archive generation
• manifest and checksum output
• smoke initialization checks on native builds
• upload-ready artifact layout for GitHub Releases

Engine dependency refresh

This DevKit line includes the engine update to v0.1.3-rc3, which incorporates the quinn-proto 0.11.14 refresh.

Included component versions

• freven-boot: devkit-v0.1.0-rc5
• freven-engine: v0.1.3-rc3
• freven-sdk: v0.1.2-rc2
• freven-vanilla: v0.1.2-rc2

Artifacts

This release includes:

• Linux: x86_64-unknown-linux-gnu
• Windows: x86_64-pc-windows-msvc
• macOS: aarch64-apple-darwin

Validation

Verified during release prep:

• workspace check / clippy / test passed for the pinned release set
• Linux release archive built successfully
• Windows x64 cross-build archive built successfully
• macOS arm64 release archive built successfully
• smoke init/list checks passed on native Linux and macOS builds

Notes

This is a pre-release intended for development, integration testing, and release-pipeline hardening before later stable DevKit releases.

DevKit 0.1.0-rc2

Freven DevKit devkit-v0.1.0-rc2

Download the archive for your OS:

• Linux/macOS: .tar.gz
• Windows: .zip

Integrity:

• archive sha256: *.sha256

Bug reports:

• include freven_boot --version
• or attach manifest/devkit_manifest.toml from inside the archive.