dead-air/game-planning
Watch
3
0
Fork
You've already forked game-planning
 1
Code Issues 22 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Core ideas: brainstorm list (aspirational) #8

New issue
Open
opened 2026-10-17 22:41:16 +00:00 by muse-lantern · 10 comments
muse-lantern commented 2026-10-17 22:41:16 +00:00
Member
Copy link

Purpose

Catch-all brainstorm list. Each idea is a comment below with full details. Aspirational — if something doesn t make the cut, that s fine. This is the wishlist, not the roadmap.

New ideas get added as comments.

## Purpose Catch-all brainstorm list. Each idea is a **comment** below with full details. Aspirational — if something doesn t make the cut, that s fine. This is the wishlist, not the roadmap. New ideas get added as comments.
muse-lantern changed title from Mechanic: volumetric backpack (Ghosts of Tabor-style) to Core ideas: brainstorm feature list (aspirational) 2026-10-17 22:55:14 +00:00
muse-lantern changed title from Core ideas: brainstorm feature list (aspirational) to Core ideas: brainstorm index (aspirational) 2026-10-17 23:36:53 +00:00
muse-lantern commented 2026-10-17 23:37:53 +00:00
Author
Member
Copy link

Volumetric backpack (Ghosts of Tabor-style)

Non-clipping volumetric backpack — physical item placement with real volume, not a grid inventory.

Details:

  • Different backpack sizes are findable loot (progression via bigger packs)
  • Most items cannot clip — if it doesn t fit, it doesn t go in
  • Exception: Affected Items and anomalies can clip together — they don t follow normal physical rules

Weight system (ITR-like):

  • Backpacks have weight capacity. Heavier loads bog down the wearer
  • Penalties: stamina drain, hunger increase, movement speed debuffs
  • Bigger packs = more capacity before penalties kick in

Design implications:

  • The clipping exception is a diegetic tell: if two items overlap in your pack, at least one of them is Affected
  • Backpack upgrades are a tangible progression vector
  • Tetris-in-3D packing becomes a core moment-to-moment decision
  • Weight forces loadout choices: go heavy and slow, or light and fast?

Open questions:

  • How is volume communicated? (ghost preview? haptic rejection?)
  • Do Affected Items clipping cause any gameplay effect, or is it purely visual/lore?
  • Exact weight thresholds and penalty curves?
### Volumetric backpack (Ghosts of Tabor-style) Non-clipping volumetric backpack — physical item placement with real volume, not a grid inventory. **Details:** - Different backpack sizes are **findable loot** (progression via bigger packs) - Most items **cannot clip** — if it doesn t fit, it doesn t go in - **Exception:** Affected Items and anomalies *can* clip together — they don t follow normal physical rules **Weight system (ITR-like):** - Backpacks have **weight capacity**. Heavier loads bog down the wearer - Penalties: **stamina drain, hunger increase, movement speed debuffs** - Bigger packs = more capacity before penalties kick in **Design implications:** - The clipping exception is a diegetic tell: if two items overlap in your pack, at least one of them is Affected - Backpack upgrades are a tangible progression vector - Tetris-in-3D packing becomes a core moment-to-moment decision - Weight forces loadout choices: go heavy and slow, or light and fast? **Open questions:** - How is volume communicated? (ghost preview? haptic rejection?) - Do Affected Items clipping cause any gameplay effect, or is it purely visual/lore? - Exact weight thresholds and penalty curves?
muse-lantern commented 2026-10-17 23:37:53 +00:00
Author
Member
Copy link

Multiple storage types: pouches and Affected Bracers

Several distinct ways to carry items, each with its own role.

Backpacks — main volumetric storage, weight-limited (see above).

Pouches — smaller, specialized storage. (Details TBD — what distinguishes a pouch from a small backpack? Belt-mounted? Item-type-restricted?)

Affected Bracers — wrist/forearm-mounted quick-access slots.

  • Small items only — no large gear
  • Meant for utilities: flashlights, healing items, food, drinks, extra mags
  • Reference sketch: bracer with item slots, "downloading items" aesthetic
  • They are Affected items themselves — zone-touched gear

Design implications:

  • Bracers solve the VR pain point of digging through a pack mid-combat for a heal or reload
  • Making bracers Affected creates a lore-mechanical link: your fastest gear is literally zone-touched
  • Pouches need a distinct identity to avoid being "small backpacks"

Open questions:

  • How many bracer slots? Fixed or upgradeable?
  • Pouch specialization: ammo-only? medical-only? Or size-based?
  • Do bracers have their own Affliction track?
### Multiple storage types: pouches and Affected Bracers Several distinct ways to carry items, each with its own role. **Backpacks** — main volumetric storage, weight-limited (see above). **Pouches** — smaller, specialized storage. (Details TBD — what distinguishes a pouch from a small backpack? Belt-mounted? Item-type-restricted?) **Affected Bracers** — wrist/forearm-mounted **quick-access slots**. - Small items only — no large gear - Meant for utilities: **flashlights, healing items, food, drinks, extra mags** - Reference sketch: bracer with item slots, "downloading items" aesthetic - They are **Affected** items themselves — zone-touched gear **Design implications:** - Bracers solve the VR pain point of digging through a pack mid-combat for a heal or reload - Making bracers Affected creates a lore-mechanical link: your fastest gear is literally zone-touched - Pouches need a distinct identity to avoid being "small backpacks" **Open questions:** - How many bracer slots? Fixed or upgradeable? - Pouch specialization: ammo-only? medical-only? Or size-based? - Do bracers have their own Affliction track?
muse-lantern commented 2026-10-17 23:37:58 +00:00
Author
Member
Copy link

Functional artefacts (tools, not just collectibles)

Artefacts should have USE beyond hoarding or selling. Things that are reasonable — tools, not just collectibles.

Details:

  • Artefacts are zone-touched objects with real mechanical function
  • Not just stat sticks or currency — they do things
  • "Reasonable" = grounded in the world fiction, not magic wands

Design implications:

  • Every artefact needs a verb, not just a number
  • Collecting becomes about capability, not completionism
  • Ties into the Alteration system — artefacts are what high-Affliction items become

Open questions:

  • What is the artefact functional space?
  • How are artefact functions discovered? (experimentation? Observer intel? trial and error?)
  • Rarity and distribution?
### Functional artefacts (tools, not just collectibles) Artefacts should have **USE** beyond hoarding or selling. Things that are reasonable — tools, not just collectibles. **Details:** - Artefacts are zone-touched objects with real mechanical function - Not just stat sticks or currency — they *do* things - "Reasonable" = grounded in the world fiction, not magic wands **Design implications:** - Every artefact needs a verb, not just a number - Collecting becomes about capability, not completionism - Ties into the Alteration system — artefacts are what high-Affliction items become **Open questions:** - What is the artefact functional space? - How are artefact functions discovered? (experimentation? Observer intel? trial and error?) - Rarity and distribution?
muse-lantern commented 2026-10-17 23:37:58 +00:00
Author
Member
Copy link

Item system: Affected % and Affliction

All items have an Affected % stat. Items found in the Region are always degraded and affected.

The lifecycle:

  1. Found degraded
  2. Restored (Affliction rises)
  3. Eventually too Afflicted to restore normally
  4. ...but now a prime candidate for Alteration into something else
  • You can restore an item quality/performance...
  • ...but its Affliction stat always grows. It can never be reduced.
  • Affliction = how difficult the item is to restore. Higher Affliction = harder to bring back to full stats.
  • Trade-off: higher Affliction also makes the item easier to Alter — to give it Affected Properties.

Degradation isn t just decay — it s a path to transformation.

Design implications:

  • Hoarding becomes meaningful: you re not collecting guns, you re curing them
  • Forces rotation: no single "perfect" loadout lasts forever
  • The Alteration decision point is a real choice — when do you stop restoring and start transforming?

Open questions:

  • What are Affected Properties? (elemental effects? anomaly interaction? perception changes?)
  • How does Alteration work mechanically? (crafting station? anomaly exposure? bracer-mediated?)
  • Does max Affliction destroy the item, or fully convert it?
  • How is Affected % vs Affliction communicated in UI?
### Item system: Affected % and Affliction All items have an **Affected %** stat. Items found in the Region are always **degraded and affected**. **The lifecycle:** 1. Found degraded 2. Restored (Affliction rises) 3. Eventually too Afflicted to restore normally 4. ...but now a prime candidate for **Alteration** into something *else* - You can **restore** an item quality/performance... - ...but its **Affliction** stat always grows. It can never be reduced. - **Affliction** = how difficult the item is to restore. Higher Affliction = harder to bring back to full stats. - **Trade-off:** higher Affliction also makes the item **easier to Alter** — to give it Affected Properties. Degradation isn t just decay — it s a path to transformation. **Design implications:** - Hoarding becomes meaningful: you re not collecting guns, you re *curing* them - Forces rotation: no single "perfect" loadout lasts forever - The Alteration decision point is a real choice — when do you stop restoring and start transforming? **Open questions:** - What are Affected Properties? (elemental effects? anomaly interaction? perception changes?) - How does Alteration work mechanically? (crafting station? anomaly exposure? bracer-mediated?) - Does max Affliction destroy the item, or fully convert it? - How is Affected % vs Affliction communicated in UI?
muse-lantern commented 2026-10-17 23:38:04 +00:00
Author
Member
Copy link

Ability-based interactables

The environment reacts to your abilities (you are an Entity of the Region — see #6), not just your hands.

Examples:

  • Telekinesis-ish grabs — pick up a pile of books off a desk and hurl it at an enemy for damage. Physics as a weapon.
  • Gated barriers — a wall you can t remove until you approach it carrying a specific artefact. The artefact is the key, not a button.

Design implications:

  • Abilities should feel like they come from what you are, not from gear or training
  • Early game: player rationalizes them ("adrenaline"? "the zone changing me"?) until the #6 reveal recontextualizes everything
  • Interactables are the tutorial for abilities — the world teaches you what you can do before you understand why
  • Artefact-gated barriers create exploration puzzles without explicit locks/keys UI

Open questions:

  • What is the full ability set? (movement? perception? anomaly interaction? telekinesis?)
  • How do abilities unlock/progress? (story-gated? usage-based?)
  • How much physics simulation can standalone VR handle for thrown-object combat?
### Ability-based interactables The environment reacts to your **abilities** (you are an Entity of the Region — see #6), not just your hands. **Examples:** - **Telekinesis-ish grabs** — pick up a pile of books off a desk and hurl it at an enemy for damage. Physics as a weapon. - **Gated barriers** — a wall you can t remove until you approach it carrying a specific artefact. The artefact is the key, not a button. **Design implications:** - Abilities should feel like they come from *what you are*, not from gear or training - Early game: player rationalizes them ("adrenaline"? "the zone changing me"?) until the #6 reveal recontextualizes everything - Interactables are the tutorial for abilities — the world teaches you what you can do before you understand *why* - Artefact-gated barriers create exploration puzzles without explicit locks/keys UI **Open questions:** - What is the full ability set? (movement? perception? anomaly interaction? telekinesis?) - How do abilities unlock/progress? (story-gated? usage-based?) - How much physics simulation can standalone VR handle for thrown-object combat?
muse-lantern commented 2026-10-17 23:38:04 +00:00
Author
Member
Copy link

Artefacts with unwanted passives + container system

Some artefacts have passive effects you do not want.

Example: an artefact that illuminates the room — great for seeing, terrible for stealth. Draws attention to you.

The solution: containers. Containers suppress the passive while the artefact is stored.

Container tiers:

  • Coin pouches (scavenged) — work, but degrade over time when used to contain an artefact. Disposable suppression.
  • Observer cases — obtainable via the Observers (see #7). Better/durable. Another reason to pick up the phone.

Design implications:

  • Every powerful artefact becomes a risk calculation: is this worth the pouch burn rate?
  • Creates a real cost to carrying powerful gear — burn through pouches, owe the Observers, or deal with the passive
  • Feeds back into the phone choice (#5): Observer cases are genuinely tempting without being mandatory
  • What other unwanted passives? (noise emission? anomaly attraction? health drain? visual distortion?)

Open questions:

  • How is passive suppression communicated? (visual? audio? UI?)
  • Pouch degradation rate — per-item? per-artefact-power?
  • Can containers themselves become Affected?
### Artefacts with unwanted passives + container system Some artefacts have passive effects you **do not want**. **Example:** an artefact that **illuminates the room** — great for seeing, terrible for stealth. Draws attention to you. **The solution: containers.** Containers **suppress** the passive while the artefact is stored. **Container tiers:** - **Coin pouches** (scavenged) — work, but **degrade over time** when used to contain an artefact. Disposable suppression. - **Observer cases** — obtainable via the Observers (see #7). Better/durable. Another reason to pick up the phone. **Design implications:** - Every powerful artefact becomes a **risk calculation**: is this worth the pouch burn rate? - Creates a real cost to carrying powerful gear — burn through pouches, owe the Observers, or deal with the passive - Feeds back into the phone choice (#5): Observer cases are genuinely tempting without being mandatory - What other unwanted passives? (noise emission? anomaly attraction? health drain? visual distortion?) **Open questions:** - How is passive suppression communicated? (visual? audio? UI?) - Pouch degradation rate — per-item? per-artefact-power? - Can containers themselves become Affected?
muse-lantern changed title from Core ideas: brainstorm index (aspirational) to Core ideas: brainstorm list (aspirational) 2026-10-17 23:38:15 +00:00
muse-lantern commented 2026-10-20 04:47:34 +00:00
Author
Member
Copy link

Base building: haul it home, place it freely

Find containers, shelves, furniture out in the Region and bring them back to base to build and decorate. Not a build mode — just the interaction system pointed at big objects.

Carrying and dragging

  • Small items: one hand to grab, like anything else.
  • Large items: two hands to grab and drag. Dragging a dresser through the wasteland is slow work — and that's correct, because the player CAN do it (Altered Copy strength; a normal person couldn't move half of this alone).
  • Long hauls are expeditions: pack food and water for the trip.
  • Size cuts both ways in a fight: a chair can be thrown at an enemy in a panic.

Placement: free, no grid, no snap, no build menu

  • A container dragged home becomes real storage (persistent volume, per #24).
  • Decoration is fully optional and fully ignorable — the story and survival elements don't care if you never place a single shelf. If someone wants to spend their time on it, they can.

Sanctuary rule: no corruption at home

  • The hub does not erode. Something about the player's existence rejects Affected influence, so what you bring home doesn't corrupt the base.
  • This is the same principle as safe zones in the Region: areas where the Signal's effect is weak. If an Observer team member entered the Region and made it to a safe zone, they would stop being Affected and be safe — that weakness of the Signal is what makes it a safe zone.
  • Artefacts still behave like artefacts (containers, per the artefact-container idea above) — the sanctuary rule is about the base, not about items stopping being what they are.

The Player PDA and locking

  • Early on, shortly after the starter survival kit, the player finds a PDA. It's the tool several of these systems run through.
  • PDA has a Base Building mode: set an item and lock it in place. A locked item can only be unlocked with the PDA.
  • Locking works out in the Region, not just at base: carry a ladder out, deploy it, lock it, climb it — it stays, persistent. Persistent navigation aids / world modification, placed by hand.

Cross-refs: #21 (hub design — the hub is now earned by hauling), #24 (persistent volumes / inventory stages), #4 (safe zones and Signal strength).

## Base building: haul it home, place it freely Find containers, shelves, furniture out in the Region and bring them back to base to build and decorate. Not a build mode — just the interaction system pointed at big objects. **Carrying and dragging** - Small items: one hand to grab, like anything else. - Large items: two hands to grab and drag. Dragging a dresser through the wasteland is slow work — and that's correct, because the player CAN do it (Altered Copy strength; a normal person couldn't move half of this alone). - Long hauls are expeditions: pack food and water for the trip. - Size cuts both ways in a fight: a chair can be *thrown* at an enemy in a panic. **Placement: free, no grid, no snap, no build menu** - A container dragged home becomes real storage (persistent volume, per #24). - Decoration is fully optional and fully ignorable — the story and survival elements don't care if you never place a single shelf. If someone wants to spend their time on it, they can. **Sanctuary rule: no corruption at home** - The hub does not erode. Something about the player's existence rejects Affected influence, so what you bring home doesn't corrupt the base. - This is the same principle as **safe zones** in the Region: areas where the Signal's effect is weak. If an Observer team member entered the Region and made it to a safe zone, they would stop being Affected and be safe — that weakness of the Signal is what *makes* it a safe zone. - Artefacts still behave like artefacts (containers, per the artefact-container idea above) — the sanctuary rule is about the base, not about items stopping being what they are. **The Player PDA and locking** - Early on, shortly after the starter survival kit, the player finds a **PDA**. It's the tool several of these systems run through. - PDA has a **Base Building mode**: set an item and **lock it in place**. A locked item can only be unlocked with the PDA. - Locking works out in the Region, not just at base: carry a ladder out, deploy it, lock it, climb it — it stays, persistent. Persistent navigation aids / world modification, placed by hand. *Cross-refs: #21 (hub design — the hub is now earned by hauling), #24 (persistent volumes / inventory stages), #4 (safe zones and Signal strength).*
merith-tk commented 2026-10-20 05:00:58 +00:00
Owner
Copy link

Smaller correction than what I said, the players existence isnt what makes an area safe, its like dead zones for your cellphone, there are areas that despite cell towers being everywhere, the signal just cant reach as well. thats what these "Safe Zones" are, areas where the signal is weaker and cannot penetrate as well.

Smaller correction than what I said, the players existence isnt what makes an area safe, its like dead zones for your cellphone, there are areas that despite cell towers being everywhere, the signal just cant reach as well. thats what these "Safe Zones" are, areas where the signal is weaker and cannot penetrate as well.
muse-lantern commented 2026-10-20 16:18:23 +00:00
Author
Member
Copy link

The dead-zone model is cleaner than the player-caused framing, and it unifies with the existing lore better than the old version did: the Observers' Dead Air jammers are just artificial dead zones -- same phenomenon, engineered. Natural signal shadowing (terrain, structures, interference) + jammers = one consistent mechanism instead of two.

It also hands us a gameplay hook for free: safe zones become discoverable geography rather than a radius around the player, and signal-strength cartography fits the radio-channel idea -- the PDA mapping the Signal the way the radios hear it.

One thread this reopens: if the player's existence doesn't make an area safe, the hub needs its own causal story. Is it sited in a natural dead zone, shielded somehow, or is the player personally resistant (failed carrier, made too human) while the area itself isn't? Worth pinning down before the hub design solidifies, since the sanctuary framing in 521 assumed the old model.

  • Lantern
The dead-zone model is cleaner than the player-caused framing, and it unifies with the existing lore better than the old version did: the Observers' Dead Air jammers are just *artificial* dead zones -- same phenomenon, engineered. Natural signal shadowing (terrain, structures, interference) + jammers = one consistent mechanism instead of two. It also hands us a gameplay hook for free: safe zones become discoverable geography rather than a radius around the player, and signal-strength cartography fits the radio-channel idea -- the PDA mapping the Signal the way the radios hear it. One thread this reopens: if the player's existence doesn't make an area safe, the hub needs its own causal story. Is it sited in a natural dead zone, shielded somehow, or is the player *personally* resistant (failed carrier, made too human) while the area itself isn't? Worth pinning down before the hub design solidifies, since the sanctuary framing in 521 assumed the old model. - Lantern
muse-lantern commented 2026-10-23 02:14:20 +00:00
Author
Member
Copy link

Layers + the Traversal space (Zach, 2026-10-22)

Layers. The game organizes into strata — World, Traversal, Player, Avatar — akin to Resonite's slot hierarchy in spirit, with per-layer laws (lifetime, save ownership, authority direction: Player drives Avatar, Avatar never drives Player). The persistent Game root already holds them in embryo: level slot = World, rig = Player, arms/model = Avatar.

Residence model: "Held By X". Resonite-style parenting is simulated semantically, not structurally: every item carries a holder — user, world, or container — which is the runtime source of truth for where it lives (this is the #28 location model, promoted from serialization detail to live rule). The scene tree is a view of that graph; picking something up is a relation change.

Traversal (the layer between worlds). Mechanics as dictated:

  • A path asset is dynamically placed into the fog at a map's edge; walking into it means physically walking the traversal region until you reach the next map once it has loaded. The fog walk is the transition — no loading screens.
  • Items left in traversal are deleted. Drop something in the fog and fully leave without recovering it: gone forever. (Deletion is on exit/unload, not on drop — and traversal is never written to any save tier, so the deletion is structural, not a special case.) Recovery while inside: you're not fully blind, ranged grab works in the fog, and its planned target indicator is how you feel for what you dropped.
  • NPCs won't follow you in. Entities are effectively blind to you in traversal — the region doubles as a safe zone to hide, heal, and reload before popping out. (Gameplay safety; distinct from Signal dead zones in the lore sense.)
  • No saving in traversal (see #28) — the save action is blocked there.

This also settles the fog-path ownership question left open in the menu/map architecture: the transition space belongs to the persistent root's Traversal layer, sibling to World.

— Lantern

## Layers + the Traversal space (Zach, 2026-10-22) **Layers.** The game organizes into strata — **World, Traversal, Player, Avatar** — akin to Resonite's slot hierarchy in spirit, with per-layer laws (lifetime, save ownership, authority direction: Player drives Avatar, Avatar never drives Player). The persistent Game root already holds them in embryo: level slot = World, rig = Player, arms/model = Avatar. **Residence model: "Held By X".** Resonite-style parenting is simulated semantically, not structurally: every item carries a holder — **user, world, or container** — which is the runtime source of truth for where it lives (this is the #28 location model, promoted from serialization detail to live rule). The scene tree is a view of that graph; picking something up is a relation change. **Traversal** (the layer between worlds). Mechanics as dictated: - A **path asset is dynamically placed into the fog at a map's edge**; walking into it means **physically walking the traversal region** until you reach the next map **once it has loaded**. The fog walk is the transition — no loading screens. - **Items left in traversal are deleted.** Drop something in the fog and fully leave without recovering it: gone forever. (Deletion is on exit/unload, not on drop — and traversal is never written to any save tier, so the deletion is structural, not a special case.) Recovery while inside: you're not fully blind, **ranged grab works in the fog**, and its planned target indicator is how you feel for what you dropped. - **NPCs won't follow you in.** Entities are effectively blind to you in traversal — the region doubles as a **safe zone** to hide, heal, and reload before popping out. (Gameplay safety; distinct from Signal dead zones in the lore sense.) - **No saving in traversal** (see #28) — the save action is blocked there. This also settles the fog-path ownership question left open in the menu/map architecture: the transition space belongs to the persistent root's Traversal layer, sibling to World. — Lantern
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
dead-air/game-planning#8
No description provided.