← Back to case files
CASE FILE / Games & simulation
Had some fun taking Jev from @typesafeai for a spin, switching seamlessl…
Had some fun taking Jev from @typesafeai for a spin, switching seamlessly between manual and AI-driven gameplay. It’s clocking 2–3 calls/sec at 60 FPS, with ~150ms avg latency. The most interesting part wasn’t the speed, though. It was distilling the game into the variables, actions, and decision criteria the AI needs to play well: Does it risk going for the powerup, or protect the ball? When is the reward worth the risk? Fun times ahead!
● ● ●CASE FILEGUIDE
Adrián Mato 🐙 · @adrianmg
Original post
Had some fun taking Jev from @typesafeai for a spin, switching seamlessly between manual and AI-driven gameplay. It’s clocking 2–3 calls/sec at 60 FPS, with ~150ms avg latency. The most interesting part wasn’t the speed, though. It was distilling the game into the variables, actions, and decision criteria the AI needs to play well: Does it risk going for the powerup, or protect the ball? When is the reward worth the risk? Fun times ahead!
Views 646Likes 14Reposts 0
Chinese translation
从@typesafeai获得了一些乐趣,在手动和人工智能驱动的游戏之间无缝切换。 它的时钟2-3调用/秒在60 FPS,与~ 150毫秒的平均延迟。 最有趣的部分不是速度。它将游戏提炼成AI需要玩好的变量、动作和决策标准: 它是否冒着去加油的风险,或者保护球?什么时候回报值得冒险? 有趣的时代即将到来!
What this case shows
- Game state maps cleanly onto typed choices
- Let JEV pick; keep generation elsewhere
- The original post usually has a playable demo