How ges233/variationsofyesterday works
Variations of Yesterday is an experimental Minecraft mod centered on a tick-driven ecological Mandate Engine. Server lifecycle hooks start the engine; active-player ticks enter an actor as events, which update a spatial stress lattice and publish snapshots. A development-only client HUD reads those snapshots. The action channel and inbound event types establish extension points, but no gameplay event producers or action producers are shown. README feature detail is minimal, so this map reflects the implemented prototype; several edges are grounded in the sampled implementation excerpts.
Main entry points: MandateRuntime.scala Engine Runtime · MandateAgent.scala Mandate Actor · MandateState.scala Cell Dynamics · MandateHud.scala Mandate HUD
Components 13
Game Integration
- Mod Initializer
src/main/scala/moe/chestnut/awa/voy/VariationsOfYesterday.scala - Engine Runtime
src/main/scala/moe/chestnut/awa/voy/MandateRuntime.scala
Mandate Engine
- Event Protocol
src/main/scala/moe/chestnut/awa/voy/inner/event/EventMsg.scala - Action Protocol
src/main/scala/moe/chestnut/awa/voy/inner/action/ActionMsg.scala - Mandate Actor
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateAgent.scala
Simulation Model
- Stress Lattice
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateGrid.scala - Cell Dynamics
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateState.scala - ODE Solver
src/main/scala/moe/chestnut/awa/voy/helpers/ODESolver.scala - Plant Data
src/main/scala/moe/chestnut/awa/voy/inner/plant/PlantDTO.scala
Client View
- Client Initializer
src/client/scala/moe/chestnut/awa/voy/VariationsOfYesterdayClient.scala - Mandate HUD
src/client/scala/moe/chestnut/awa/voy/hud/MandateHud.scala
Other components
- Player
- Minecraft Server
Connections 16
- Minecraft Server → Mod Initializer: fires lifecycle
src/main/scala/moe/chestnut/awa/voy/VariationsOfYesterday.scala - Mod Initializer → Engine Runtime: starts and ticks
src/main/scala/moe/chestnut/awa/voy/VariationsOfYesterday.scala - Engine Runtime → Minecraft Server: reads tick state
src/main/scala/moe/chestnut/awa/voy/MandateRuntime.scala - Engine Runtime → Event Protocol: sends tick
src/main/scala/moe/chestnut/awa/voy/MandateRuntime.scala - Engine Runtime → Mandate Actor: creates actor
src/main/scala/moe/chestnut/awa/voy/MandateRuntime.scala - Mandate Actor → Event Protocol: handles messages
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateAgent.scala - Mandate Actor → Stress Lattice: steps lattice
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateAgent.scala - Stress Lattice → Cell Dynamics: advances cells
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateGrid.scala - Cell Dynamics → ODE Solver: integrates equations
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateState.scala - Mandate Actor → Engine Runtime: publishes snapshot
src/main/scala/moe/chestnut/awa/voy/MandateRuntime.scala - Mandate Actor → Action Protocol: emits actions
src/main/scala/moe/chestnut/awa/voy/inner/mandate/MandateAgent.scala - Engine Runtime → Action Protocol: drains queue
src/main/scala/moe/chestnut/awa/voy/MandateRuntime.scala - Client Initializer → Mandate HUD: registers in development
src/client/scala/moe/chestnut/awa/voy/VariationsOfYesterdayClient.scala - Mandate HUD → Engine Runtime: reads chunk state
src/client/scala/moe/chestnut/awa/voy/hud/MandateHud.scala - Player → Mandate HUD: views overlay
- Plant Data → Cell Dynamics: models plant