BUILD / Stages 04–05

Examples and resources

Use focused examples as executable documentation and keep official and community sources distinct.

On this page

Choose a section or expose the complete guide.

01

Understand the native library and plugin surface behind RE_Kenshi extensions.

KenshiLib

KenshiLib is the native library used by RE_Kenshi extensions to interact with Kenshi systems. The official repository and examples are the authority for its current interfaces and working patterns.

Use the examples as executable documentation: begin from the smallest project that demonstrates the system you need, confirm it unchanged, then make one observable modification at a time.

02

Move from HelloWorld into focused UI, state, data, API, and rendering examples.

Example map

After HelloWorld, move through focused examples instead of starting with a large plugin:

  1. KillButton / MyGUI — UI and event handling.
  2. Dialogue + GameData — game data and FCS-paired behavior.
  3. Persistent WorldStates — data that survives across play state.
  4. Plugin Import / Export — inter-plugin APIs.
  5. Materials + Shaders — rendering-facing experiments.

The official examples repository remains authoritative for the exact project list and build notes.

03

Build-oriented source and distribution destinations for public RE_Kenshi work.

Public extension map

Gameplay External listing

Direct Control

by SmokeFoolius

Adds direct WASD movement and a first-person perspective while retaining Kenshi's tactical systems.

Framework extension External extension

KenshiExtensionPlugin

by Lucius64

A community RE_Kenshi plugin that provides additional fixes and functionality for Kenshi.

Developer resource Official examples

KenshiLib Examples

by BFrizzleFoShizzle

Official examples covering UI, dialogue, persistent world state, plugin APIs, and more.

04

Keep native experiments small, observable, and source-aware.

Working practices

Keep a working Release/x64 HelloWorld build available as a control. Add one system at a time, log the important lifecycle events, and separate FCS data from native behavior clearly.

Link users to author-owned releases and compatibility notes. Do not treat a successful local experiment as a general compatibility guarantee, especially when mixing native extensions.

05

Distinguish official project sources from community-tested supplements.

Upstream references

Use the official KenshiLib, KenshiLib Examples, dependencies, and HelloWorld sources for project requirements and current code. The RE_Kenshi repository and wiki describe the loader and framework behavior.

The Weisspure working solution is labeled as a community-tested supplement. It can help compare a working filesystem or solution, but it does not override BFrizzleFoShizzle’s repositories.