-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment Modes
Adastrea Director offers two deployment modes: Standalone and Unreal Engine Plugin. Both use the same Python backend, providing consistent functionality across different workflows.
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Deployment Layer β
β βββββββββββββββββββ βββββββββββββββββββ β
β β Standalone β β Plugin Mode β β
β β (Python) β β (UE + Python) β β
β ββββββββββ¬βββββββββ ββββββββββ¬βββββββββ β
ββββββββββββββΌβββββββββββββββββββββββββββΌββββββββββββββββββ
β β
βββββββββββ¬βββββββββββββββββ
β
ββββββββββββΌβββββββββββββββββββββββ
β Shared Python Backend β
β β’ RAG System (P1) β
β β’ Planning System (P2) β
β β’ Agent System (P3) β
βββββββββββββββββββββββββββββββββββ
Standalone mode provides a Python-based interface (CLI and GUI) for using Adastrea Director without Unreal Engine.
β Use Standalone Mode when:
- Working on non-Unreal Engine projects
- Testing and prototyping features
- Developing agents or backend components
- Needing quick access without loading UE
- Working on documentation or planning
- Running on systems without Unreal Engine
CLI Applications:
-
main.py- Context-aware assistant -
planner.py- Planning system -
agent_orchestrator_cli.py- Agent management -
agent_dashboard.py- Real-time monitoring
GUI Application:
-
gui_director.py- Graphical interface with all features
β All Core Features:
- RAG-based Q&A system
- Document ingestion
- Planning and task decomposition
- Agent orchestration
- Real-time dashboard
# Clone repository
git clone https://github.com/Mittenzx/Adastrea-Director.git
cd Adastrea-Director
# Run setup script
./setup.sh
# Or install manually
pip install -r requirements.txtSee Installation Guide for details.
CLI:
# Context-aware assistant
python main.py
# Planning system
python planner.py --interactive
# Agent orchestrator
python agent_orchestrator_cli.py start --allGUI:
# Start GUI application
python gui_director.py- β Fast Startup: No need to load Unreal Engine
- β Lightweight: Minimal system requirements
- β Easy Debugging: Direct Python debugging
- β Platform Independent: Works on any OS with Python
- β All Features: Full access to all capabilities
- β Not integrated into Unreal Engine workflow
- β Requires context switching between tools
- β No direct UE API access
- β Manual asset/actor queries via CLI
Plugin mode integrates Adastrea Director directly into Unreal Engine Editor as a C++ plugin with Python backend communication.
β Use Plugin Mode when:
- Working primarily in Unreal Engine
- Need integrated in-editor experience
- Want to query UE assets and actors directly
- Performing editor automation tasks
- Avoiding context switching
- Working on UE-specific features
C++ Plugin:
-
Plugins/AdastreaDirector/- UE plugin - Slate UI for in-editor interface
- HTTP/IPC bridge to Python backend
Python Backend:
- Same backend as standalone mode
- Additional UE Python API integration
- HTTP server for plugin communication
β Integrated Experience:
- In-editor UI panel (dockable)
- Asset and actor queries
- Console command execution
- Editor automation
- Same RAG, Planning, and Agent features
β UE Python API Access:
- Query assets and actors
- Modify scene objects
- Execute console commands
- Editor notifications
# 1. Copy plugin to UE project
cp -r Plugins/AdastreaDirector /path/to/UEProject/Plugins/
# 2. Regenerate project files
# Right-click .uproject β Generate Visual Studio project files
# 3. Build project
# Build in Visual Studio/Xcode
# 4. Launch Unreal Engine
# Window β Developer Tools β Adastrea DirectorSee Plugin Setup Guide for details.
In-Editor:
- Open Unreal Engine Editor
- Window β Developer Tools β Adastrea Director
- Use Ingestion tab to add documentation
- Use Query tab to ask questions
- Python backend starts automatically!
With UE Python API:
# Query assets
> List all StaticMesh assets in the project
# Spawn actors
> Spawn a PointLight at location (0, 0, 100)
# Execute commands
> Run command stat fps- β Integrated Workflow: No context switching
- β Direct UE Access: Query assets, actors, and execute commands
- β Editor Automation: Automate repetitive tasks
- β Natural Integration: Part of UE editor
- β Same Backend: All standalone features available
- β UE startup time overhead
- β More complex setup
- β Platform-specific builds required
- β Some features still in development (Weeks 1-6 complete)
β Complete (Weeks 1-6):
- Basic UI with tabbed interface
- RAG integration
- Document ingestion in-editor
- Query interface
- UE Python API integration
π§ In Progress (Weeks 7-16):
- Planning system integration
- Agent orchestration UI
- Performance profiling panel
- Bug detection integration
| Feature | Standalone | Plugin |
|---|---|---|
| Setup Complexity | Easy | Moderate |
| Startup Time | Fast (seconds) | Slow (UE startup) |
| Context Switching | Required | Not required |
| RAG System | β | β |
| Planning System | β | π§ |
| Agent System | β | π§ |
| UE Integration | β | β |
| Asset Queries | Manual | Direct |
| Editor Automation | β | β |
| Platform | Any | UE-supported |
| Development | Easy | Moderate |
| Non-UE Projects | β | β |
You can use both modes together!
Example Workflow:
- Planning - Use standalone GUI for quick planning
- Implementation - Use plugin in UE for implementation
- Monitoring - Use standalone dashboard for agent monitoring
- Documentation - Use standalone for doc queries
Shared Resources:
- Same knowledge base (chroma_db)
- Same configuration
- Same Python backend
Are you using Unreal Engine?
ββ No β Use Standalone Mode
ββ Yes
ββ Do you need in-editor integration?
ββ Yes β Use Plugin Mode
ββ No β Use Standalone Mode
(faster, easier debugging)
For Individual Developers:
- Start with Standalone Mode for learning
- Switch to Plugin Mode once comfortable
- Use both for different tasks
For Teams:
- Standalone Mode for designers/writers/planners
- Plugin Mode for UE developers
- Both for technical directors
For Non-UE Projects:
- Standalone Mode only
Switching between modes is seamless:
Standalone β Plugin:
- Install plugin
- Point to same
chroma_dbdirectory - Use same configuration
- All data preserved
Plugin β Standalone:
- Exit Unreal Engine
- Use standalone CLI/GUI
- Same database and config
- No data loss
Standalone:
CLI/GUI β Python Backend β LLM/Vector DB
Plugin:
UE Plugin (C++) β HTTP/IPC β Python Backend β LLM/Vector DB
β
UE Python API
Standalone:
- Backend runs directly in Python process
- Immediate availability
Plugin:
- Backend starts on plugin initialization
- HTTP server on localhost:8000 (configurable)
- Automatic startup/shutdown with UE
Both modes share:
-
Vector DB:
./chroma_dbor configured path -
Config:
~/.adastrea/config.json - Logs: Same logging directory
Standalone:
- Web-based UI (browser interface)
- VS Code extension
- CLI autocomplete
Plugin:
- Blueprint integration
- Visual scripting support
- In-game runtime queries
Both:
- Cloud synchronization
- Team collaboration features
- Multi-project support
Adastrea Director | GitHub | Issues | Discussions
Building tomorrow's game development tools, today.