Making a game in a browser with aukimi Engine
Build a small playable course in aukimi Engine, add movement and a goal, test it with a player, then export a web build from the browser.

On this page
Making a game in a browser starts with a small interaction that someone can play. In aukimi Engine, you can arrange a scene, add behaviour, run it and build a web version from the same workspace. For a first project, make a short obstacle course. The player moves through one room, avoids a hazard and reaches a clearly marked finish. Give yourself a complete loop to test before adding more rooms.
Create a project and open Engine
Open the aukimi dashboard and choose New project. Give it a recognisable name, then select Engine in the module rail. A project holds the state of multiple studios, so you can prepare artwork or sound elsewhere in the suite as the game grows. The dashboard also lets you start directly in one module, which creates a single-studio document. The getting started guide explains both routes.
Look at the scene graph, central viewport, right-hand inspector and bottom console. The toolbar includes viewport modes, playback controls and Build. A new scene starts with a Main Camera, Directional Light, Skybox and Ground Plane. Save a copy before changing the scene so you have a point to return to.
Block out one readable room
Use Add Entity to create a few cubes for walls and obstacles. In the inspector, adjust their position and scale. Keep the route short and wide enough to understand from the camera. Use simple colours for the start, danger and finish areas. At this stage, large readable shapes make it easier to spot a problem with the layout.
Engine includes character presets such as Top-Down, First-Person and Platformer. Choose a preset that fits the room and check its controls during play. Preconfigured props include a healing pickup and a damaging hazard. Begin with one hazard so you can verify what happens when the player touches it. The Engine reference describes these entities and components.
Add movement, a goal and a restart
Give the player three things to understand. They need to know how to move, where to go and how to try again. First, test movement and camera framing in the empty room. Then place the hazard where players can see it before contact. Add a visible finish area at the other end.
For custom behaviour, select an entity and use Add Script in the inspector, or open the script editor with F2. Templates include movement and trigger zones. You can also work with Blueprint behaviours. Use a trigger for the finish condition, then display a success message and provide a restart action. Test those changes separately so you can trace an error to the step that introduced it.
Playtest the loop before adding artwork
Use Play, Pause and Stop to inspect the game. Engine reports changes made during a play session when you stop. Read that message before continuing the edit. Use the console to find script errors and identify the entity involved.
Ask someone to try the course without instructions. Watch whether they recognise the player, find the finish and understand the hazard. If the camera hides the next turn, fix the framing. If they reach the end without noticing, improve the finish feedback. After the loop works, bring in artwork from Pixel or other studios, and add sound in the places where feedback helps.
Build and check a shareable web version
Open Build, check the game type and choose Web. The web target offers options including embedded assets, minification and an FPS counter. Export the build and test it through a web server or hosting service. Use a fresh browser session to verify loading, controls, audio activation and the finish-to-restart loop. The build documentation covers the target options.
Desktop and mobile targets use a generated Bevy project, so check the exported result for the features your game uses. Keep the editable project and a backup with the release. Browser graphics support also varies by device. Our WebGPU explainer helps you assess those differences, and the indie game development tools guide covers the rest of a small production setup.

