Dave - Roblox: Impact Soccer

First Early Look of 'Impact Soccer' - A physics-based soccer game w/ no ball, pummel opponents to the ground or kick them free standing to score goals. Control your speed, angle, & kick power to execute major curves on strikes. ALL feedback welcome & looking for play testers 🤝

One of the best saves I’ve seen and kick had perfect curve too!

Game Dev Tip #3: Our approach to running a mini video game studio of AI agents should mimic that of an actual game studio. Human employees don't need to be told what to do every morning when they show up to work. They know their priorities and keep working off of them. Here's how I replicate that with my own studio. Now I just type “claude start” and the team gets to work: 1. Turn on Remote Control for every session. In Claude Code, go to /config > "Enable Remote Control for all sessions." This is a key step: it's frustrating to realize you're dead in the water when you're out and about. 2. Add a startup hook that opens your tools. Have your Orchestrator agent (the highest-level agent) set up a SessionStart hook. It's a script that runs automatically every time a new Claude session starts, with no approval needed. Here is how I have mine setup: A. launches Rojo in its own PowerShell window B. opens Roblox Studio straight into the Impact Soccer experience  Note: It skips anything that's already running, so nothing gets restarted mid-work. MCP Server Note: the Roblox Studio MCP turns on with a setting in Studio, then starts by itself whenever Studio opens, so I have no step for it. Other game editors may need a "launch and connect MCP server" step. 3. Put the morning routine in your CLAUDE.md file. This is what the Orchestrator does once everything is open: A. Checks that Studio and Rojo are healthy, and has the QA agent click "Connect" on the Rojo plugin. B. Catches up: it reads the last session's handoff notes, git and the plan.md file. C. Resumes anything that was paused, then gives the top item in each lane (QA, building, art, audio/video, marketing) to the right agent. D. Reports what's running, plus a list of things only I can test or decide. The plan.md file is where all my brain-dumped ideas go. The Orchestrator prioritizes them automatically unless I give one a priority when I dump it. At the end of every session it writes a handoff and updates the queue, so the next session picks up exactly where we left off. Every once in a while it's still good to review plan.md yourself, to make sure everything is properly prioritized (and to remember all the ideas you forgot about lol). Due to the limited RAM on my computer, I don't launch Blender or OBS at startup. Instead, I've authorized the Orchestrator to open and close them when needed. If you have a more powerful setup, you could add them to your startup hook. Hope this is helpful 🤝

Not sure if this is a good thing or bad thing lol

There has never been a more important time than now to exercise your curiosity and creativity.

Game Dev Tip #2.1: To summarize, the last post talked about ensuring the Game Editor is on the forefront of the screen and not using your computer when the QA agent (i.e. computer use Agent) is testing. We received some great tips from the Game Dev community here that I wanted to highlight. Shout out to @rblx_tyridge77, @gamedevaitools, @jvan253, and @afskiuban! rblx_tyridge77: "For roblox that usually means you're locked out of being able to work while your AI is working A good way to do this that I've been doing is to: - Work freely in your main studio file/teamcreate etc, which syncs code and agent asset changes from your main repo - Set up a laptop/second machine for your agents - orchestrator agent takes a snapshot of main.rbxl and the main source/repo - your agents build features in parallel in an isolated rojo/git branch - each agent tests its ready branch one at a time by cloning from snapshot.rbxl , loading up the place, loading its branch, and testing - any asset changes are recorded and sent back as well as performance reports etc - orchestrator takes all finished and tested agents and lets you test them before resolving conflicts and merging to main and resolving asset changes etc." gamedevaitools: "for unreal, untick use less cpu when in background in editor preferences. that's the editor's own throttle" jvan253: "good tip. if you can't keep unity in front, set Preferences > General > Interaction Mode to No Throttling. the editor slows way down when it loses focus, which makes agent tests flaky. and turn on Run In Background in player settings for builds" afskiuban: "i let mine launch unreal in headless mode especially for regression gating (with a custom gate monitor that watches gate progress and system resource utilization) so the window position doesn't matter and as long as you're not stressing the system by trying to run another game it's just waiting" Me: I found that you can prompt your Orchestrator Agent (i.e. highest level agent) to add to claude.md instructions to run a command from the root folder whenever the Game Editor or Blender is not on the forefront of the screen to bring to the front. I was worried about giving too much access to allow for this, but no additional permissions were needed (i.e. no admin access needed in Powershell) as this is a general windows command. Really appreciate everyone's support on this educational series and plan to continue these types of posts. Hope this is helpful 🤝

There might be a lot more than what meets the eye in Impact Soccer

Game Dev Tip #2: When running a team of AI agents to help develop your game it is important that you have the Game Editor (e.g. Roblox Studio, Unreal Editor, Unity Editor, etc.) always at the forefront of the screen. This is necessary so the QA Agent can properly run its tests on new updates, which always includes a performance check. If the Game Editor is in the foreground, then your computer automatically throttles the frame rate which leads to inaccurate test results. It is also important that you do not use your computer while the QA is running tests, but this creates a bottle neck. How can you continue brain dumping ideas all day to the Orchestrator Agent (i.e. the highest level agent)? One solution that has helped me (especially since I’m limited to one screen during the work week), is using the /remote-control command in Claude Code. This feature allows you to access your same Claude Code instance from your phone wherever you might be. Hope this is helpful. 🤝

Game Dev Tip: When using AI to help develop your game, prompt your LLM to analyze your game and create a lineup of multiple different permanent agents (all Opus 5.5 for my setup) that can be assigned to work on different aspects of the game. Then tell the LLM to have each agent to review the project to gain an understanding of what the game is and what the tech stack is like, then do deep research on their domain of expertise. The ability to now have a team of agents working on many different tasks in parallel has saved me significant time. I can freely brain dump all the different ideas I have through out the day without having to wait for my single LLM to free up their context. Different projects will have different types of agents spun up, but for Impact Soccer it made me 2 different game play coding agents, a graphics designer, a social media manager, a gameplay testing agent, multi-platform performance reviewer, sound and audio agent, project manager/planner, platform compliance agent, and a few others. Hope this is helpful 🤝

A word from the legend himself..

Some gems are really starting to come out of the wood works.. this one’s got some real potential.

Building games is so satisfying. The ability to see your oddball, obnoxious, good/bad ideas come to life is a real treat. Maybe I have a higher standard than most, but even if you are using AI, it takes some real dedication to make something truly fun and great that people will enjoy (not to claim that I am there yet, but I believe I am on the right path). I’m about 5 months in on building my game. Building games has been the most fun of any project I’ve worked on and hits closest to home as something I am passionate about. I have had maybe 15-20 failed business attempts/ventures over the years, 1 success, and 1 major success. What I’m trying to say is don’t be afraid to fail, don’t let the loud ones deter you from creating and building. Keep building friends 🤝