An arena survival game where Jev or Laya controls every enemy
Sree's game describes each moment in one sentence and asks one typed question; the enemies act on the returned probabilities, with either model plugged in.
BUILDS
Agents, routers, scorers and games — built on models that decide. Every entry links to the models it uses, so you can pull the same one and start from there.
29 builds · page 1 of 2
Sree's game describes each moment in one sentence and asks one typed question; the enemies act on the returned probabilities, with either model plugged in.
Ahmed had the 322M multilingual checkpoint control every paddle move, running locally on Windows.
A Unity-native client for local Laya servers and compatible endpoints: game state goes in, typed choices and scores come out.
A native Windows demo on CUDA or CPU showing live probabilities, chosen moves, inference timing and how often the planner stepped in.
Dev Ed measured local Laya on a base M5 against Jev's hosted API on the same maze.
A local 15×15 Gomoku game: you play black, and every white move is one Laya choice among up to six candidate points.
AmirTaha feeds the fruit, head and wall positions to the model and moves in the direction it returns.
mgear runs the ONNX weights in Unity through onnxruntime-unity and plays full games against the model.
Both models get identical inputs and questions in unscripted matches, as shown in a Prompt Engineer video; only the model changes.
Viraj Bhartiya ran Laya locally on MLX and Jev over its API on the same T-Rex track and physics.
Hope set up a first-to-five 1v1: Jev's calls were sharper, while Laya decided about twice as often.
With the network off, local Laya made 86.4 decisions a second from a 1 GB footprint while the API-bound Jev managed 3.2.
atomic.chat pitted Laya on a 16 GB MacBook Air against Jev's API; the local model decided about 11× faster.
Mansour Raad's experiment: Laya alone landed 0 of 90 attempts; with model-predictive control overruling a small share of moves, 90 of 90.
Arcade physics, a browser flight recorder and a Laya checkpoint fine-tuned on CUDA that landed every held-out flight when run on MLX.
soybelli connected Pac-Man to the model on Apple Silicon, with a live view of action probabilities, latency and tactical planning.
Tom Siwik argues that framing the decision space and batching matter more than the model: over the network Jev wins, locally the two tie.
Daniel Tremer's agent plays Hordes.io from screenshots: Apple Vision reads the screen, Qwen on MLX plans and Laya on Core ML makes each decision.
Simplifying AI ran the same game and questions on both models; Laya made 86.5 decisions a second against the API's 3.2.
Tobias ran all three on a low-memory MacBook: Jev won on quality, the local models on speed and cost.
Tony Dinh ran laya-mlx at about 84 ms per decision against Jev in real-time Tetris; Jev won all three games.
Daniel F's browser fighter has 21 characters, special moves, combos and replays, with the computer opponent run by Laya.
The announcement of the MLX port: under 1 GB of RAM, choosing the snake's next move sixty times a second.
Unmodified weights on a DGX Spark, real NES emulation and text observations read from RAM: 207 verified decisions at a 16.79 ms median.
Many of the first builds here were collected by madewithlaya.com. Every entry links to its creator’s own post, repository or site.