Getting started

About 20 minutesUnity 2022.3 LTS or 6Windows 10 or 11

Mulno records a playtest of your Unity game (picture, sound, the tester's mic and webcam, and the moments your game marks) on one timeline, and keeps it in your own storage or in Mulno Cloud. This page is the map: what works today, then the shortest path from a download to your first session in Studio.

Mulno is in beta

The web app is at app.mulno.com: accounts, workspaces, builds and branches, campaigns, plans, and review in the browser. New accounts come from the beta waitlist: how to join. The shipped Studio keeps the platform's screens in the web app for now; it signs in only to get its updates. Studio and the Unity package download from the web app once you are signed in (the Download page has the button; the Launcher is public), and what is marked Soon below is not open yet.

1. What works today

PartStatusRead
Record a playtest to a folder on your PCWorks todayRecord your first playtest
Review in Studio: player, timeline, notes, drawings, transcripts, bug reports, live reviewWorks todayReview a session
Remote playtests: a campaign, invite codes, uploads into Mulno Cloud or your own R2 bucketWorks today, in the betaSend a build to testers
Ask Claude about your sessions on your own PC, and let it pin notes backWorks todayConnect Claude over MCP, Apply notes
Copy a moment for Jira, Trello or MarkdownWorks today, as mulno:// links that open in StudioMoment links and trackers
Push a build to a branch, and testers get it through the LauncherWorks today, at app.mulno.comPush a build, The Launcher
Review in the browser and https moment linksWorks today, at app.mulno.comReview in the browser
Remote MCP: Claude reads your Mulno Cloud sessions at mcp.mulno.comWorks today, for ClaudeConnect Claude over MCP
Accounts, workspaces, plans and billingWorks today, at app.mulno.comPlans and quotas
Mulno Cloud storage: builds and testers' sessionsWorks today, counted against your plan's storageYour own bucket and the lent key
Reviewing a Private-bucket project in the browser, the lent key, handing a tester the web zipSoonYour own bucket and the lent key, The web zip

2. The shortest path

  1. Get the files. Studio (Mulno Studio_0.4.2_x64-setup.exe), the Unity package (com.mulno.playtest-0.4.1.tgz) download from the web app once you are signed in: use Sign in to download on the Download page. SHA256SUMS.txt is public there. Compare the hash before you run anything (how).
  2. Install Studio. Windows shows a SmartScreen warning because Mulno doesn't sign its installer yet: choose More info, then Run anyway. It installs for your Windows user with no admin rights and registers the mulno:// link scheme. Details: Install and configure.
  3. Add the package to your game. Window › Package Manager › + › Add package from tarball…, then pick the .tgz. The capture DLL and the uploader come inside it. Replace the whole package on every release: the DLL, the uploader and the C# are one unit.
  4. Record yourself. Tools › Mulno Playtest › Build Playtest Player (Windows x64), run the player, accept the consent screen, play for a minute, press F6 once. Recording exists only in that build; your normal builds carry none of it.
  5. Open it in Studio. On its first run Studio asks Where do your playtests record? Choose Local or network folder and point it at the folder the session was written to. Nothing is copied or moved.

The same steps with the code are in Record your first playtest, and a minimal script is on Samples.

3. Local mode and remote mode

Local is what you just did: the PlaytestConfig has no Broker Url, so a session is written to a local folder and never leaves your PC. Use it for in-person tests and for trying Mulno out.

Remote is a config with a Broker Url and a Campaign Id baked into the build. A tester types an invite code, agrees to what gets recorded, and the session uploads from their PC to wherever the project keeps sessions: Mulno Cloud, our storage and a new project's default, or your own bucket, where Mulno's servers never see the footage. You set up the storage, the branch, the campaign and the codes in the web app, or, with a bucket of your own and no workspace, in Studio's Campaigns screen (Send a build to testers). Testers never count as seats and need no account.

4. Who can have an account

Sign in on this site goes to app.mulno.com. The beta admits studios from a waitlist: Join the waitlist opens the waitlist form, you confirm your address from the email we send, and we let you in from the list; after that you sign in at app.mulno.com. A new account is created only for an address we have let in, or one invited into a workspace. For now Mulno opens new accounts only to studios in Thailand; elsewhere the site says it's coming soon and you can write to us. It won't create an account for a request from the EEA or the UK until it has named its legal representatives there. Existing accounts and testers aren't affected: an existing account signs in from any country, a tester in any country can play your build, and you stay the controller of what they record. More in Privacy for studios and testers.

5. Where next