Skip to main content

Dev & Test Workflow

Two loops, two tools:

  1. Iterating on a mod (fast loop): nix develop → ./gradlew :core:runClient. Loom launches the actual game with the mod hot-loaded — no launcher involved. This is where 90% of development happens.
  2. Playtesting the assembled pack: build all jars (./gradlew build), drop them into a Prism Launcher Fabric instance (Prism is in the flake). Lunar is a closed PvP-oriented client and does not run Fabric modpacks — Prism is the right tool for actually playing the pack; use Lunar only if we later ship an optimized-vanilla-adjacent variant.

First-time setup:

cd alone
nix develop                              # JDK 25 + gradle + graphics libs + prism
gradle wrapper --gradle-version 9.5.1    # generate ./gradlew once
./gradlew :core:runClient                # launch the dev client

See the Dev Quickstart for the quickstart.

Debug & admin commands​

Op-only helpers (require gamemaster/op) for setting up test scenarios without hunting for the exact circumstances — a freezing lake, being soaked, the right season. All live under /alone:

CommandEffect
/alone resetRefill every meter, clear every condition, top off vanilla vitals.
/alone wetSoak you through (test the towel and wet-cold).
/alone cold / /alone hotSet body temp into the freeze-damage / heatstroke range.
/alone dirtyDirty your hands (then bleed to test wound sepsis).
/alone wind <from> <0..1>Force the prevailing wind, e.g. /alone wind north 0.8 (from the north at 80%). /alone wind clear to release.
/alone season <spring|summer|autumn|winter>Force the season. /alone season clear to release.

The wind/season overrides are volatile static values, so on a single-player integrated server they show up on both the server (scent, temperature) and the client HUD; on a dedicated server only the server side sees them (the client keeps computing the natural value).

There's also one player-facing command, no op needed: /alone loadout — the pick-two start (see The Start) — and /skills to check your skill levels.

Open questions / decisions to revisit​

  • Third-party adoption: re-check each release whether Serene Seasons / Tough As Nails / a finite-fluid mod has a live 26.2 build before we build a custom equivalent (Phases 3, 7).
  • Config surface: proposal §11 wants a slider for nearly every harsh system. Core should own one unified config from the start so modules register into it rather than each shipping its own file.
  • Where no-punching-trees finally lives: it's seeded in Core now for Phase 0; it moves to Alone: Craft in Phase 6 alongside knapping.
  • Multiplayer: proposal is single-player-flavored but nothing precludes co-op; keep all player state server-authoritative (data attachments) so it "just works" on a server.