History

VinPropane 3882b0e2c6 NS-16: MoveCommand → server PositionState, Godot sync, tests Implement E1.M1 intent → authority: POST /game/players/{id}/move with v1 JSON MoveCommandRequest (snap + sequence), extend in-memory store and PositionStateApi. Godot client splits ground_pick and position_authority_client with thin main.gd; snap_to_server on player. Tests live under NeonSprawl.Server.Tests/Game/PositionState/ with AAA layout and MethodName_ShouldExpectedOutcome_WhenScenario naming. Debug builds use UseAppHost=false so Linux IDEs resolve .NET 10 from a user-local SDK. Add NS-16 implementation plan, code review doc, godot-client-script-organization rule, csharp test layout/naming rules, and refresh E1.M1 / alignment docs. Server and client README updates include move API, prerequisites, and Rider notes. Made-with: Cursor		2026-03-30 19:54:17 -04:00
..
epics	Complete Neon Sprawl rename and server project defaults.	2026-03-29 17:24:35 -04:00
milestones	Initial project vision and decomposition planning baseline.	2026-03-29 16:09:57 -04:00
modules	NS-16: MoveCommand → server PositionState, Godot sync, tests	2026-03-30 19:54:17 -04:00
README.md	docs: documentation vs implementation alignment (#7 )	2026-03-30 19:03:03 -04:00

README.md

Decomposition Workspace

This workspace contains detailed planning artifacts derived from the finalized master plan:

Source of truth: neon_sprawl_vision.plan.md
Tech stack baseline: docs/architecture/tech_stack.md
Scope here: executable decomposition (epics, modules, milestones)

Folder Layout

epics/ - One file per epic with implementation slices.
modules/ - Contract definitions, client vs server authority, PvP × combat engine, quest scope × party, data reload × telemetry ops, docs vs implementation, full module dependency register (all epic modules), per-module docs, and interface notes.
milestones/ - Phase-gated implementation tracks and pass/fail checklists.

Working Rules

Do not rewrite baseline vision in these files; link back to the master plan.
Keep slices backlog-ready (clear owner, dependencies, acceptance criteria).
Use stable IDs (E1, E1.M1, P1.M1, etc.) to preserve traceability.
Every new slice must reference telemetry and validation where applicable.

Epic Files

Epic	Document
1 - Core Player Runtime	epics/epic_01_core_player_runtime.md
2 - Classless Progression	epics/epic_02_classless_progression.md
3 - Crafting Economy	epics/epic_03_crafting_economy.md
4 - World Topology	epics/epic_04_world_topology.md
5 - PvE Combat	epics/epic_05_pve_combat.md
6 - PvP Security	epics/epic_06_pvp_security.md
7 - Quest / Faction	epics/epic_07_quest_faction.md
8 - Social / Guild	epics/epic_08_social_guild.md
9 - LiveOps / Integrity	epics/epic_09_liveops_integrity.md

Template for new epics or major revisions: epics/_epic_template.md

Next Actions

Expand slices into engineering tickets; keep module IDs aligned with the master plan.
Populate modules/module_dependency_register.md as contracts stabilize.
Refine milestones/phase_execution_plan.md with dates and owners when execution starts.