Skip to content

Add plan.md: roadmap from physics kit to a full xTalk 2D game engine#20

Merged
SethMorrowSoftware merged 1 commit into
mainfrom
claude/sweet-planck-duhB5
Jun 4, 2026
Merged

Add plan.md: roadmap from physics kit to a full xTalk 2D game engine#20
SethMorrowSoftware merged 1 commit into
mainfrom
claude/sweet-planck-duhB5

Conversation

@SethMorrowSoftware
Copy link
Copy Markdown
Owner

A planning document (no code changes) describing how to grow Box2Dxt into "xGE", a modular 2D game engine usable both script-only and via a GUI editor:

  • Honest assessment of today's 4 layers and what the Kit already provides.
  • A layered target architecture (L0 native → L1 binding → L2 physics kit → L3 engine core → L4 editor → L5 runtime/export) where each layer is usable on its own and runtime never depends on the editor.
  • Design principles that keep it simple: controls are entities, native LiveCode behaviors are components, library stacks are modules — no ECS, no custom renderer on the critical path.
  • A fixed behavior/message contract as the public engine API.
  • A 7-phase roadmap (script-only engine first, then editor, then export), each phase shippable with a sample game as its milestone.
  • Cross-cutting plans for rendering/perf, standalone packaging, assets, input, save formats, testing, and backwards compatibility.

https://claude.ai/code/session_018VCGPT8pLd7wQhnLKdZDEx

A planning document (no code changes) describing how to grow Box2Dxt into
"xGE", a modular 2D game engine usable both script-only and via a GUI editor:

- Honest assessment of today's 4 layers and what the Kit already provides.
- A layered target architecture (L0 native → L1 binding → L2 physics kit →
  L3 engine core → L4 editor → L5 runtime/export) where each layer is usable
  on its own and runtime never depends on the editor.
- Design principles that keep it simple: controls are entities, native
  LiveCode behaviors are components, library stacks are modules — no ECS, no
  custom renderer on the critical path.
- A fixed behavior/message contract as the public engine API.
- A 7-phase roadmap (script-only engine first, then editor, then export),
  each phase shippable with a sample game as its milestone.
- Cross-cutting plans for rendering/perf, standalone packaging, assets,
  input, save formats, testing, and backwards compatibility.

https://claude.ai/code/session_018VCGPT8pLd7wQhnLKdZDEx
@SethMorrowSoftware SethMorrowSoftware merged commit b383e79 into main Jun 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants