23.1 Overview
Game Developer is AIUNIFY PROS SUITE’s AI-powered browser-game creation workspace.
Although the Sidebar identifies the Tool as:
Game Developer
the current workspace itself is titled:
Game Maker
with the description:
“Describe your game idea and have AI generate a fully playable HTML file instantly”.
Game Developer currently provides subscriber-facing workflows for:
23.2 Where Game Developer Is Located
Navigate to:
Sidebar → Core Tools → Game Developer
The verified route is:
/game-maker
and the Sidebar currently marks the Tool as:
New.
23.3 Game Developer vs. Game Maker
You will see two Names associated with this feature.
Sidebar Name
Game Developer
Workspace Name
Game Maker
They refer to the same /game-maker workspace in the current version.
23.4 Authentication Is Required
The Game Maker route checks whether you are signed into PROS SUITE.
If you are not authenticated, it redirects toward:
/login.
23.5 Feature Access Is Also Required
The page is protected by:
FeatureGuard → game-maker.
Therefore, successful sign-in alone does not guarantee Game Developer access.
Your current account must also be allowed to use the Tool under the access rules explained in Chapter 8.
23.6 Game Developer Is Not a Standard Generator
Game Developer does not use the simple Standard AI Generator workspace documented in Chapter 12.
Instead, it has a specialized interface containing:
23.7 What Game Developer Creates
The AI is instructed to generate:
one complete HTML file
for a browser-based Game.
The generated file can contain the:
inside a single .html output.
23.8 Single HTML File Does Not Necessarily Mean Offline
There is an important distinction.
The generation instructions also explicitly encourage references to external resources such as:
Therefore:
A downloaded Game is a single HTML file, but it is not source-verified as completely offline/self-contained in the sense of containing every external library, Font, or image inside the file.
Some generated Games may require internet access for externally referenced resources.
23.9 Main Workspace Layout
Game Maker is divided into two major working areas.
Left
Game Studio
where you describe/configure the Game.
Right
Preview
where the Game is built and played.
Below those is:
Saved Games
for account-persisted projects.
23.10 Game Studio
The left Card is titled:
Game Studio
with:
“Define the core mechanics and theme of your game”.
23.11 Description
The primary Prompt field is labeled:
Description.
Describe the Game you want AIUNIFY to build.
23.12 Description Placeholder
The current example is:
“e.g. A neon-themed space shooter where you collect gems to upgrade your ship...”
23.13 No Source-Verified Description Character Limit
The current Description Textarea does not define a visible:
limit.
This differs from some other PROS SUITE Tools.
23.14 What to Include in Your Game Description
A strong Game request can specify:
23.15 Weak Prompt
For example:
Build a racing game.
leaves many decisions entirely to the AI.
23.16 Stronger Prompt
For example:
Create a futuristic top-down hover-car racing game. The player dodges traffic, collects energy boosts, earns points for distance, and has three lives. Increase speed every 30 seconds. Include a Start screen, score and lives HUD, Game Over screen, keyboard controls, neon city visuals, particle effects, and a Retry button.
This gives the Game Developer a much clearer target.
23.17 Design the Game Loop in Your Prompt
A useful Game description should answer:
What does the player repeatedly do?
For example:
Move → Avoid → Collect → Score → Increase Difficulty → Continue
or:
Aim → Shoot → Defeat Enemies → Collect Power-ups → Survive Waves
A clear Game loop helps the generator structure playable mechanics.
23.18 Define the Win or Failure Condition
Consider explicitly identifying:
For example:
The player wins after surviving five waves.
23.19 Describe Controls Where Important
Even though the current internal Game settings include a Keyboard control default, your Description can provide more specific creative direction.
Examples:
The current interface's separate Mobile Friendly control is described later in this chapter.
23.20 Add Mockup/Ref Image
Next to Description is:
Add Mockup/Ref Image.
Use this when you want the AI to have a visual reference in addition to your written Description.
23.21 Accepted Reference File Type
The current file selector accepts:
image/*.
Therefore, the verified reference attachment type is an image.
23.22 Reference Image Size Limit
The current maximum is:
5 MB.
23.23 Image Too Large
If the image exceeds 5 MB, the exact current message is:
“Please upload an image smaller than 5MB.”
23.24 What Happens After Upload
The image is converted into browser-readable image data and stored with the current Game Maker session.
A thumbnail appears inside the Description area.
23.25 Remove Reference Image
Select the X attached to the reference thumbnail to remove it.
23.26 Reference Image Is Sent to the AI
When you build the Game, the current request includes the reference image with the generation request.
Therefore, it is not merely a decorative image Preview.
23.27 Example — Visual Mockup
You could attach a UI mockup and enter:
Use the attached mockup as the visual direction. Build a playable space-defense game with the same futuristic panel layout, but add a score HUD, enemy waves, shields, and a restart screen.
23.28 Reference Images Are Optional
A Game can be generated using the Description and Configuration without attaching an image.
23.29 Reference Image Is Not Persisted with Saved Games
The Save Game request stores:
but does not send the current reference image.
Therefore:
If you later reopen a saved Game and want to regenerate it using the same reference image, reattach that image.
23.30 Demo Prompts
Game Studio includes:
Try a demo prompt.
Four current examples are provided.
23.31 Flappy Bird Clone
Preset Name:
Flappy Bird Clone
Prompt:
“Create a Flappy Bird clone with a cyberpunk theme and neon pipes.”
23.32 Space Shooter
Preset Name:
Space Shooter
Prompt:
“Build a top-down space shooter where you fight waves of alien ships and collect power-ups.”
23.33 Memory Match
Preset Name:
Memory Match
Prompt:
“Design a card memory matching game with a clean minimalist UI and smooth animations.”
23.34 Dino Runner
Preset Name:
Dino Runner
Prompt:
“Create a side-scrolling endless runner game similar to the Chrome Dino game but with a desert fantasy theme.”
23.35 Selecting a Demo Prompt
Selecting a Demo Prompt places its complete Prompt into:
Description.
It does not automatically generate the Game.
You can edit the Prompt before selecting Build Game Now.
23.36 Advanced Configuration
Below the Demo Prompts is:
Advanced Configuration.
The current configuration area is expanded by default.
23.37 Collapsing Advanced Configuration
Use the Chevron control beside Advanced Configuration to collapse or reopen it.
Collapsing the panel does not reset your selected values.
23.38 Current User-Selectable Game Settings
Advanced Configuration currently exposes:
23.39 Default Genre
The current default Genre is:
Platformer.
23.40 Available Genres
The current Genre options are:
23.41 Genre Provides Structural Direction
Genre is included directly in the AI generation instructions.
For example, selecting:
Puzzle
provides different structural direction than:
Shooter.
23.42 Match Genre to the Description
For predictable generation, avoid obvious conflicts such as:
Description: First-person racing Game
Genre: Puzzle
unless the hybrid experience is intentional.
23.43 Default Visual Style
The current default is:
Premium UI.
23.44 Available Visual Styles
Current Visual Style choices are:
23.45 Visual Style Is Separate from Genre
For example:
Genre: Shooter
could be combined with:
This lets you separate Game mechanics from appearance.
23.46 Default Difficulty
The current default Difficulty is:
Medium.
23.47 Available Difficulty Levels
Current choices are:
23.48 Difficulty Is Sent as Generation Guidance
The selected Difficulty is included in the Prompt sent to the AI.
It is guidance for the generated Game rather than a guaranteed standardized numeric difficulty algorithm.
23.49 Mobile Friendly
Advanced Configuration contains:
Mobile Friendly.
23.50 Mobile Friendly Is Off by Default
The source default is:
mobileFriendly: false.
23.51 What Mobile Friendly Changes in the Generation Instruction
When enabled, the AI receives:
“Yes, add touch controls”
as part of the Game settings.
When disabled, it receives:
“No”.
23.52 Enable Mobile Friendly for Phone/Tablet Games
If the Game needs to be playable without a physical Keyboard, enable:
Mobile Friendly
before generating.
23.53 Mobile Friendly Is AI-Generated Behavior
The toggle instructs the AI to add touch controls.
The source does not contain a separate runtime system that automatically converts every generated Keyboard Game into a standardized touch interface.
Test the resulting Game on an actual mobile device before deployment.
23.54 No Separate Theme Selector Is Visible
The Game configuration model contains Themes, including:
but the current Game Studio does not render a Theme selector.
23.55 Current Internal Theme Default
The current Game-generation Configuration begins with:
Sci-Fi
as its internal Theme default.
Because no separate Theme selector is currently displayed, use the Description when you want a different thematic direction.
For example:
Make the setting medieval fantasy rather than science fiction.
23.56 No Separate Control-Type Selector Is Visible
The current Configuration also contains an internal Control Type but does not expose a control-type selector in Game Studio.
Its default is:
keyboard.
23.57 Use the Description to Clarify Controls
If you need:
state those requirements in the Description.
Mobile Friendly can additionally request touch controls.
23.58 Build Game Now
Once Description contains text, select:
Build Game Now.
23.59 Build Game Now Is Disabled Without a Prompt
If Description is blank, the main generation button is disabled.
23.60 Prompt Required
The generation hook also performs its own validation.
If the Prompt is empty, the exact current notification is:
Prompt Required
“Describe the game you want to create.”
23.61 What Is Sent to the AI
The generation request includes:
23.62 Game Developer Uses the Shared AI Model
Game Developer reads:
selectedModel
from your normal PROS SUITE AI settings.
Therefore, the Model selection concepts in Chapter 10 apply to Game generation.
23.63 No Separate Game Model Selector
There is no Game-specific Model dropdown inside Game Studio.
Change the shared Model using the normal PROS SUITE Header Model Selector when necessary.
23.64 Provider API Keys Can Apply
Game Maker sends your configured provider API Keys with the AI-generation request when they are present.
Therefore, Chapter 11 can also apply when using a Model that requires a personal provider credential.
23.65 Reference-Image Compatibility Can Depend on the Selected Model
The source verifies that an attached image is sent with the generation request.
It does not establish that every selectable AI Model supports image input equally.
If generation fails specifically when a reference image is attached, test again without the image or with an appropriate available Model.
23.66 Generation Begins by Clearing the Previous Final Game
When a new generation starts, Game Maker clears:
and moves to:
thinking.
Therefore, preserve a Game you care about before starting another generation.
23.67 Generation Stages
The current stages are:
23.68 Analyzing Game Concept
The visible Thinking label is:
Analyzing game concept...
23.69 Writing Game Code
The Generating label is:
Writing game code...
23.70 Compiling & Optimizing
The Compiling label is:
Compiling & optimizing...
23.71 Game Ready
The Done label is:
Game ready!
23.72 Generation Failed
The Error label is:
Generation failed.
23.73 Developing...
While generation is active and no final Game exists, the Preview header can display:
Developing...
23.74 Generation Progress
During generation, Game Maker displays:
23.75 Progress Is an Estimate
During streaming, the percentage is estimated from the amount of generated text.
It rises toward a maximum of approximately:
90%
during streamed code generation.
23.76 95% Compiling Stage
After generation finishes and valid HTML is detected, the workflow sets:
95%
during its Compiling stage.
23.77 100% Means the Final HTML Was Accepted
After the final HTML is assigned to the Game Preview, Progress becomes:
100%.
23.78 Progress Is Not Provider-Reported Build Completion
The streaming percentage is calculated from generated-text length rather than returned as a precise provider progress measurement.
Treat it as a helpful progress indicator.
23.79 Live Game Building
One of Game Developer's more distinctive features is that it can render streamed HTML while the AI is still producing it.
When streamed Game content becomes available, the Preview runs in:
Building Live
mode.
23.80 Building Live Indicator
During live generation, the Preview displays:
Building Live.
23.81 Live Preview Is Provisional
The streamed code may be incomplete while it is still arriving.
Game Maker performs limited temporary closing of incomplete HTML/style/body tags so the partially generated output can be previewed.
Therefore:
A visual glitch during Building Live does not necessarily mean the final Game will contain that same problem.
Wait for final completion before judging the finished result.
23.82 Live Preview Can Change Continuously
Because the Preview is rebuilt from the accumulating streamed HTML, the design and gameplay can change while the AI is still writing the Game.
23.83 Stop Generation
During an active generation, the normal Build button is replaced by:
Stop Generation.
23.84 What Stop Generation Does
Selecting Stop Generation aborts the active AI request and resets:
23.85 Your Inputs Remain After Stopping
The Stop function does not clear:
You can revise the instructions and start again.
23.86 Partial Game Is Not Promoted to a Completed Game
After cancellation, the partial streamed code is not assigned as the final:
generatedHtml.
Therefore, the normal:
controls do not become available from that canceled partial generation.
23.87 Stopping Does Not Establish a Token Refund
The client source proves that the browser request is aborted.
It does not establish the server-side Token-accounting result after a request has already started.
Therefore, this manual does not promise that stopping generation automatically refunds any AI usage.
23.88 AI Output Is Cleaned Before Final Preview
When generation finishes, Game Maker attempts to:
23.89 Valid HTML Is Required
If the final response does not contain an HTML document, Game Maker raises:
“AI did not generate valid HTML game code.”
23.90 Successful Generation Message
When the Game is accepted, PROS SUITE displays:
Game Created!
“Your game is ready to play.”
23.91 Generation Failure
If generation fails, Game Maker displays:
Generation Failed
with the returned Error message.
23.92 Error Preview
The Preview area can also display:
Generation encountered an error.
23.93 Retry
The Error Preview includes:
Retry.
This starts generation again using the current Description and Configuration.
23.94 No Game Generated Yet
Before any Game exists, Preview displays:
No game generated yet
and:
“Enter a description on the left and click "Build Game Now" to start your creative process.”
23.95 Final Preview
Once generation succeeds, the Preview displays the final HTML Game inside a sandboxed browser frame.
23.96 LIVE
When a completed Game exists, the Preview header shows:
LIVE.
23.97 The Preview Is Interactive
The Game Preview iframe allows scripts to run, enabling the generated JavaScript Game to be played directly inside PROS SUITE.
23.98 Click Inside the Game When Keyboard Controls Do Not Respond
Browser Games often need focus before they receive Keyboard input.
If Arrow keys, WASD, or Space do not initially respond:
This is standard browser behavior and a useful first troubleshooting step.
23.99 Preview Size
Outside Fullscreen, the Game Preview is responsive and uses increasing fixed-height ranges for different screen sizes, reaching approximately 600px on larger screens.
23.100 Fullscreen
After a completed Game exists, select the Fullscreen icon in the Preview header.
23.101 What Fullscreen Does
Game Maker requests Fullscreen specifically for the Game Preview workspace.
23.102 Exit Fullscreen
Select the Minimize icon or use your browser's standard Fullscreen exit method.
The page monitors browser Fullscreen changes and resets its local Fullscreen state when Fullscreen ends.
23.103 Fullscreen Is for Testing and Playing
Fullscreen does not:
It only changes how the current Preview is displayed.
23.104 Copy Code
Once a completed Game exists, the Preview toolbar includes:
Copy Code.
23.105 What Copy Code Copies
Copy Code writes the complete generated HTML source to your clipboard.
23.106 Copy Confirmation
The exact current notification is:
Copied!
“Game source copied to clipboard.”
23.107 Copy Code Does Not Save the Game
Copying source code does not add the Game to:
Saved Games.
Use:
Save Game
when you want account persistence.
23.108 Download HTML
The Preview toolbar also contains:
Download HTML.
23.109 Downloaded Format
The generated Game is downloaded as:
HTML.
The Blob MIME type used by the current workspace is:
text/html.
23.110 Download Filename
The current filename pattern is:
game-[timestamp].html.
For example, the actual filename contains a numeric timestamp generated at Download time.
23.111 Download Confirmation
After initiating the download, Game Maker displays:
Downloaded!
“Game saved as HTML file.”
23.112 The Downloaded File Is Runnable in a Browser
Because the output is HTML containing browser Game logic, it can generally be opened as a webpage in a compatible browser.
However, behavior can differ from the built-in PROS SUITE sandbox.
23.113 External Dependencies May Still Need Internet Access
A downloaded HTML file may load:
from external URLs because those resources are explicitly encouraged in the generation instructions.
Test the downloaded file under the conditions in which you intend to use it.
23.114 Download Does Not Publish the Game
Download HTML creates a local file.
It does not:
23.115 No ZIP Export Is Established
The current Game Developer does not provide:
The verified export is a single .html file.
23.116 Save Game
The Preview toolbar contains:
Save Game.
Use this to persist a completed Game to your PROS SUITE account.
23.117 Save Game Appears Only After Generation
The Save Game control is displayed only when:
generatedHtml
exists.
You cannot save an empty or merely partial live generation.
23.118 Saving State
While a Save is in progress, the Save control becomes disabled and displays a loading indicator.
23.119 What Save Game Preserves
The client currently submits:
23.120 How the Saved Game Name Is Created
The current UI does not ask for a separate Game Name before saving.
Instead, it automatically uses the first:
30 characters
of the Game Description.
If the Description exceeds 30 characters, it adds:
...
23.121 Example Saved Name
A Prompt such as:
Create a futuristic space shooter with three levels...
could be represented in Saved Games using its truncated opening text rather than a manually entered Project Name.
23.122 No Rename-before-Save Field
The current Game Developer does not provide a:
Game Name
input in Game Studio.
The saved Name is generated automatically from the Prompt.
23.123 Game Saved Successfully
When Save succeeds, the exact current notification is:
Game saved successfully!
The Saved Games collection is then refreshed.
23.124 Failed to Save Game
If the Save request is rejected, Game Maker displays:
Failed to save game.
23.125 Error Saving Game
If the Save operation throws a client/network Error, the interface displays:
Error saving game.
23.126 Saved Games Are Account-Specific
The underlying Game persistence model includes the owning user's Email and retrieves Games for that user ordered by the most recently updated records.
23.127 Saved Games
Below the builder is:
Saved Games.
This is the persistent Game collection.
23.128 Saved Games Load Automatically
When Game Maker opens, it requests the current saved Game collection automatically.
23.129 No Manual Refresh Saved Games Button
The current Saved Games heading does not provide a Refresh control.
The list refreshes automatically after:
and when the page initially loads.
23.130 No Saved Games Yet
If nothing has been saved, the interface displays:
No saved games yet
and:
“Build your first game and save it to see it appear here in your collection.”
23.131 Saved Game Card
Each Saved Game Card contains a visual miniature Preview created directly from the saved Game code.
23.132 Saved Game Preview Is Not a Static Screenshot
The Card uses an embedded HTML frame generated from the saved code rather than relying on a separately generated screenshot.
23.133 Saved Preview Is Non-Interactive
The small Card Preview has:
pointer-events-none
so it functions as a visual Preview rather than the primary playable environment.
Use:
Play Again
to load the actual playable Preview.
23.134 Saved Game Information
Each Card displays:
23.135 Genre Display
The Card displays the saved Genre as a small badge.
23.136 Updated Date
Saved Game Cards display the project's:
updatedAt
date using the browser's local Date formatting.
23.137 Prompt Preview
The original Prompt appears beneath the Card information and is visually limited to approximately two lines.
23.138 Play Again
Hover over the Saved Game Preview and select:
Play Again.
23.139 What Play Again Loads
Play Again restores:
into the active Game Maker workspace.
23.140 Play Again Does Not Regenerate the Game
The saved HTML is loaded directly.
No new AI-generation request is made simply by selecting Play Again.
23.141 Play Again Marks the Current Game Done
After loading the saved code, the workspace sets the generation state to:
done.
That gives you access again to:
23.142 Play Again Scrolls Back to the Builder
The current workflow scrolls toward the top of the page after loading the Game.
23.143 Play Again Attempts Fullscreen
Shortly after loading the Game, the current implementation attempts to activate Fullscreen.
Browser Fullscreen policies can affect whether that request succeeds.
23.144 Saved Difficulty Is Not Restored
The current Save request does not persist Difficulty, and Play Again restores only:
among the Advanced Configuration values.
Therefore:
If you later Regenerate a saved Game, verify the current Difficulty setting first.
23.145 Saved Mobile Friendly Setting Is Not Restored
The current Save request also does not preserve the Mobile Friendly toggle.
A Saved Game's existing HTML still contains whatever controls were originally generated, but regenerating it uses the current Mobile Friendly setting.
23.146 Reference Image Is Not Restored
Play Again does not restore the original reference/mockup image.
Reattach it before Regeneration when that visual reference remains important.
23.147 Internal Theme and Control Type Are Not Stored per Saved Game
The saved Game model preserves:
but does not include per-project Difficulty, Theme, Control Type, or Mobile Friendly values.
Accordingly, those settings should not be assumed to be recoverable from Saved Games.
23.148 Regenerate Game
After a Game has been successfully generated or loaded from Saved Games, the main button changes from:
Build Game Now
to:
Regenerate Game.
23.149 Use Regenerate to Create Another Version
Before selecting Regenerate Game, you can change:
Then generate another version.
23.150 Regenerate Is a Full Generation, Not an Incremental Edit
This is an important distinction.
When generation starts, the current completed HTML is cleared, and the new AI request is based on the current:
The previous Game code is not sent as an editing context.
Therefore:
Regenerate Game creates a new Game version from the instructions; it is not a line-by-line AI edit of the previous Game.
23.151 Example — Refining Through Regeneration
Suppose your first Game works but is too slow.
Instead of expecting an in-place patch, modify the Description to include:
Keep the same concept, but increase player speed, make enemy waves 20% faster, add a visible health bar, and make the Game Over screen more cinematic.
Then select:
Regenerate Game.
The AI creates a new full HTML version.
23.152 Preserve the Old Version Before Regenerating
Because Regeneration clears the current final Game at the beginning of the new request, first use one or more of:
if you may need the existing version later.
23.153 There Is No Built-In Code Editor
The current Game Maker does not expose a source-code editing pane where subscribers can directly modify generated HTML, CSS, or JavaScript.
You can:
but not edit the code directly inside Game Maker.
23.154 Copy Code for External Editing
If you want precise manual changes:
There is no source-verified Upload Modified HTML back into Game Maker.
23.155 No “AI Edit This Game” Chat Is Established
Unlike Website Builder's specialized editing workflow, Game Developer does not currently provide a source-verified conversational AI edit panel for the generated Game.
Refinement is performed through:
Modify Instructions → Regenerate Game.
23.156 Save Before Experimenting
A practical versioning workflow is:
Generate V1
↓
Save Game
↓
Change Prompt
↓
Regenerate V2
↓
If better:
Save Game
This keeps previously saved versions available.
23.157 Save Game Is Not a Verified Overwrite Control
The visible UI contains:
Save Game
but does not expose:
as separate subscriber actions.
Treat each saved result according to what appears in Saved Games rather than assuming the existing Card will necessarily be overwritten.
23.158 Delete Game
Each Saved Game Card contains a Trash control.
23.159 Delete Confirmation
Selecting Delete opens:
Delete Game
with:
“Are you sure you want to delete this game? This action cannot be undone.”
23.160 Confirm Delete
The confirmation button is:
Delete.
23.161 Successful Deletion
When deletion succeeds, Game Maker displays:
Game deleted.
The Saved Games collection is then refreshed.
23.162 Failed to Delete Game
A rejected Delete request displays:
Failed to delete game.
23.163 Error Deleting Game
A request/network exception displays:
Error deleting game.
23.164 Deleted Games Cannot Be Restored Through a Verified UI
The confirmation explicitly states deletion cannot be undone.
No:
function is established in the current Game Developer source.
23.165 No Rename Saved Game
Saved Game Cards do not expose:
Rename.
Since the Name is generated from the Description, use a distinctive opening phrase in the Prompt when project identification matters.
23.166 No Saved Game Search
The current Saved Games area does not contain:
23.167 No Saved Game Folders
There are no source-verified:
for organizing saved Game projects.
23.168 No Duplicate Button
The current Cards do not provide:
Duplicate.
You can, however:
23.169 Generated Games Are Not Automatically Saved
Successful Game generation creates the Game in the current browser workspace.
It does not automatically add it to Saved Games.
You must select:
Save Game.
23.170 Refreshing Before Saving Can Lose the Current Game
The active generated HTML is held in current page state until you explicitly Save or Download it.
No automatic recovery of an unsaved current Game is established.
Therefore:
Save or Download important Game results before refreshing or leaving the page.
23.171 Saved Games Are Persistent
By contrast, the source defines an account-specific Game Project record containing:
This is the basis for the persistent Saved Games collection.
23.172 Saved Cards Use the HTML Code for Preview
Although the underlying Game record supports an optional Preview field, the current Saved Games UI does not rely on it.
It renders the saved Game code directly in a small iframe.
23.173 Intended Generated Game Structure
The AI's Game system instructions request:
23.174 These Are Generation Instructions, Not Guarantees
The AI is instructed to create a polished, playable Game.
However, generated software can still contain:
Test every generated Game before publishing or distributing it.
23.175 Start Screen Expectation
The AI is specifically instructed to create a:
Start Screen
with:
If a generated Game omits it, add that requirement explicitly to your next Prompt and Regenerate.
23.176 Game Over Screen Expectation
The generation instructions also request a:
Game Over Screen
with:
23.177 HUD Expectation
The AI is instructed to create a responsive HUD that can display Game information such as:
where appropriate.
23.178 Effects and Animation
The generation instructions encourage:
23.179 Default Color Direction
The current internal instructions tell the AI to use:
blue as the primary color
unless the user specifies otherwise.
If you want another palette, say so directly.
Example:
Use black, burgundy, and warm gold. Do not use blue as the primary interface color.
23.180 Specify Brand Colors Explicitly
For a branded Game, include:
This helps override generic visual defaults.
23.181 Game Preview Runs Generated Code
Remember that Game Developer is not displaying a static mockup.
The Preview runs the generated HTML/JavaScript in an iframe sandbox.
That is why you can interact with the generated Game.
23.182 Downloaded Code Runs Outside the PROS SUITE Preview Sandbox
The sandbox applies to the built-in Preview.
Once you Download the HTML and open or host it elsewhere, the file executes according to the environment in which you place it.
Review generated code before production deployment.
23.183 Inspect Third-Party References Before Publishing
Because AI-generated HTML can reference:
review those dependencies before commercial publication.
Confirm that they are:
23.184 No Public Hosting Workflow
The current Game Developer does not establish:
These functions should not be confused with Website Builder's publishing capabilities.
23.185 No App Store Publishing
Game Developer does not directly publish to:
The verified output is a browser Game HTML file.
23.186 No Native Mobile-App Package
The current export does not create:
files.
Mobile Friendly means the AI can be instructed to create touch-friendly browser controls—not a native mobile application package.
23.187 No Executable Desktop Export
The current Tool does not export:
23.188 No Multiplayer Backend Generator Is Established
Although the AI can generate browser code, the Game Developer source does not provide a specialized multiplayer server/deployment system.
Do not assume a Prompt requesting online multiplayer will automatically create and host the required production backend.
23.189 No Database Provisioning for Generated Games
The current Game Developer does not provide a subscriber UI for provisioning Game databases, user accounts, leaderboards, cloud saves, or authentication systems.
A generated frontend could simulate such interfaces, but hosted backend infrastructure is not established here.
23.190 No Asset Library Inside Game Maker
The current workspace does not contain a specialized Game asset manager for:
Use Prompt instructions and reference images where supported.
23.191 No Audio Upload
The reference attachment control accepts:
images.
It does not establish an audio-upload workflow for background Music or sound effects.
23.192 No Game Code Upload
There is no current user-facing control for uploading an existing:
for AI editing.
23.193 Token Catalogue Value
The PROS SUITE feature catalogue currently defines:
Game Maker — 100 Tokens.
23.194 Token-Cost Qualification
The Game Maker workspace itself does not display:
100 tokens per use
beside Build Game Now.
Its generation request goes to:
/api/ai/stream
using:
tool: "game-maker".
The actual server-side Token accounting is outside the sanitized user-operations bundle.
Therefore:
The 100-Token catalogue value is a source-verified feature default/reference, but this manual does not claim that every live Game generation is permanently fixed at exactly 100 Tokens.
Current system configuration can affect operational AI costs.
23.195 Token Balance Refresh After Successful Generation
When Game generation completes successfully, Game Maker calls the normal user-refresh workflow.
This allows updated account information to be reflected in PROS SUITE.
23.196 No Token Cost Display Inside Game Studio
Use the normal:
Monthly Tokens
account display to monitor your overall balance.
23.197 Copy, Save, Preview, and Download Are Not New AI Generations
The source does not start another AI-generation request when you:
Those are operations on an already generated result.
23.198 Regenerate Does Start Another AI Generation
Selecting:
Regenerate Game
calls the same AI generation workflow again.
It should therefore be treated as another AI-generation operation.
23.199 Best Practice — Define the Game Before Generating
Before selecting Build Game Now, decide:
A clear concept reduces unnecessary regeneration.
23.200 Best Practice — Put Critical Requirements in the Description
Because Theme and Control Type do not have visible selectors, include critical directions in the Description.
Example:
Fantasy forest theme. No sci-fi styling. Use mouse clicks and touch controls instead of keyboard-only controls.
23.201 Best Practice — Use Advanced Configuration Consistently
Make sure your selected:
match your written Description.
Conflicting instructions can reduce predictability.
23.202 Best Practice — Use Reference Images for Layout Direction
A reference image is especially useful when you care about:
The written Prompt should still explain what should be taken from the reference.
23.203 Best Practice — Do Not Expect Pixel-Perfect Reproduction
The reference image is sent as AI-generation context.
The source does not establish a deterministic pixel-perfect conversion engine.
Treat it as design guidance.
23.204 Best Practice — Turn On Mobile Friendly Before Generation
If mobile support matters, enable it before building rather than expecting desktop controls to become touch-enabled afterward.
23.205 Best Practice — Test Every Control
After Game generation, verify:
23.206 Best Practice — Test Win and Lose Conditions
Do not test only the first few seconds.
Confirm that the Game can actually:
as intended.
23.207 Best Practice — Test Difficulty
A Game labeled Easy or Medium may still be subjectively too difficult or too simple because Difficulty is AI-generated guidance.
Play it yourself and Regenerate if needed.
23.208 Best Practice — Test on Multiple Screen Sizes
For responsive or Mobile Friendly Games, test:
A Game looking correct in the PROS SUITE Preview does not guarantee identical behavior everywhere.
23.209 Best Practice — Save Good Versions Before Refining
If a Game is playable and useful:
Save it before Regenerating.
This gives you a persistent fallback if the next version is worse.
23.210 Best Practice — Download Important Final Versions
Saved Games provide account persistence, while Download HTML gives you an independent file copy.
For important projects, use both.
23.211 Best Practice — Rename Downloaded Files Externally
The automatic filename uses a timestamp.
After downloading, you can rename the file on your device to something easier to identify, such as:
aiunify-training-game-v1.html
or:
product-quiz-game-final.html
23.212 Best Practice — Version Your Games
A useful external naming structure is:
This prevents accidental replacement of a working Game.
23.213 Best Practice — Preserve the Original Prompt
Saved Games already preserve the Prompt.
If you Download the Game externally, also save the Prompt somewhere appropriate when reproducibility matters.
23.214 Best Practice — Verify External Dependencies
Before commercial deployment, inspect the generated source for third-party:
Single-file output can still rely on them.
23.215 Best Practice — Security-Test Before Hosting
Generated code is AI-created code.
Before placing it on an important business domain:
23.216 Best Practice — Avoid Entering Secrets in the Prompt
Do not place into Game generation instructions:
The Game should not need these for ordinary browser gameplay.
23.217 Best Practice — Do Not Hard-Code Production Secrets Into Generated HTML
A downloadable HTML file is client-side content.
Any secret placed in it can potentially become visible to users who inspect the file.
23.218 Best Practice — Use Game Developer for Appropriate Projects
Strong use cases include:
23.219 Best Practice — Treat Complex Games as Prototypes
For highly complex Games requiring:
Game Developer's single-page browser output is better treated as a prototype or starting point than a complete production Game platform.
23.220 Troubleshooting — Cannot Access Game Developer
Check:
23.221 Troubleshooting — Build Game Now Is Disabled
Enter a non-empty:
Description.
The generation button remains disabled while the Prompt is blank.
23.222 Troubleshooting — Prompt Required
If you receive:
Prompt Required
“Describe the game you want to create.”
enter a Description and try again.
23.223 Troubleshooting — Reference Image Is Rejected
Check that the image is no larger than:
5 MB.
23.224 Troubleshooting — Reference Image Does Not Reappear in Saved Game
Reference images are not part of the current Save Game payload.
Reattach the original image before Regenerating a saved Game.
23.225 Troubleshooting — Generation Appears Strange During Building Live
The AI may still be producing incomplete HTML.
Wait until:
Game Created!
before evaluating the final result.
23.226 Troubleshooting — Progress Is Moving Slowly
Progress is estimated from streamed output length.
A long or complex Game may produce substantial HTML and JavaScript before completion.
23.227 Troubleshooting — Progress Reached 90% and Paused
Streaming progress is capped around 90% until the output finishes.
The workflow then moves through Compiling at 95% and finally Done at 100%.
23.228 Troubleshooting — Generation Failed
Read the Error message accompanying:
Generation Failed.
Then:
23.229 Troubleshooting — Invalid HTML Error
If the AI did not return a valid HTML document, you may receive:
“AI did not generate valid HTML game code.”
Select Retry or simplify the Game instructions.
23.230 Troubleshooting — Stop Generation Removed the Live Preview
That is expected.
Stop Generation aborts the current request and returns the Stage to Idle.
The incomplete streamed Game is not promoted to a final playable output.
23.231 Troubleshooting — Game Does Not Respond to Keyboard
First:
If that fails, the generated Game code itself may have a control problem.
Add clearer controls to the Description and Regenerate.
23.232 Troubleshooting — Mobile Game Has No Touch Controls
Confirm that:
Mobile Friendly
was enabled before generation.
If it was, make the requirement explicit in the Prompt:
Include visible on-screen touch controls for movement and action.
Then Regenerate.
23.233 Troubleshooting — Game Is Sci-Fi When I Wanted Another Theme
The current internal Theme default is Sci-Fi and there is no visible Theme selector.
State the desired Theme explicitly.
Example:
Use a medieval forest fantasy setting. No sci-fi elements.
23.234 Troubleshooting — Game Uses Too Much Blue
The current generation instructions suggest blue as the default primary color unless the user specifies otherwise.
Specify your preferred palette explicitly and Regenerate.
23.235 Troubleshooting — Game Has External Fonts/Assets
This can be expected because the generation instructions explicitly permit/encourage external CDN resources.
Review the source if a fully offline Game is required.
23.236 Troubleshooting — Downloaded Game Looks Different Offline
The downloaded HTML may depend on online resources.
Reconnect to the internet or modify the Game externally to bundle required resources locally.
23.237 Troubleshooting — Save Game Does Nothing
Save Game requires completed:
generatedHtml.
If generation did not successfully reach Done, there is no completed Game to persist.
23.238 Troubleshooting — Save Failed
Current Error messages include:
Failed to save game.
or:
Error saving game.
Retry after confirming your session/connectivity.
23.239 Troubleshooting — My Saved Game Has a Strange Name
Game Developer does not currently provide a separate Game Name or Rename Game field.
When you select Save Game, the system automatically creates the saved Game Name from the beginning of your Game Description.
The current workflow uses approximately the first 30 characters of the Description and adds an ellipsis when the Description is longer.
For example, if your Description begins:
“Create a futuristic space shooter with three levels...”
the Saved Game may appear under a shortened Name based on those opening words.
Best Practice
Begin important Game Descriptions with a short, recognizable project Name.
For example:
“AIUNIFY Sales Challenge — Create an interactive...”
or:
“Cyber Racer — Build a futuristic racing game...”
This makes Saved Games easier to identify later.
The current interface does not provide a separate Rename control after saving.
23.240 Troubleshooting — Play Again Changed My Configuration
Selecting Play Again from Saved Games restores only certain parts of the original Game Project.
The current source verifies restoration of:
The current workflow does not restore all of the Advanced Configuration settings.
In particular, you should verify:
before selecting Regenerate Game.
Important
The saved Game itself still contains the Game behavior that was originally generated.
The limitation applies to the configuration controls used for a new Regeneration.
For example, a saved Game may already contain mobile controls, but after loading it through Play Again, the visible Mobile Friendly toggle may not represent the original setting.
Always review the current Configuration before Regenerating a Saved Game.
23.241 Troubleshooting — Play Again Opened Fullscreen
The current Play Again workflow attempts to place the loaded Saved Game into Fullscreen shortly after opening it.
This is intentional current behavior.
If Fullscreen opens and you prefer the normal Game Developer workspace:
Browser security rules may also prevent the automatic Fullscreen request from succeeding.
If Fullscreen does not open automatically, the Saved Game still loads normally.
You can use the Preview toolbar's Fullscreen control manually when needed.
23.242 Troubleshooting — Cannot Find Edit Code
The current Game Developer workspace does not provide a built-in source-code editor.
After Game generation, you can:
But you cannot directly open the HTML, CSS, and JavaScript in an editable coding panel inside Game Developer.
If You Need Manual Code Changes
Use:
Copy Code
or:
Download HTML
Then open the generated file in an appropriate external development environment.
Examples include:
After external editing, test the Game carefully before deployment.
The current Game Developer does not provide a verified Upload Modified Game workflow for bringing that edited HTML back into the Game Maker project.
23.243 Troubleshooting — Regenerate Changed the Game Completely
This can happen because Regenerate Game is not an incremental code-editing function.
When you select Regenerate, Game Developer starts a new AI-generation request using the current:
The previously generated Game code is not sent back to the AI as an existing Game that must be patched.
Therefore, Regeneration can substantially change:
Best Practice
If you want continuity, describe what should remain unchanged.
For example:
“Recreate the same cyberpunk racing concept. Keep the three-lane road, score system, player movement, neon city design, and Game Over screen. Only increase enemy speed and add two new power-ups.”
This gives the AI stronger continuity instructions.
Always preserve a good version before Regenerating.
23.244 Troubleshooting — Cannot Publish the Game
The current Game Developer does not provide a built-in:
Publish Game
workflow.
There is no source-verified control for automatically publishing a generated Game to a public AIUNIFY URL.
The current supported output workflow is:
Generate
→ Test
→ Save Game
→ Download HTML
If you want the Game publicly available, the downloaded HTML must be deployed through an appropriate website or hosting workflow outside the current Game Developer interface.
23.245 Troubleshooting — Cannot Get a Public Game Link
Game Developer does not currently generate a public hosted link for Saved Games.
Saving a Game adds it to your private Saved Games collection inside PROS SUITE.
It does not automatically create:
If public access is required, use Download HTML and deploy the file through the appropriate external website or hosting environment.
23.246 Troubleshooting — Cannot Export APK or iPhone App
Game Developer currently generates browser-based HTML Games.
It does not provide native application export formats such as:
The Mobile Friendly option means the AI can be instructed to create a browser Game with mobile-friendly layout and touch controls.
It does not convert the Game into a native Android or iOS application.
Native mobile packaging would require a separate development workflow outside the current Game Developer.
23.247 Troubleshooting — Saved Game Delete Was Accidental
The Delete Game confirmation explicitly warns that the action cannot be undone.
The current Game Developer does not establish:
Therefore, once a Saved Game is successfully deleted through the current interface, there is no verified subscriber-facing recovery option.
Best Practice
Before deleting an important Game:
23.248 Game Creation Checklist
Before selecting Build Game Now, confirm the following:
23.249 Generation Checklist
While the Game is being created:
23.250 Game Testing Checklist
After generation completes, test the Game thoroughly.
Start and Instructions
Controls
Game Mechanics
Game Completion
Display
23.251 Preservation Checklist
Before Regenerating, refreshing, or leaving Game Developer:
A strong operating habit is:
Generate → Test → Save → Download → Then Regenerate
23.252 Saved Games Checklist
Inside Saved Games, you should now be able to:
23.253 Export Checklist
Before distributing or hosting a downloaded Game:
23.254 What Game Developer Currently Supports
The current source verifies the following subscriber-facing capabilities.
Game Input
Game Configuration
AI Generation
Game Preview
Game Output
Game Persistence
23.255 What Game Developer Does Not Currently Establish
The current subscriber-facing source does not establish the following as active Game Developer features:
Project Management
Editing
Publishing
Export Formats
App/Store Distribution
Backend Infrastructure
Asset Management
Configuration
Guarantees
The current source also does not guarantee:
These capabilities should not be documented as active subscriber functions unless a later version of the source verifies them.
23.256 Important Current-Version Persistence Matrix
The following table shows which project elements are used during Game creation, which are currently saved, and which are restored through Play Again.
| Game Information | Used During Generation | Saved | Restored by Play Again |
| HTML Game Code | Yes | Yes | Yes |
| Description / Prompt | Yes | Yes | Yes |
| Genre | Yes | Yes | Yes |
| Visual Style | Yes | Yes | Yes |
| Difficulty | Yes | No | No |
| Mobile Friendly | Yes | No | No |
| Reference Image | Yes | No | No |
| Internal Theme | Yes | No | No |
| Internal Control Type | Yes | No | No |
Why This Matters
Suppose you created a Game using:
After saving and later selecting Play Again, the current system restores:
But it does not source-verify restoration of:
Therefore, review those settings before selecting Regenerate Game.
23.257 Game Developer at a Glance
The current subscriber workflow can be summarized as:
GAME DEVELOPER
↓
Workspace:
GAME MAKER
↓
Game Studio
Enter:
DESCRIPTION
↓
Optional:
ADD MOCKUP/REF IMAGE
↓
Optional:
TRY A DEMO PROMPT
↓
Configure:
GENRE
VISUAL STYLE
DIFFICULTY
MOBILE FRIENDLY
↓
BUILD GAME NOW
↓
Generation progresses through:
ANALYZING GAME CONCEPT...
↓
WRITING GAME CODE...
↓
Optional:
BUILDING LIVE
↓
COMPILING & OPTIMIZING...
↓
GAME CREATED!
↓
Preview
The generated Game becomes:
LIVE
↓
Play and Test
↓
Available actions:
SAVE GAME
COPY CODE
DOWNLOAD HTML
FULLSCREEN
↓
For another AI-generated version:
REGENERATE GAME
↓
Persistent projects appear under:
SAVED GAMES
↓
Saved Game actions include:
PLAY AGAIN
and:
DELETE
23.258 Chapter Summary
AIUNIFY PROS SUITE Game Developer is the Core Tool located at:
/game-maker
and presented inside the workspace as:
Game Maker.
Its purpose is to allow subscribers to describe a Game concept in natural language and have AI generate a playable browser Game as HTML.
The Game Studio provides a Description field for defining:
Subscribers can also attach a reference/mockup image of up to 5 MB to provide visual guidance to the AI.
Four current Demo Prompts are available for:
Advanced Configuration provides four visible subscriber controls:
The current defaults are:
The underlying Game configuration also contains internal defaults for:
but the current subscriber interface does not expose separate Theme or Control Type selectors.
Therefore, if you want a different Theme or control method, state it clearly in the Game Description.
For example:
“Create a medieval fantasy environment with no sci-fi elements. Use mouse and touch controls rather than keyboard-only controls.”
Selecting Build Game Now sends the Game Description, selected configuration, shared PROS SUITE AI Model, applicable provider API Keys, and optional reference image into the Game-generation workflow.
Generation proceeds through:
Analyzing game concept...
→ Writing game code...
→ Compiling & optimizing...
→ Game ready!
During generation, Game Developer can display the partially constructed Game through a:
Building Live
sandbox Preview.
Because that Preview is created from incomplete streaming HTML, temporary visual errors or incomplete functionality can appear while the Game is still being written. Evaluate the Game only after generation fully completes.
Subscribers can cancel an active generation using:
Stop Generation.
Stopping aborts the current request and returns the workflow to Idle. The partial streamed Game is not promoted into a completed Game that can be saved or downloaded.
When Game generation completes successfully, PROS SUITE validates the response as HTML and displays:
Game Created!
Your game is ready to play.
The completed Game can then be played directly within the Preview.
Available completed-Game actions include:
Copy Code copies the complete generated HTML source.
Download HTML creates a local browser Game file using a filename pattern similar to:
game-[timestamp].html
The generated Game can generally be opened in a compatible browser.
However, a single HTML file does not necessarily mean the Game is fully offline.
The AI-generation instructions currently permit external dependencies such as:
Therefore, downloaded Games should be tested both online and offline when offline operation is important.
Save Game creates a persistent Game Project inside PROS SUITE.
The saved project currently preserves:
The displayed Saved Game Name is automatically derived from approximately the first 30 characters of the Prompt.
Saved Games appear in the:
Saved Games
collection.
Each Game provides:
Play Again
and:
Delete.
Selecting Play Again restores the saved Game HTML, Prompt, Genre, and Visual Style and loads the Game back into the active Preview.
However, the current Save workflow does not preserve or restore:
These settings should therefore be reviewed before Regenerating a Saved Game.
Another major current-version distinction is:
Regenerate Game is a new full AI generation.
It is not an incremental AI edit of the existing HTML.
Game Developer clears the current generated Game and creates another complete Game from the current Description and Configuration.
For that reason, preserve valuable versions before Regeneration using:
Save Game
and/or:
Download HTML.
The feature catalogue currently identifies Game Maker with a 100-Token reference/default value. However, the Game Maker workspace itself does not display a fixed per-generation cost, and final server-side Token accounting is outside the User Operations source bundle.
Therefore, this manual should not state that every Game generation will permanently cost exactly 100 Tokens.
The recommended Game Developer operating method is:
Define the Game Clearly
→ Select Genre, Style, Difficulty, and Mobile Support
→ Add a Reference Image When Helpful
→ Choose the Appropriate AI Model
→ Build Game Now
→ Watch the Live Development
→ Wait for Game Created!
→ Test the Complete Game Thoroughly
→ Save a Good Version
→ Download an External Copy
→ Refine the Description
→ Preserve the Existing Version
→ Regenerate
→ Test the New Version
→ Deploy Externally Only After Verification