Files
gregWiki/docs/roadmap/unified-roadmap.md
Marvin e2839584f4 Merge Docusaurus site: all content under docs/, align with gregFramework split layout
- Move markdown and wiki-import tree into docs/; keep app shell at repo root
- Point docusaurus docs path to docs/; edit links to mleem97/gregWiki
- Sync and i18n scripts use gregWiki root and ../.wiki under gregFramework
- Sidebars: workspace layout from root docs ids; plugins under mods/extensions
- Fix redirects, module catalog URLs, release note paths, and wiki-import category keys
- Update repo inventory for split repos; Dockerfile for single-repo context

Made-with: Cursor
2026-04-09 23:39:32 +02:00

2.1 KiB

id, title, slug
id title slug
unified-roadmap Unified Roadmap /roadmap/unified-roadmap

This is the canonical roadmap page for the project. It consolidates previous roadmap documents and removes duplicate planning tracks.

Status Summary

  • Framework Runtime: active
  • Docs & Contributor Tooling: active
  • Mod Distribution & Audit Pipeline: active planning
  • Multiplayer (Steamworks): blocked externally

Important Multiplayer Note

Multiplayer was planned around Steamworks P2P and that direction remains conceptually valid.
However, it is currently not implementable in production because the game developer has not integrated Steamworks support in the game runtime/API surface required for a stable implementation.

Consolidated Workstreams

1) Framework & Hooking

  • Stabilize hook coverage and event contracts.
  • Keep C# and Rust bridge compatibility versioned.
  • Expand diagnostics for mod-runtime compatibility failures.

2) Documentation & Information Architecture

  • Keep /wiki/* as canonical docs namespace.
  • Maintain separated Plugin Wiki and Mod Wiki sections.
  • Remove duplicate docs by keeping one canonical page per topic.

3) Mod/Plugin Catalog & Distribution

  • Maintain dynamic /mods catalog with links to wiki and release endpoints.
  • Keep release metadata visible (version, author, dependencies, language).
  • Keep release-state gating (NotReleasedYet) explicit for users.

4) Security Audit & Submission Workflow

  • Accept plugin submissions via Git repository URL.
  • Run automated static checks and suspicious-pattern scans.
  • Gate publication/release visibility on successful audit outcome.

5) Multiplayer Track (Blocked)

  • Keep architecture docs for future Steamworks integration readiness.
  • Track dependencies on game-side Steamworks implementation.
  • Re-open implementation only when game runtime exposes required primitives.

Legacy Roadmap Documents

The following pages are now legacy references and should not be used as primary planning sources:

  • wiki-import/ROADMAP
  • wiki-import/Steamworks-P2P-Multiplayer-Roadmap
  • roadmap/mod-store-stages