👾Robot Creation
How to create a robot or environment
1️⃣ Create Robot (Create Environment)
Purpose:
Build a fully original robot from scratch with complete customization.
Workflow:
User initiates "Create Robot" from the frontend.
System auto-generates a new robot draft, including:
A unique
sim_typeX(for simulation mapping).A unique
robot_00X(for rule tracking).Default placeholder values for:
Robot status
Robot commands
Environmental rules
User customizes every element:
Appearance
Movement
Sensors
Abilities
Environment interactions
Draft is saved in a JSON configuration file for future editing.
Robot can be deployed immediately or later.
Capabilities:
Full creative control over the robot’s design and behavior.
Environment objects receive unique IDs for easy reference.
Robots can be deployed at any time by the user.
Frontend Label:
Create Robot
Use Case:
Ideal for advanced users who want full control over their robot and its environment.
2️⃣ How the System Manages Robots
Unique Identifiers:
Robots:
sim_typeX→ Simulation mappingrobot_00X→ Rule tracking
Environment Objects:
Automatically assigned unique IDs for precise interaction.
Draft Management:
Saved as JSON configuration files.
Editable anytime before deployment:
Status
Commands
Rules
Tokenization (On-Chain):
When a robot is deployed:
A base token is minted on-chain.
This represents:
Ownership
Value
Simulation history
3️⃣ Choosing Between Deploy and Create
Deploy Robot
Limited
Easy
✅ Automatic
Create Robot
Full
Medium
✅ Optional (after deployment)
🔁 Robot Creation Flow (Visual)
Step 1: User Chooses an Option
✅ Deploy Robot (Add Robot)
Frontend Label:
Deploy RobotNotes:
Choose from pre-defined robots
Minimal setup required
Token automatically minted
🎨 Create Robot (Create Environment)
Frontend Label:
Create RobotNotes:
Full customization
Draft saved for continued edits
Token minted only when deployed
🔑 Key Points Summary
All robots—default or custom—can be deployed and tokenized.
Custom robots allow full control over:
Status
Commands
Environmental interactions
Drafts are saved in JSON for flexible, ongoing modification.
Unique identifiers (
sim_typeX,robot_00X) ensure consistent management across simulation and rule layers.
Last updated