kronic/Project-M
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs

Browse Source
This commit is contained in:
Luis Gonzalez
2026-06-13 00:00:50 -07:00
parent 49cdec3a1e
commit 42691e5431
1 changed files with 361 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Docs/Vault/06_Roadmap/End_Of_Month_Game_Jam_Slice.md
+361
View File
@@ -0,0 +1,361 @@
---
tags:
- roadmap
- demo
- game-jam
- slice
- art-direction
- combat
- base-defense
status: active
updated: 2026-06-13
permalink: gamevault/06-roadmap/end-of-month-game-jam-slice
---
# End-of-Month Game Jam Slice
## Decision
Build **Awakening Engine Last Stand** as the end-of-month playable slice.
This is a compact top-down ARPG / survival-action base-defense demo. The player mines Ore near the base, builds a small defense, converts Ore into Charge, survives escalating Husk waves, and either holds the Awakening Engine through a final siege or gets overrun.
The goal is not to prove the whole future game. The goal is to finish a small, fun, visually cohesive slice that makes the strongest existing systems feel like one game.
## Why This Direction
The project is currently strongest when combat, base, and economy are braided together on one screen:
- Dash and melee already form the best moment-to-moment action verb.
- Base-local mining already gives the player something to do before and between sieges.
- Turrets, walls, Fabricator, Charge, structure HP, and Core integrity already create stakes.
- The HUD, live tuning, wave director, and feedback systems are usable enough to polish around.
- The recent implementation velocity supports tuning and composition better than building a new mode.
The project is weakest when it tries to be broad: expedition, automation chains, inventory, equipment, multi-region world dressing, and narrative mystery all compete for attention. They can remain in the project, but they should not be foregrounded for this slice.
## Demo Pitch
> A Sleeper wakes inside a failing Aether colony outpost. Mine Ore from the perimeter, power the Fabricator, feed the turrets, and hold the Awakening Engine against a Husk siege long enough to stabilize the core.
## Target Experience
The slice should feel like:
- A readable top-down ARPG combat arena.
- A small defend-the-core survival scenario.
- A compact Riftbreaker-like base-defense loop without broad factory complexity.
- A dark sci-fi frontier outpost where cyan ordered Aether fights orange-red wild Aether.
It should not feel like:
- A systems showcase.
- A large survival/crafting prototype.
- A broad expedition adventure.
- A menu-heavy progression demo.
- A pretty asset test with no strong loop.
## Core Loop
1. Start in Calm at the Awakening Engine.
2. Mine nearby Ore crystals with melee or ranged attacks.
3. Spend Ore on a Fabricator, turret, and walls.
4. Fabricator converts Ore into Charge.
5. Turrets consume Charge during the siege.
6. Husks attack structures first, then breach the Core if not stopped.
7. Survive the final siege to win, or get overrun and lose resources / fail the run.
## Minimum Feature Set
The end-of-month demo should include only these foreground features:
- Player movement, dash, melee combo, and secondary ranged poke.
- Ore mining at the base.
- Build palette with Turret, Wall, and Fabricator.
- Charge economy: Ore -> Fabricator -> Charge -> turret shots.
- Scheduled waves plus a final siege.
- Destructible structures.
- Engine Core integrity and overrun state.
- Clear win condition and clear loss/overrun condition.
- Basic save/continue only if it already works without extra polish.
Everything else is optional background or cut.
## Minimum Asset List
Required visible assets:
- **Awakening Engine / Core:** the brightest hero object in the arena.
- **Ore crystal:** readable from the top-down camera and clearly harvestable.
- **Turret:** one clear silhouette, cyan owned read, obvious firing direction.
- **Wall:** simple defensive barrier, lower visual priority than enemies/core.
- **Fabricator:** recognizable machine, cyan active state, no complex animation required.
- **Player:** readable cyan/neutral silhouette, visible facing and attack arc.
- **Grunt Husk:** orange-red hostile read.
- **Charger Husk:** larger/different silhouette with a readable telegraph.
- **Enemy spawn marker/rift:** shows where waves enter.
- **Ground/arena kit:** dark, quiet, low-detail surface with a few lane/edge markers.
- **Perimeter props:** 5-10 repeated dark sci-fi/natural-frontier props to frame the arena.
Optional if fast:
- Small cyan cables/veins from Core to machines.
- Orange corruption decals near enemy lanes.
- A few low cover rocks or broken colony pieces.
- Core state changes as integrity drops.
## Visual Direction
Use **Aether Siege Outpost**.
### Mood
Dark, readable, high-contrast frontier sci-fi. The base should feel like a tiny engineered foothold holding back a hostile wild field.
### World Feel
The world should read as a small industrial clearing, not a broad meadow. Nature can exist, but it is background texture. The gameplay identity is the Engine, the machines, the perimeter, and the corrupted attacks.
### Palette
- Cyan / teal: player, owned structures, Core, ordered Aether, build affordances.
- Orange / red: Husks, telegraphs, damage, corruption, danger.
- Amber: Ore and build costs.
- Violet: Charge resource.
- Neutral dark greens / greys: ground, rocks, inactive props, perimeter.
The ground must stay quieter than the actors. If the terrain, fog, or boundary ring pulls more attention than the player, enemies, Core, or Ore, it is wrong for the slice.
### Camera
Use a closer ARPG framing than the wide biome screenshots.
Camera goals:
- Player, enemies, Core, and one or two defensive structures should be readable at the same time.
- Combat spacing should be visible without making actors tiny.
- The Core should remain the compositional anchor near the center of the arena.
- Avoid giant empty ground fields.
- Avoid huge perimeter silhouettes blocking readability.
### Lighting and Post
Use lighting and post-processing to unify assets:
- Darker ground and props.
- Stronger cyan/orange emissive gameplay reads.
- Moderate bloom only on Aether and attacks.
- Fog should create depth, not wash out silhouettes.
- Avoid beige, flat daylight, and low-contrast haze for the demo.
## Asset Workflow
Use **Synty assets with strict art rules plus lighting/material/post-processing unification**.
Do not switch to a Blender-first workflow for the jam slice. Blender can be used for tiny fixes or one hero prop, but not as the production backbone before the end of the month.
### Day-to-Day Workflow
1. Pick a small allowed asset set before placing anything.
2. View every candidate asset from the actual gameplay camera.
3. Assign it one gameplay role: core, defense, resource, enemy, lane, boundary, or background.
4. Re-material/tint it into the slice palette.
5. Place it in the compact arena.
6. Test whether it improves readability in motion.
7. Delete it if it does not serve the slice.
### Allowed Asset Approach
- Prefer Synty SciFiSpace, SciFiCity, Generic, Mech, selected FantasyKingdom siege pieces, and selected Nature/NatureBiomes ground or rocks.
- Use FantasyKingdom pieces only when they can read as colony defense after tinting/material treatment.
- Avoid mixing cozy village, carnival, western, vikings, dungeon, or decorative fantasy props unless they are deliberately recontextualized and visually quiet.
- Use GabrielAguiar / Synty VFX sparingly for hit, dash, turret fire, core overrun, and final win/loss.
### Consistency Rules
- Every owned object must have cyan ordered-Aether accents.
- Every enemy object/effect must have orange-red wild-Aether accents.
- Neutral props should be dark and desaturated.
- No tall or noisy props inside combat lanes.
- No asset should be more visually important than the Core unless it is an active enemy or attack.
- Keep object scale consistent with player readability, not with source-pack defaults.
- Reuse a few assets well instead of placing many packs badly.
## What To Cut For This Slice
Do not work on these before the jam demo:
- Expedition loop polish.
- Full dungeon/room sequence.
- Boss or miniboss.
- New enemy faction.
- Deep inventory/equipment progression.
- Tool-gated harvesting.
- Conveyor/harvester automation presentation.
- Broad recipe economy.
- Full narrative system or voiced Echo.
- New Blender asset pipeline.
- Pixelated/toon/downsample render experiments beyond small tests.
- More asset-pack imports.
- Co-op-specific UX polish beyond what already works.
- Large world/biome redo.
## Visual Cohesion Checklist
Use this checklist every time the scene changes:
- Can the player, enemy, Core, turret, Ore, and danger telegraph be identified within one second?
- Is the Core the hero object, not the boundary ring or background props?
- Are enemies visible without relying only on particles?
- Is the ground darker and quieter than actors, attacks, and resources?
- Are cyan and orange-red used consistently as owned vs hostile Aether?
- Does every prop have a gameplay or composition job?
- Is the camera close enough for combat, but wide enough for dash spacing?
- Are tall props kept out of lanes and away from the player silhouette?
- Does the HUD support the action instead of overwhelming it?
- Does the scene still read in a screenshot with no motion?
## Done Definition
The demo is done when a new player can:
- Start a run from the menu or game scene.
- Understand that the Core must be defended.
- Mine Ore near the base.
- Build at least one Fabricator, turret, and wall.
- See Charge feed turret fire.
- Fight Grunts and Chargers with melee/dash.
- Lose structures and understand why it matters.
- See the Core take damage if enemies breach.
- Reach a final siege.
- Win by surviving or lose/get overrun clearly.
- Finish the run in 5-8 minutes.
The slice should be considered successful if it feels coherent and replayable even with only one arena.
## Milestone Plan
### June 13-15: Scope Lock and Arena Cleanup
- Lock this document as the working target.
- Make one compact base-defense arena.
- Remove or hide visual noise that does not support the slice.
- Reduce the visible asset vocabulary.
- Make the Core the focal point.
- Set the camera framing target.
### June 16-19: Loop Tuning
- Tune Ore amount, build costs, Fabricator rate, Charge consumption, turret strength, wall HP, and wave size.
- Verify the player naturally mines, builds, fights, repairs/rebuilds, and defends.
- Tune Grunt/Charger mix for readability and pressure.
- Make failure possible but not abrupt.
### June 20-23: Visual Cohesion Pass
- Darken and quiet the ground.
- Add clear enemy lanes and spawn reads.
- Unify owned structures with cyan accents.
- Unify Husks, telegraphs, and danger effects with orange-red.
- Reduce fog/haze if it hurts silhouettes.
- Improve Core, Ore, turret, and Fabricator silhouettes.
### June 24-26: Final Siege and Ending
- Add or tune the final siege.
- Add clear victory state.
- Add clear overrun/loss state.
- Keep messaging minimal and readable.
- Ensure the run has a beginning, middle, and end.
### June 27-29: Polish and Cut
- Play the whole run repeatedly.
- Cut confusing mechanics.
- Fix camera/HUD readability problems.
- Tune feedback: hit, dash, turret fire, structure break, Core breach, win/loss.
- Capture screenshots and compare against the visual checklist.
### June 30: Package
- Produce a playable build or reliable play path.
- Do not add new systems.
- Fix only blockers, readability issues, and major feel problems.
## Future Work / Expansion After The Jam
If the slice works and the project continues, expand from the proven core instead of reopening the whole project at once.
### First Expansion: Stronger Combat Depth
- Add one ranged enemy that forces repositioning.
- Add one heavy enemy or elite that tests dash timing.
- Add a clearer player secondary/special attack.
- Add enemy death animations or stronger hit reactions.
- Add better combat audio identity.
### Second Expansion: Better Base Identity
- Make the Awakening Engine visually evolve as it charges.
- Add repair/rebuild decisions after sieges.
- Add a small number of meaningful structure upgrades.
- Add clearer machine states: powered, dry, damaged, destroyed.
- Add diegetic cables, Aether veins, or power flow from Core to machines.
### Third Expansion: Expedition Reintroduction
Only reintroduce expeditions after the base-defense slice is fun.
The expedition should have one clear purpose:
- Gather a special resource.
- Trigger a stronger retaliation.
- Unlock a new defense option.
- Reach a mini-objective and return.
Do not reintroduce it as a second full game mode until the base loop is proven.
### Fourth Expansion: Automation Depth
Bring back conveyors/harvesters only when they create visible, tactical pressure.
Good automation expansion:
- Machines create combat resources.
- Machines can be attacked.
- Machine layout changes defense choices.
- Output is visible and immediately useful.
Bad automation expansion:
- Hidden ledger numbers.
- Broad recipes without combat consequence.
- Factory optimization detached from sieges.
### Fifth Expansion: Art Pipeline
After the jam, decide whether to continue with:
- Strict Synty kitbash plus custom materials.
- Synty blockout with custom Blender hero assets.
- A custom low-poly Blender kit.
- A toon/outline/pixelated render style.
Do this after the playable slice, not before it. The slice should reveal which assets deserve custom treatment.
### Sixth Expansion: Narrative and Progression
Add narrative only where it supports the loop:
- Core charge milestones reveal memory fragments.
- The Echo comments on first mine, first build, first siege, first overrun, and first win.
- THEM / Wellspring mystery becomes the long-term goal.
- Equipment and inventory become rewards for combat survival, not menu clutter.
Narrative should be light, atmospheric, and tied to run progress.
## Guiding Rule
When in doubt, choose the option that makes the 5-minute defend-the-Core run clearer, more readable, and more satisfying.
Everything else can wait.