Skip to content

Commit f41689b

Browse files
committed
fixes
1 parent d69488a commit f41689b

File tree

10 files changed

+1043
-66
lines changed

10 files changed

+1043
-66
lines changed

docs/architecture/core-components.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,6 @@ Note that these components are intentionally minimal. Game developers are expect
4343
- **Vite:** Our build tool and development server. It provides extremely fast Hot Module Replacement (HMR) for instant feedback during development and optimizes the final build for production.
4444
- **TypeScript:** Ensures type safety throughout the codebase, reducing runtime errors and improving code maintainability and developer confidence.
4545

46-
## Optional Editor
46+
## Development Workflow
4747

48-
- **Rogue Engine:** A visual editor that can be used to design and lay out scenes, configure components, and preview the game. It streamlines the level design and asset integration process, exporting configurations compatible with our Three.js/R3F setup.
48+
The engine is designed to work primarily through code and our AI-assisted editor interface, focusing on programmatic scene creation and manipulation rather than visual drag-and-drop tools.

docs/architecture/technical-stack.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,6 @@ Our stack consists of the following key libraries and technologies:
2424
- _Reason:_ A battle-tested framework for multiplayer game servers, providing features like room management, state synchronization (delta patching), and client prediction.
2525
- **Build Tooling:** **Vite 5 + TypeScript 5**
2626
- _Reason:_ Vite offers extremely fast Hot Module Replacement (HMR) for a rapid development feedback loop, while TypeScript provides static typing for improved code safety and maintainability.
27-
- **Editor (Optional):** **Rogue Engine**
28-
- _Reason:_ A visual, Unity-like editor for Three.js scenes. It can export vanilla JavaScript or work with React, providing a visual authoring workflow.
2927

3028
## Rationale
3129

docs/architecture/tooling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ This document describes the tools and development workflow used for the Vibe Cod
4242

4343
## Editor & Asset Pipeline with AI
4444

45-
- **Vibe Coder 3D Editor with Integrated AI Copilot:** This is the primary tool. There is no reliance on external visual editors like Rogue Engine, as the AI facilitates visual and logical assembly through conversation and direct engine manipulation.
45+
- **Vibe Coder 3D Editor with Integrated AI Copilot:** This is the primary tool. The AI facilitates visual and logical assembly through conversation and direct engine manipulation.
4646
- **AI-Driven Asset Handling:**
4747
- The AI Copilot can interface with asset generation tools (e.g., text-to-3D, procedural generators) or search asset libraries based on user descriptions.
4848
- Assets are managed within the project structure, with the AI assisting in their import, organization, and application.
@@ -58,7 +58,7 @@ This document describes the tools and development workflow used for the Vibe Cod
5858

5959
## Future Considerations
6060

61-
- Development of custom editor tools built with React/Web technologies if Rogue Engine proves insufficient or too restrictive.
61+
- Development of custom editor tools built with React/Web technologies as needed.
6262
- More sophisticated asset pipeline/management system if project scale demands it.
6363
- Integration of automated testing tools (e.g., Vitest, Playwright).
6464
- Standardized logging framework.

0 commit comments

Comments
 (0)