MOBA systems

1. It is a game, not an API. Open it in euca-studio (cargo run -p euca-studio, pick the MOBA project) and press Play, or serve it headless with cargo run -p euca-studio -- --headless moba (agent HTTP API on :3917, no window). The engine names no game; the studio resolves the moba project’s app id to its Game.
2. There are no /moba/* or /hero/* endpoints. An arena is assembled from the generic spawn, item, rule, and gameplay routes plus the MOBA ECS systems that run inside game.step. The repo’s scripts/moba.sh builds the whole arena this way over the API — read it as the worked end-to-end example.

​

Stand up an arena

curl -s -X POST http://localhost:3917/spawn -H 'Content-Type: application/json' -d '{
  "mesh":"sphere","color":"cyan","position":[-7,0.5,0],"scale":[1.2,1.2,1.2],
  "physics_body":"Kinematic","collider":{"shape":"Sphere","radius":0.6},
  "health":500,"team":1,"combat":true,"combat_damage":30,"combat_range":2,
  "combat_speed":4,"combat_cooldown":0.8,"role":"hero",
  "gold":0,"gold_bounty":300,"xp_bounty":200,"player":true}'
# {"entity_id":103,"entity_generation":0}

curl -s -X POST http://localhost:3917/item/define -H 'Content-Type: application/json' \
  -d '{"id":1,"name":"Iron Branch","properties":{"cost":50,"health":15}}'
# {"ok":true,"message":"Defined item 1: Iron Branch"}

curl -s -X POST http://localhost:3917/item/give \
  -H 'Content-Type: application/json' -d '{"entity_id":103,"item_id":1,"count":1}'
# {"ok":true,"message":"Added 1 of item 1"}

# (from scripts/moba.sh — creep wave every 20s, score on enemy death)
euca rule create --when timer:20 --do-action "spawn cube -7,0.5,0 blue 80 1 ... minion 3"
euca rule create --when death --filter team:2 --do-action "score source +1"

​

Behavior and gotchas

• There is no /moba/spawn, /moba/match, /hero/define, or /hero/select. Those MOBA-specific routes were removed; they 404. The MOBA layer is pure ECS systems plus the generic spawn / item / rule / gameplay routes. A hero is one /spawn with combat + role flags; a creep is /spawn plus a combat role, or a timer rule.
• The full hero kit (mana, abilities, stat growth) is in-game, not over HTTP. euca-moba’s Rust spawn_hero inserts an AbilitySet, Mana, and base/growth stats. The generic /spawn does not — see Units & roles and Abilities & status effects.
• The MOBA systems run inside game.step. tower_aggro_system, neutral_camp_system, vision/wards, and day-night are part of the MOBA game’s per-tick schedule, so they advance on every /step of the headless host without any MOBA-specific endpoint.
• Serve it with the project id. cargo run -p euca-studio -- --headless moba loads the moba project under projects/. With no id, the first discovered project is served instead.

​

Endpoints

​

Status

• Shipped — hero attributes (STR/AGI/INT, derived stats), towers and barracks, creep waves, Roshan, neutral camps, item actives, fog-of-war and wards, day-night, tower aggro, and gold/XP. Runs as the euca-moba example game in euca-studio (windowed) or headless.
• Requires — rendering a match needs a GPU host (the windowed studio); the match logic itself is fully headless.