Currently invitation-only. Signing up does not automatically allocate a cloud computer. Register with the invited email and complete email verification.
If your account has cloud projects, the creation page also offers Import an existing project from GitHub for a private repository on your personal account; ZIP archives are not supported yet.
01 · Open project creation
Log in and choose Create project on the dashboard. If the entry is missing, confirm your account has creation access. To join a teammate, skip to Join a project below.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Create project on the dashboard · Select image to enlarge Dark UI · Local teaching account; cloud preparation and readiness are seeded.
02 · Name your project
Enter a project name and create it. This only prepares your space. On the preparation page, choose how to start, then describe your idea or paste a design document.
Name the project and prepare your creative space · Select image to enlarge Dark UI · Local teaching account; cloud preparation and readiness are seeded.
03 · Connect GitHub
GitHub stores your project source. Choose Connect GitHub and continue, then sign in with the owner’s personal GitHub account. MiniGrove creates a private repository for the new project.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
The GitHub connection prompt in MiniGrove · Select image to enlarge Dark UI · Local teaching account; cloud preparation and readiness are seeded.
04 · Review repository access
For first installation, follow the prompt and choose All repositories. This allows access to and management of all current and future repositories on that account. Administration covers repository management; Contents covers file access. Review the scope, then use GitHub’s installation confirmation button (Install).
Actual GitHub permission-page excerpt: locate All repositories; first-install buttons can differ · Select image to enlarge Dark UI · Actual GitHub capture; no authorization or permission change submitted.
05 · Authorize account access
If this page appears, check the app is MiniGrove and the return address is app.minigrove.io. Review it, then choose Authorize. An installed account may only need this step.
MiniGrove account authorization on GitHub; captured before Authorize · Select image to enlarge Dark UI · Actual GitHub capture; no authorization or permission change submitted.Different page, or GitHub did not return?
The screenshot focuses on All repositories in existing installation settings; this installed account retains Only select repositories with no permission change.
Installation chooses which repositories the app can access; account authorization lets it act on your behalf. First connection may require both, while an existing connection may only ask for sign-in. The pictured installed account uses selected repositories. Such existing connections can continue, with a newly created repository added to the app’s scope. Keep your existing connection.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Before GitHub, MiniGrove explains the handoff and preserves your project name · Select image to enlarge Dark UI · Local teaching account; cloud preparation and readiness are seeded.
If the return does not happen, reopen the original preparation page, expand Already connected, or GitHub did not return?, and choose Check connection and continue. Continue this preparation instead of creating another project.
While preparing, choose Discuss first (default) or Start building, then write and save the corresponding input. Saving authorizes that discussion or production once ready. Advanced settings start folded and contain engine, platform and technical requirements; the Windows example can use Godot / Windows. Typing or waiting sends nothing, and readiness will not interrupt your draft. You can skip for now. Keep stalled or error messages and the page link for support.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Back in MiniGrove, follow the preparation steps; progress is a local teaching preset · Select image to enlarge Dark UI · Local teaching account; cloud preparation and readiness are seeded.
07 · Open the project
When Project is ready appears, choose Enter project →. Continue the original discussion or production conversation if you saved an idea, or start inside the project later.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Project and AI ready → Enter project; readiness is seeded for teaching · Select image to enlarge Dark UI · Local teaching account; cloud preparation and readiness are seeded.
The project owner invites teammates from member management using their MiniGrove email address. Invitations follow project permissions and available capacity; ask the owner or MiniGrove support if the entry is unavailable.
Log in with the invited email, accept the invitation and open your team’s project. Members share its files and model connection; no separate project or repeated GitHub connection is needed.
Windows target, browser iteration
This guide uses Windows 10/11 x64 with Godot standard / GDScript. In Advanced options choose Godot and Windows. Steam distribution is a later step.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Choose Godot and Windows in Advanced options; the pictured brief is unsubmitted · Select image to enlarge Dark UI · Local teaching interactions; build outcomes are seeded. No Windows playtest is claimed.
These preferences set the final delivery target, not a separate development workflow. For Windows too, ask AI for a browser-playable version and use preview marks. Check Compatibility rendering and the export environment; test the final Windows package at delivery. A capable computer can download Godot and templates on demand, so the first build may take longer.
Example first brief for a PC game
Example promptBuild an offline Windows 10/11 x64 tactical RPG with Godot standard / GDScript and Compatibility rendering. Start with one small battle: grid movement, turn order, a basic attack, wait, win/loss and restart. Provide a browser playtest for preview marks during development. Create the final Windows candidate from mainline and test its complete ZIP on Windows.
You can skip this chapter. Projects include AI usage; configure this only to use your own key or subscription.
Monthly allowance renews each month; see AI allowance for the balance and reset date. Trial and extra grants follow the validity shown there. Expand setup only to change sources.
Members use the project’s existing allowance and connection. The project owner configures any change of source.
Own-key setup (optional)
Project menu → Connections and keys → Models → Change model source → Your API key (BYOK)
BYOK setup form with an empty key field · Select image to enlarge Dark UI · Local teaching data with seeded execution states.
01
Prepare your key
Create a dedicated key in your OpenRouter account and check its budget and available models.
02
Enter and verify
Enter your OpenRouter key, choose tool-compatible models, then verify and save.
03
Check receipt
Confirm BYOK is the source and the state says “Saved · Received by cloud computer”, then verify it with a small task.
Need your own key? Open OpenRouter API Keys, sign in, and create a dedicated key for the project. Choose models that support tool calling and pass this form’s verification. Availability follows your account and validation result. If your project already has a working model source, continue directly.
1 · Saved; wait for receipt2 · Received; start a task
Check the resultSaving alone is not enough. “Received by cloud computer” means the key reached the computer; “Waiting to be claimed” on a task means that task has not started. Wait for a small task’s reply and preview before larger work. If progress stops, keep the state and last-update time for support instead of submitting duplicates.
Costs, keys and common questions
Use the Models area, not Project service keys.
Model costs go to the key’s OpenRouter account. Cloud computer use and plan coverage are separate. BYOK does not increase concurrency.
The key is delivered to the cloud computer. Members who can run code there may read it. Use a dedicated key you agree to share with project members, set a budget, and keep it out of chat and screenshots.
If verification fails, keep the error and check the key and models. The key’s account holder checks balance, budget and model access. Contact MiniGrove support below if setup still fails.
Use your ChatGPT plan (optional)
When your project offers the ChatGPT subscription option and its permissions, plan and cloud computer support it, a project member can connect it without creating an OpenRouter key.
Project menu → Connections and keys → Models → Change model source → ChatGPT subscription
Connection and sharing
01
Review sharing first
This connection is shared by current/future project members and enabled tasks. Members able to run code may read saved credentials. Connect only after accepting that scope.
02
Authorize with OpenAI
Choose Connect, open the OpenAI authorization page and enter the code shown in the connection view. Keep passwords and codes out of project chat.
03
Wait for connection, then open a new conversation
Once connected and the computer is online and ready, start a new conversation. Finish or stop queued/running tasks before switching; history is kept. Exhaustion does not automatically switch to API billing.
If the option is missing or connection is unavailable, follow the project’s message and use its existing model source. Cloud computer time and the MiniGrove plan are accounted for separately.
Claude subscription: eligible solo projects
Only when your project offers the Claude option and its permissions and computer support it can the owner connect their own Claude Pro/Max. It is limited to single-person projects; use the existing source if the option is absent.
Connections and keys → Models → Change model source → Claude subscription (single-person project)
Open Claude authorization from the page and return the code to the connection form, keeping it out of chat. Wait for connection before starting a new conversation. Before inviting teammates or choosing another source, disconnect Claude and wait for the computer’s confirmation.
03
03 / 09 · Start your first idea
Start your first idea
Check your project’s progress before creating a task.
Start building selected
Wait for the first build
If you entered an idea and selected Start building, the first production task starts after setup. Follow that task and wait for its preview instead of sending the same brief again.
Discuss first or no idea entered
Create a production task
For Discuss first, the idea saved on the preparation page starts a discussion. Continue refining your design there. If you have not saved an idea, start a conversation inside the project. When ready to build: ＋ New → Task. Describe the scope and acceptance checks, then send.
Actual tactical RPG example: start by validating movement, turn order and one battle · Select image to enlarge Actual gameplay from My Tactical RPG; not a promise of the first task’s output.Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Shared first task: keep the project engine and final target, request a browser playtest first; the clip ends queued · Play; use fullscreen for details Dark UI · Local teaching data with seeded execution states.
01
Open the menu
＋ New → Task.
02
Set the scope
Describe what to build, what to preserve and how to test it.
03
Send and wait
Follow the queue and progress, then playtest this task’s version.
Example brief and task scope
This guide follows a classic tactical RPG. Validate one small battle first; each task keeps a version you can playtest independently.
Example promptBuild one small battle for a classic tactical RPG: an 8-by-6 grid, 3 allies and 3 enemies, with turn-order movement, a basic attack and wait. Defeat all enemies to win, lose when all allies fall, and allow restart. Keep the engine and final delivery target already chosen for this project. During development, first provide a browser-playable version for playtesting and selection edits. Use simple characters and scenery; leave story expansion, equipment and skill trees for later. Provide the current task’s browser playtest link, controls, completed checks and unverified items.
Work in parallel while you wait
While gameplay is being built, use ＋ New → Discussion to talk through art or music. The original task continues. Choose Task for asset or feature production.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Open a discussion for art direction → save an Idea; saving it does not start AI · Play; use fullscreen for details Dark UI · Actual local teaching-account interactions; AI replies and roadmap results are seeded.
Discussion: explore options
For example: “Warm illustration or pixel art? Compare first; do not change the game.”
Idea: save it for later
Keep a future idea. Choose Start when you are ready to work on it.
Before parallel production, separate the scope
Use separate tasks for animation and sound, with clear boundaries to avoid editing the same feature. They do not combine automatically: review the base, merge it into mainline, then sync later tasks before integration.
Example promptI want an exploration and management game. Compare two core loops, their players, appeal and production scope. Discuss before building.
MiniGrove Advisory Group offers Positioning Office Hours. Use /mg-positioning-office-hours for long-term positioning; Jam and learning goals suit a lighter review. Availability follows your project’s skill menu.
Hand off in the same conversation
When your project has teammates, mention someone in a task that has completed its first production turn. They confirm in the same chat, then continue with AI.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Qing mentions Lin in a note → Lin confirms in the same chat → turns To AI on to continue · Play; use fullscreen for details Dark UI · Actual local teaching-account interactions; AI replies and roadmap results are seeded.
01
Ask in a note
Turn off To followed by the AI’s name. Type @, select a project member and send.
02
Confirm the handoff
Your teammate replies in the original chat and agrees on the edit scope.
03
Continue production
Your teammate turns To AI on before sending an instruction, then mentions you here for review.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Turn To AI off → select Lin from the @ list → send a note · Select image to enlarge Dark UI · Actual local teaching-account interactions; AI replies and roadmap results are seeded.
Mentioning a teammate alone does not choose the AI recipient. Merge after review; a handoff does not merge versions.
04
04 / 09 · Playtest and edit
Playtest and edit
During development, prioritize browser playtests and preview marks. Windows and Web share this iteration workflow; validate final builds on their delivery platform.
Browser: playtest the current task
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Completed task → open Preview → restart; the local scene demonstrates entry and restart only · Play; use fullscreen for details Dark UI · Local teaching data with seeded execution states.
01
Stay in this task
Select the current production task and wait for its preview link. Done means the turn ended; playtest it yourself before accepting.
02
Open Preview
On a wide screen use ▶ Preview on the right rail; on narrow screens choose Preview from the view controls. A project deployment link in the reply also opens there. Check the task name and preview tab’s version label.
03
Play a complete round
Focus the game. Select a character and check movement range, positioning, attack, wait and enemy actions, then play through win/loss and restart. If no preview is supplied, ask for it in this task; do not treat Done as acceptance.
Check the resultYou are testing the Core gameplay task, which has not entered mainline yet. Note a specific issue; the next step selects it in this same task preview.
After playing, select one concrete issue
Make the tactical RPG action menu easier to select. Its annotation subtask merges back into the current Core gameplay task.
Current annotation tools: markers, brush, arrows, text and color picker; Bajia example · Select image to enlarge Actual Bajia gameplay and annotation tools; local unsent draft.Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Guided zoom (the earlier selection interface; the flow is the same): ask for the change → locate the subtask → review and merge back to parent; execution states are seeded · Play; use fullscreen for details Dark UI · Local teaching data with seeded execution states.
01
Mark the current task preview
In this task’s Preview, open the round key and choose Mark. Use markers, brush, arrows, text or color picking to point out the action menu, a character or a tile. State what to change and preserve. Done adds the image and notes to the composer; review before sending.
02
Turn on Subtask, then send
Turn on Subtask in the composer row, add your request and send. A new edit subtask is created and merges back into this task once its checks pass; until then this task stays as it is.
03
Review the edit subtask
Open the new subtask in the conversation list. Once its preview is published, choose View subtask result and restart: check the action menu while movement range and damage rules stay the same. Not right yet? Keep asking in the subtask.
Example prompt
Example promptEnlarge the Move, Attack and Wait buttons and separate them to prevent misclicks. Preserve movement range, damage, turn order and the existing rules.
Merge back to the parent
The subtask merges back on its own once its checks pass. Wait for the green success state in its progress strip, then choose View parent task update. This opens the updated parent preview; the conversation may still be the subtask.
Check the resultReturn to Core gameplay, open its updated preview and replay. Check the task name and version label. This merged into the parent task; the next chapter puts it into mainline.
Windows: development and final acceptance
Windows games use the same browser playtest and preview-mark workflow above. Final Windows acceptance uses the complete ZIP from a mainline candidate. A working Web preview does not establish a Windows pass.
01
Check the task
Ask for this task’s browser-playable version, test gameplay and select areas to edit. If it cannot yet be provided, ask AI for the reason, completed checks and unverified items; AI completion is not your acceptance.
02
Build a mainline candidate
Candidates come from mainline. Enable and check Windows in Release, create a candidate, then download its ZIP and play it on Windows.
03
Bring feedback back
Record the candidate version, screenshots, reproduction steps and expected behavior in a new fix task. Merge the fix, create another candidate and test the new package.
Example promptWindows candidate v0.1.0-rc.1: movement stops after switching from fullscreen to windowed. Reproduce: launch game.exe → fullscreen → windowed → left/right keys. Movement should still work. Screenshot attached. In a new task, check the candidate source against current mainline, then fix it. Preserve movement range and damage rules; report checks and remaining Windows tests.
The selection walkthrough above applies to browser playtests, including those for a Windows target. Send native Windows screenshots and reproduction steps to a fix task; do not select directly in the native window.
Mainline is the project’s shared base. Sync brings its updates into a task; merge brings reviewed task changes into mainline.
Two merge destinations
Selection subtask → Merge back to parent → original Core gameplay. After reviewing that task → Merge into mainline… → mainline. Displayed tree hierarchy does not change an ordinary task’s merge destination.
Merge into mainline
On the reviewed Core gameplay task, choose ⋯ → Merge into mainline…, check the destination and changes, then confirm. Once merged, the base is in mainline. Continue to building a candidate in the next chapter.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Task menu → confirm Merge → completion receipt → mainline status; checks and merge outcome are seeded · Play; use fullscreen for details Dark UI · Local teaching data with seeded execution states.
Final Windows delivery: iterate in the browser during development and merge after task checks. Before delivery, build a candidate for Windows acceptance. Fix issues, merge and rebuild before public delivery. Windows delivery steps →
After merging the base, build and review a candidate. Expand the A/B example when you need parallel production.
Example: sync and merge parallel tasks
Example: parallel production
Merge Core gameplay into mainline → ＋ New → Task to create task A; repeat for task B. Alternatively, right-click mainline in the tree and choose New top-level task.
The clip uses the tree entry for B: name it B · Attack sound, confirm the project default branch as the base, then submit. Each task has its own working version; start B while A is still running.
Task A · Character walk animation
Animation only
Compare two movement strengths for one character’s walk cycle.
Task B · Attack sound
Sound only
Audition two short sounds, then integrate the chosen one.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Create B from mainline → inspect progress in A and B → draft a request to sync mainline in B · Play; use fullscreen for details Dark UI · Local teaching data with seeded execution states.
Bring the summary, asset paths and decisions to each new conversation. Check its base and any uncommitted-file choice; cancel and reselect if the base is wrong.
A changes animation only and B sound only. Compare options before integration. Advanced topics below has the detailed briefs and actual material demos. See advanced topics →
Before merging
Playtest, then use Merge into mainline… to review the destination, changes and checks. The destination is mainline; resolve conflicts or failed checks before continuing.
01
Merge animation A first
Select and test A, checking animation and gameplay. Use ⋯ → Merge into mainline… and wait for the merge to finish.
02
Sync and retest inside B
Return to B · Attack sound and send the request below. Open B’s updated browser playtest after syncing. Check A’s animation and B’s sound together, also for a Windows target. Validate the final package separately on Windows. Resolve conflicts first.
03
Merge B and test mainline
After reviewing B, merge it using the same menu. Check mainline in 🚀 Release, then create a candidate build as described below. For final acceptance, Web uses that candidate’s Preview ↗ link; Windows uses its complete ZIP, extracted and tested on Windows. Neither uses an old A/B tab instead.
Example prompt
Example promptA · Character walk animation has entered mainline. Sync the latest committed mainline into this B · Attack sound task, preserving B’s audio changes. Explain conflicts first. Provide a new B preview and changed-file list. Do not merge yet.
Check the resultMerge A → sync and retest B → merge B. Then build and playtest a mainline candidate. Animation and sound are optional additions; you can publish the base directly.
06
06 / 09 · Publish and share
Publish and share
Windows packages and minigrove.games Web publication have separate delivery paths. Both start with a mainline candidate and review of that exact build.
When your project offers Windows builds and its checks are ready, follow these steps for a testable package. Merging into mainline prepares a candidate; it does not establish Windows acceptance or public publication.
01 · Enable Windows and check the build computer
🚀 Release → Platforms and candidates → Windows. The project owner enables Windows and saves. Cloud projects use their project computer by default; choose a computer if a selector is offered. Check both engine and computer readiness.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Windows settings: Godot / GDScript, build computer and enable option; readiness is seeded · Select image to enlarge Dark UI · Local teaching interactions; build outcomes are seeded. No Windows playtest is claimed.
02 · Create a candidate from mainline
Merge the production task into mainline, then choose ＋ New candidate…. Check main and the version number. The Windows row should name Windows ZIP download. Confirm and follow this candidate’s build progress; first-time preparation may take longer.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Candidate confirmation: mainline source and Windows ZIP target; candidate results are seeded · Select image to enlarge Dark UI · Local teaching interactions; build outcomes are seeded. No Windows playtest is claimed.
03 · Download the full ZIP and test on Windows
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Download .zip and personal playtest confirmation on one candidate; build result is seeded and confirmation remains unchecked · Select image to enlarge Dark UI · Local teaching interactions; build outcomes are seeded. No Windows playtest is claimed.
01
Extract and run
Choose Download .zip in the Windows row. Extract the complete archive, keep all its files and launch game.exe.
02
Play the core loop
Check movement, turn order, attacks, win/loss and restart, then window/fullscreen, sound and exit. Test offline operation if required; reopen to check saves when present.
03
Confirm your own test, then deliver
After personally passing this package on Windows, check I have playtested this on Windows. Share the complete ZIP when delivering to nonmembers; project download links require current membership.
Check the resultKeep the candidate version and test result. Open a fix task for issues, merge it, then create and test a new candidate. An old package or confirmation does not test the new one.
Build failed or not ready
Read the failed row and How to resolve. Use Let AI fix for project errors. Follow the page’s guidance for computer/environment problems, then retry or create a new candidate. Keep the version, error and reproduction steps instead of duplicating requests.
A browser development preview is not a publicly published Web release. Windows ZIP delivery, public Web publication on minigrove.games and Steam distribution are separate steps; Steam requires additional preparation.
Web: create a release candidate
Projects with Web publication enabled can publish publicly to minigrove.games.
Open 🚀 Release → Platforms and candidates. If Web is not enabled, the owner enables it and selects a capable build computer. Choose ＋ New candidate…, check the mainline source and commit, choose a version number and confirm. When this candidate’s Web build shows Build preview, select Preview ↗ on that same row. This is a fixed version; later mainline changes do not automatically replace it.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Source commit, Web build label and Preview link for one candidate; build progress is seeded · Select image to enlarge Dark UI · Real local sample files; AI replies and cloud build progress are seeded for teaching.
Check the resultTest movement, turn order, attacks, win/loss and restart in this mainline build. Review animation and sound if added. An old task preview does not replace testing this candidate.
Publish to minigrove.games
Choose Publish publicly in the minigrove.games platform row. Check its candidate and Web label, then review title, description, cover and visibility. Later mainline changes need a new, tested candidate.
Example version identifiers
Three identifiers for the same version
v0.1.0-rc.1 main @ b84539f2909a3d870c288e1237b7b57b4add974c v0-1-0-rc1
Check main’s commit when creating the candidate. Once its build is ready, note the Web label on that row. After choosing Publish publicly, the version selector and preview must name that same Web label. The public form shows the build label; check the source commit back in candidate details.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Create a candidate from mainline → check the build → open that build’s publication form; the recording stops before public confirmation · Play; use fullscreen for details Dark UI · Real local sample files; AI replies and cloud build progress are seeded for teaching.Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Choose the same Web build in the publication form and check description, cover and visibility · Select image to enlarge Dark UI · Local teaching data with seeded execution states.
When ready to make it public, the owner submits the publication form. Open the public URL in a window without project access and play it. Later updates need explicit publication again; the recording stops before confirmation.
Check the resultGet the public URL, then open and play it in a window without project access.
07
07 / 09 · Advanced workflows
Advanced workflows
Add animation, sound or a release plan when needed. Define deliverables, compare options, integrate and review.
Create character frame animation
Start with a character reference and one action: idle, walk or attack. Approve key poses, generate the sequence, then integrate it into the game. Seedance is another animation option, usually at a higher cost. Choose for your art style, motion needs and budget; validate one short action before producing a batch.
Actual Bajiao character assets: armored walk and drummer march; each action has 33 frames played at 8 fps · Play; use fullscreen for details Actual transparent Bajiao frame sequences · Playback on a dark background.
01
Choose a character and action
Supply a reference, direction, style and loop requirement. Start with one action.
02
Review poses and playback
Check silhouette, foot position and timing. Inspect frames for distortion and the loop for jumps.
03
Integrate the approved sequence
Request transparent frames or a sprite sheet, then connect it to character states. Test transitions in the game.
See actual key frames and an example briefFrames 1, 7, 13, 19, 25 and 33 from each 33-frame action · Select image to enlarge Actual transparent Bajiao frame sequences · Playback on a dark background.
Example promptUse this armored character reference for a right-facing walk cycle. Preserve the face, armor and shield, keep a stable foot anchor and use transparency. Show key poses and playback first. After approval deliver frames or a sprite sheet, then integrate the walk state without changing gameplay or audio.
When listed in the project’s skill menu, use /mg-sprite-gen for character frames and /mg-build-character-frame-animation to build the animation.
Check the resultCheck smooth looping, consistent character design and state transitions such as idle to walk. Review the animation again in the game after approving the asset preview.
Fruit-catching example: a simple feedback animationOperation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Compare two basket bounce strengths → choose the soft variant → trigger a catch; this is feedback animation, separate from the character frame example · Play; use fullscreen for details Dark UI · Real local sample files; AI replies and cloud build progress are seeded for teaching.
Example promptTask A · Catch animation. Start from current mainline. Add basket squash-and-stretch on catch. Change animation only; preserve collisions, values and audio. Provide two previews, integrate the chosen one, and list changed files, preview and acceptance steps.
Create music and sound
For music, specify mood, length and looping. For effects, specify trigger, duration and repeated behavior. Audition two options before integrating. External audio services may need another key; state missing prerequisites or start with procedural sound effects.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Play two WAV files in the tool → inspect the delivery checklist → state the chosen variant; the recording is silent, and samples below are playable · Play; use fullscreen for details Dark UI · Real local sample files; AI replies and cloud build progress are seeded for teaching.Example prompt
Example promptTask B · Attack sound. Start from current mainline. Make short basic-hit and battle-victory sounds. Provide two playable samples before integrating the chosen one. Change audio only; preserve visuals and rules. Control repeated-trigger volume. List sample locations, final assets, triggers and preview.
Earlier fruit-catching sample: audio and integration files
These paths belong to the browser demo project; ask AI for the actual paths in Godot or other engines. Choose A · Soft squash-and-stretch and catch-soft.wav. Audition files repeat; the integrated effect is the short single sound. catchFruit() triggers animation and sound together. Repeated catches reuse the player and reset its position to avoid overlapping tracks.
Check the resultAudition, then check final files and triggers. In the integrated version, catch once and repeatedly, wait for the 30-second ending and restart. Confirm chosen animation/sound are integrated while movement and scoring still work.
Roadmap and team responsibilities
Agree on milestones and responsibilities before production. Name confirmed owners only; leave undecided work unassigned.
When the project supports roadmaps and a capable computer is available: 🗺 Roadmap → Design roadmap. On phones, choose Roadmap from More.
Operation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Design roadmap → review the draft → confirm responsibilities → view the Roadmap page · Play; use fullscreen for details Dark UI · Actual local teaching-account interactions; AI replies and roadmap results are seeded.
01
Discuss the goal
Share platform, date, scope and capacity; ask AI to draft first.
02
Confirm responsibilities
Agree with teammates, then confirm owners, reviewers and unassigned work.
03
Save and execute
After approval, view the roadmap and create tasks for ready work items.
See the responsibility draft and example briefOperation reference from a separate fruit-catching project
These earlier teaching captures locate the controls. Their project, task and build content belongs to the fruit-catching sample, not this tactical RPG.
Draft: Qing owns gameplay, Lin owns animation, sound remains unassigned · Select image to enlarge Dark UI · Actual local teaching-account interactions; AI replies and roadmap results are seeded.
Example promptInspect this project and plan from playable to release. Confirm platform, date, scope and capacity. List milestones, work items, owners, dependencies and acceptance checks. Draft first and save after our approval; do not create tasks or publish yet.
The roadmap is visible only to project members. Listing an owner is a plan; confirm it with that person. Use I want to edit for changes, mention teammates to agree on execution and update progress in the roadmap. See same-chat handoff →
Let tasks hand work to each other
For example, have art pass character files, size and direction requirements to animation, then pass the result to integration. Name the destination task, files, approved choices and acceptance checks rather than only asking them to coordinate.
When direct handoffs are supported, the system delivers the message and files to the target task with source and delivery receipts. Check Sent to confirm delivery; follow any pending or limited-state instructions. Automatic chains are bounded and may need a member to continue. A handoff does not merge versions: playtest and merge into mainline separately.
A few useful working tips
Select text and explain it
Select a passage in a finished AI reply and choose Explain this passage to ask follow-up questions. Explanations are private to you and available in Ask on the side. Use them for terminology, code or unclear reasoning.
Tell AI your preferences
Use Personal settings → Tell MiniGrove your preferences to describe how you want to work, such as “lead with the conclusion and start with a small sample.” Keep communication preferences there; put game rules, chosen art direction and team decisions in the project for teammates to see. You can update these preferences from the same personal settings entry.
Branch a conversation to ask a question
Use the conversation’s available branch or discussion entry to explore another option with the current context, such as speed-based turn order. State that you want discussion without edits first; create or continue production work after choosing a direction.
08
08 / 09 · Games and inspiration
Games and inspiration
Explore the gameplay and styles of public games on minigrove.games.
Bring a game link and the details you like into a discussion to compare approaches for your project.
Check the preparation step, latest update and any error. The first setup can take longer; gather ideas while it progresses. If it stalls or fails, keep the page link, step and message for support instead of repeatedly creating projects or resending tasks.
How many AIs can run at once?
It depends on your account's plan, and is also limited by the project's computer capacity. Covered projects share account capacity. BYOK does not increase it. Check your current plan and computer capacity.
Preview still shows an old version. What now?
Check the current conversation’s task name and Preview label. Follow the current task if another is shown, and open an offered update. A selection subtask, its parent and a mainline candidate are different versions; review final mainline through the matching candidate in Release.
What do automatic merge-back and AI checks mean?
A subtask opened with Subtask merges back into its fixed parent once its checks pass, possibly before your own playtest. AI/build checks do not mean you approved the feel. For a change you want to try before it comes back, skip Subtask and ask in the current task; if a merged change is not right, ask for more. Subtasks have their own progress strip; ordinary tasks use Merge into mainline.
How do I request edits for a desktop game?
During development, prioritize browser playtests and preview marks in an embedded preview. For issues found in the final Windows package, send screenshots, candidate version, reproduction steps and expected behavior to a fix task. Browser checks do not replace Windows testing.
How do I deliver a Windows game?
A Godot project on a computer with the required build capability can produce a Windows package. Download it and test startup, input, audio and exit on Windows. This Web example does not prove a desktop build; Steam release needs separate preparation.
Does a key or subscription increase concurrency?
No. They choose who pays for the model; concurrency and computer capacity still follow the current plan and machine. Members share the project’s current model source without configuring it individually. The project owner changes the source when needed.
Give feedback directly to the MiniGrove team
For MiniGrove issues or suggestions, use Feedback on the right rail; on narrow screens choose More → Feedback to developers. Continue game-production requests in your project’s AI tasks.
See what MiniGrove is building, share a public idea or choose “I need this too”; sign in when prompted. Use private project feedback for account issues and logs.
Mention MiniGrove support in your project
Open @ below the composer and select MiniGrove support. Include what you are doing, where you are stuck, expected and actual results, and a screenshot or error reference. This reaches human support; send game-production instructions to the project AI.
Choose support and review the unsent help draft · Select image to enlarge Actual support picker and an unsent help draft in a local teaching interface.
Before sending, review the optional 7-day project access grant. You can uncheck it or revoke it later. Grant access as needed; response time follows the actual support reply.
Wide screen: Feedback on the right
Right rail → Feedback; the orange focus ring marks the entry · Select image to enlarge Dark UI · Actual local teaching-account entry; no feedback submitted.
Include the page, steps, expected and actual results, and any error message or reference. Sending includes your name, email, project ID and browser version; replies go to your email. Keep keys, passwords and authorization codes out of the report.
For screenshots or recordings, or if Feedback is unavailable, email [email protected] with the page link and reproduction details.
Help us improve
Was this guide helpful?
Need help? Keep the page link, steps and error message. [email protected]
This tutorial uses local UI captures and seeded states; it does not establish completed AI production, Windows build acceptance or public publication.
