Log inGet started
← Explore
World media

Press Start Studio: Title, Pause, Settings and Credits Menus

Every menu your game needs, ready to drop in: title, per-player pause, settings, game over, victory, loading and scrolling credits, in 8 looks (sci-fi, fantasy parchment, cartoon, pixel retro, minimal, military, horror, cozy) and 4 layouts (centred list, side rail, card carousel, radial), switched with one call. Works with keyboard, gamepad and touch, in English, Português (BR) and Español, and is built for multiplayer worlds. Open the gallery here to browse every look, layout and screen, or walk around and pause for real. To use it, install the menusKit package (61aaf7c0-6b6e-4451-9141-a5ef7a087272) from ZeroMind in one step; it brings controlsKit along for button prompts and rebinding, and two guides inside it show how to add a main menu, pause menu and settings screen to your game.

0score
Embed

Embed this world

Paste this code into your own page and the world plays right there.

Updated Nov 16, 2026
menusuiui-kittitle-screenpause-menusettingslocalizationgamepadtouchmultiplayerpackageshowcase

menusKit 1.3.19

Every menu a game needs, as one styled screen stack: title, pause, settings, game over, victory, loading and credits. One call puts a finished screen up, and your game listens for what the player picked.

  • 8 looks: sci-fi, fantasy parchment, cartoon, pixel retro, minimal, military, horror, cozy.
  • 4 layouts: centred list, side rail, card carousel, radial. One setTheme or setLayout call restyles every screen at once.
  • Built for multiplayer: pause is per player (the world and everyone else carry on), and settings are saved per player.
  • Keyboard, gamepad and touch, down to phone-sized screens, with an on-screen pause button.
  • English, Português (BR) and Español.
  • Two guides inside the package, so they arrive with every install.
  • 121 automated tests, all passing.

Install

Install the menusKit package from ZeroMind (guid 61aaf7c0-6b6e-4451-9141-a5ef7a087272). It brings controlsKit 1.3.2 (Thumbstick Studio) with it in the same step, for button prompts, input reading and rebinding. Then paste the first example from the README at the end of your main scene's entrypoint. It runs as written, in edit and in play, with the strict checker on.

Guides

Two guides ship inside the package. Once it is installed, open them from menusKit.package/guides/ in the Docs panel or with the engine's guides tool:

  • Main menu, pause menu and settings screen for my game: how the kit fits together (the screen stack, per player pause, saved settings, rebinding, switching looks and layouts, translating the screens), what to do first and where to read on.
  • How to add a pause menu to my game: a worked example, Coin Dash, from an empty world to a playable game with a title screen, pause menu, settings and game over with Retry, installing menusKit and controlsKit from ZeroMind. Every step was followed in a brand new world.

Try it here

Open the gallery to browse every look × layout × screen, or walk around the main scene and pause for real.

New in 1.3.4

  • The select event is documented as it really fires: last, after the choice's own event and after any screen change the choice causes (Settings fires show, settings, select; Main Menu fires mainMenu, show, select). The behaviour is unchanged, and a new test pins the order.
  • No long dashes left in the kit, the gallery or the scenes.

New in 1.3.3

  • Docs only. The README no longer warns that the builtin touch controls come back over controlsKit's on a second editor Play: controlsKit 1.1.0, which a menusKit install brings, keeps its takeover (checked over three rounds in a fresh world). The code is the same as 1.3.2.

New in 1.3.2

  • Two guides in the package: a how-to-use guide and a worked example (see Guides).
  • Checked on today's engine, nothing broken. In a fresh world, the README's first example ran as pasted. Pause stopped only the player who pressed it, one setTheme restyled every screen, touch and gamepad both drove the menus, and the tests passed twice in a row. Every check ran against controlsKit 1.1.0.
  • Known limits now name only problems that are still open.

New in 1.3.1

  • The first README example works when pasted, and handlers added in onLoad no longer pile up between play runs.

Known limits

  • Phones were checked in the editor only (#19210). Safe areas were measured with simulated insets, not on a real phone. While playing inside the editor with phone insets, a menu element under them can show clipped; that is the engine's editor play view, not the kit's layout.
  • Short screens: on very short screens a few layouts (list victory at about 540 pt, carousel and side rail at about 360 pt) run a little past the bottom of the safe area. The radial layout fits everywhere. Details in the README.
  • Carousel taps mid-slide land on the card coming to rest under the finger.
  • Per-player pause was checked in one engine (#14448): two engines on one account collide as one player, so a check with two real players on two accounts has not been run.
  • The web build was not run for this release (#20946).
  • A fresh install takes about 20 seconds (#21420), since it brings controlsKit and copies of a few engine files.
  • The guides don't show in ZeroMind library search yet (ZeroMind#3099); they are in the package and the engine finds them once it is installed.
  • ZeroMind's description can lag a release (#19258).
  • Rebinding needs a controlsKit scheme; a guest with no player identity keeps settings for the session only.

MIT licensed.

Comments · 0

Open discussion, no rating attached. Ask questions, swap notes, follow threads.

Sign in to join the discussion.

Documented parts · 8