Packward / Modpack operations
Working Theory / First product
In development
See the whole pack.Change it with confidence.
Packward turns a modded Minecraft server into a readable, testable system: inventory, dependencies, proposed changes, recovery points, and deployment in one local workflow.
No public build is available yet. A download will only appear when release metadata confirms a verified installer.
- Windows 11
- Local-first
- Fabric first
- In development
Overview / The system model
A modpack is a system, not a pile of files.
Every installed mod participates in a runtime: loaders, target sides, dependencies, configuration, update paths, and the server process itself.
Packward reads those relationships together. The overview holds current health, installed files, client and server boundaries, update pressure, pending operations, and deployment history in one working context.
Arcadia / demonstration scan
- Runtime
- Fabric 1.21.1
- Installed
- 21 demo mods
- Relationships
- 11 mapped links
- Findings
- 2 open for review
- Pending
- 2 approval-gated changes
- History
- Staged, tested, and applied operations
Inventory / Exact files
One manifest for every installed file.
Packward connects the file on disk to its installed version, target side, authorship, category, dependency links, and compatible catalogue releases. Coordinated requirements stay visible beside the file that creates them.
- Identity
- Installed files matched to exact catalogue entries
- Boundaries
- Client, server, and shared targets remain explicit
- Relationships
- Dependency links stay attached to the manifest
- Versions
- Available releases are evaluated against the current pack
Compatibility / Before the edit
Compatibility before change.
The dependency atlas shows installed and target versions as a connected graph. Recommendations carry the local relationship and catalogue evidence needed to explain why one file cannot safely move alone.
Arcadia case / Waystones + Balm
The next version changes the relationship.
Arcadia’s installed pair is healthy. The available Waystones release declares a newer Balm range, so Packward groups both files into one proposed operation instead of recommending a partial update.
- Installed
- Waystones 21.1.5 / Balm 21.0.20
- Target
- Waystones 21.1.7 / Balm 21.0.22
- Decision
- Review one coordinated change
Changes / Approval boundary
AI suggestions become reviewable operations.
Packward can help interpret an intended change, but it does not let a model silently alter a live server. Suggestions are grounded in the actual pack, grouped into a coherent operation, and held for explicit approval with a recovery requirement.
From intent to reversible operation
Describe the intended server change.
Inspect the local server and catalogue evidence.
Group dependent files into one coherent operation.
Hold the proposal at an explicit approval boundary.
After approval, create a recovery point and stage the operation for isolated testing.
Deployment / Verified return
Deploy behind a recovery boundary.
A staged change becomes a controlled server procedure. Packward keeps the prior state recoverable, resolves the final manifest, publishes the intended files, restarts the server, and checks the returning runtime before the operation is settled.
Controlled deployment sequence
Recovery point
Manifest resolved
Files published
Server restarted
Health verified
Arcadia / post-deploy observations
- Tick rate
- 20.0 TPS
- Median tick
- 12.4 ms
- Memory
- 4.8 GB
- Players
- 8 online
- Regression
- None detected in the observation window
Product principles / Operating constraints
Confidence comes from boundaries you can inspect.
Packward is being built as a local operations instrument. These constraints define what its recommendations and deployment workflow must preserve.
- 01
Local-first
Server files and working context remain on the operator’s machine.
- 02
Evidence before action
Recommendations identify the files, versions, and relationships behind them.
- 03
Reversible operations
Changes carry an approval state and a recovery boundary.
- 04
Exact dependency awareness
Coordinated requirements are resolved as one system change.
- 05
Isolated testing
Staged changes can be checked away from the live server before deployment.
- 06
Honest release status
Development status remains visible until a public installer is verified.
Current technical facts
- Platform
- Windows 11 desktop
- Loader support
- Fabric first; Quilt, Forge, and NeoForge recognised
- Version
- 0.1.0, in development
- Privacy
- Local-first; worlds are never read or uploaded
- Release
- No verified public build
Current status / In development
Follow the work, not a placeholder download.
Packward does not have a verified public installer yet. Follow Working Theory for development progress; this page will only expose a download when release metadata confirms one.
Local-first. Packs and worlds remain on the operator’s machine.