May 18, 2026

Highrise Studio is a Unity-based development environment that lets you build 3D worlds and games for the Highrise platform. The process follows five phases: install Studio Hub, create a project from a template, build and customize your scene, upload to Highrise servers, then release through the Creator Portal. Once published, you can earn real income through engagement-based payouts and in-world purchases. This guide walks through every step and defines every term you’ll encounter along the way.
If you’ve spent any time in Highrise and thought “I could build something better,” this is your starting point. Learning how to create and publish a world on Highrise Studio can feel overwhelming at first, mostly because the vocabulary is unfamiliar and the official documentation is scattered across multiple pages.
This guide solves that problem. It maps the entire workflow from installation to your first published world, defines every key term in the order you’ll actually encounter it, and addresses the real issues creators run into. Whether you’ve never opened Unity before or you’re stuck on an upload error at 2 AM, everything is here in one place.
Before building, it’s worth exploring what other creators have already published. Browse existing worlds on Highrise to get a feel for what’s possible, from casual social hangouts to fully scripted games.
Per GamesBeat reporting, Highrise has over 50 million users and 10,000 creators building worlds on the platform. The opportunity is real. One creator reportedly earned approximately $300,000 from a poker-based speakeasy world, according to Fast Company.
Every world you create and publish on Highrise Studio follows the same five phases. Here’s the map, with the key terms you’ll need at each stage.
Phase 1: Install and Set Up
Key terms: Studio Hub, Studio Package, Studio Tools, Unity 6
Phase 2: Create a Project
Key terms: Project Template, Scene
Phase 3: Build and Customize
Key terms: GameObject, Prefab, Component, NavMesh, Spawn Point, Anchor Point, Lua Scripting, Highrise Assets Catalog
Phase 4: Upload
Key terms: Project Validator, Upload
Phase 5: Publish and Release
Key terms: Creator Portal, Release/Publish, Version Number
After Publishing
Key terms: Engagement-Based Payouts, In-World Purchases, Earned Gold, Creator Exchange, Profit Sharing
Keep this map handy. Every glossary entry below tells you which phase it belongs to, so you always know where you are in the process.
The first step in creating and publishing a world on Highrise Studio is getting the tools installed. This is simpler than it sounds, but there’s one critical detail that trips up many beginners.
Definition: Your central control panel for Highrise Studio. It provides access to different versions of the Studio and Unity Editor, along with project templates and samples.
Where it fits: Phase 1 (Install and Set Up).
After downloading Highrise Studio, Studio Hub is the first thing you’ll interact with. It handles installing Unity Hub and the correct Unity Editor version automatically. Think of it as the launcher that manages all your world projects in one place.
Common mistake: Skipping the Unity update prompt. Studio Hub will ask you to install a specific version of Unity. Don’t skip this.
Definition: Highrise Studio requires Unity 6 (version 6000.0.XXXX) to function correctly.
Where it fits: Phase 1 (Install and Set Up).
This is the single most important technical detail in the entire setup process. According to official Highrise news, using the wrong Unity version can lead to build failures, publishing errors, and issues when opening or updating older worlds. Practitioners on the Highrise Create Forum frequently report upload problems that trace back to a Unity version mismatch.
Pro tip: If Studio Hub prompts you to update Unity, do it immediately. Older projects may need migration to Unity 6 before they’ll build properly.
Definition: The core of Highrise Studio. It bundles the essential assets, tools, and plugins needed to create and share worlds on Highrise.
Where it fits: Phase 1 (Install and Set Up).
The Studio Package is what turns a standard Unity project into a Highrise-compatible one. It includes the components, scripts, and editor extensions specific to the platform.
Definition: A VSCode extension that simplifies coding for Highrise Studio, offering features like Lua code highlighting and word suggestions.
Where it fits: Phase 1 (Install and Set Up), though you’ll use it throughout Phase 3.
If you plan to add any interactivity to your world (and you should), install this extension. Writing Lua without syntax highlighting is needlessly painful.
With everything installed, it’s time to start a new world project.
That’s it. The template gives you a starting scene with the Highrise-specific components already configured.
Definition: A separate environment where game elements exist and interact. Each scene is essentially one room or level of your world.
Where it fits: Phase 2 (Create a Project) and Phase 3 (Build and Customize).
You create new scenes through File > New Scene in Unity. Most simple worlds use a single scene, but complex games might use multiple scenes for different areas or game modes.
Pro tip: Save your scene immediately after creating it. Unity doesn’t auto-save, and losing work to a crash is a rite of passage nobody enjoys.
This is where you spend most of your time. Building a world means adding objects, setting up navigation, and scripting interactivity. Here are the terms and steps that matter.
Definition: The fundamental building block of any Unity scene. Every object in your world, from a chair to a light source to an invisible trigger zone, is a GameObject.
Where it fits: Phase 3 (Build and Customize).
Use the GameObject menu in Unity to add basic shapes (cubes, spheres, cylinders), lights, cameras, and empty containers. You build your world by combining these elements and adding components to them.
Definition: A piece of functionality you attach to a GameObject. Examples include Rigidbody (for physics interactions) and Collider (for collision detection).
Where it fits: Phase 3 (Build and Customize).
Select any object in the scene, then look at the Inspector panel on the right side of Unity. That panel shows every component attached to that object. You can adjust properties like position, rotation, scale, and material from here.
Common mistake: Adding a Rigidbody without a Collider (or vice versa). Physics-based objects generally need both to behave correctly.
Definition: A reusable, pre-configured GameObject that saves development time and ensures consistency across your world.
Where it fits: Phase 3 (Build and Customize).
If you build a decorative lamp with specific materials and lighting settings, save it as a Prefab. Then you can drag copies into your scene without rebuilding from scratch each time. Change the Prefab, and every instance updates.
Definition: A system that outlines walkable areas in your scene, enabling characters to navigate intelligently around obstacles.
Where it fits: Phase 3 (Build and Customize).
NavMesh is generated by the “Nav Mesh Surface” component. It tells the game engine where players and NPCs can walk. Without a properly baked NavMesh, characters will either stand still or walk through walls.
Common issue: Practitioners on the Highrise Create Forum report frequent NavMesh errors, particularly the “failed to create agent because there is no valid NavMesh” message. This usually means the NavMesh wasn’t rebaked after making changes to the scene geometry. One new Unity creator described their NavMesh working initially, then breaking after scene modifications. Rebake after every significant terrain change.
Definition: A designated spot where players appear when they first enter your world or respawn after certain events.
Where it fits: Phase 3 (Build and Customize).
Place spawn points carefully. They should be on the NavMesh so that players can immediately move after spawning. Spawn points floating above unnavigable terrain will confuse players and break the experience.
Pro tip: Place multiple spawn points to prevent players from stacking on top of each other in busy worlds.
Definition: A specific location on an object where characters can attach for interactions, like sitting on a chair or standing at a counter.
Where it fits: Phase 3 (Build and Customize).
Anchor points make your world feel interactive and alive. Without them, players just stand around. With them, they sit on couches, lean against walls, and interact with furniture naturally.
Definition: The programming language used to control game object behavior, mechanics, and interactivity in Highrise worlds.
Where it fits: Phase 3 (Build and Customize).
Lua is a lightweight scripting language. It handles everything from door open/close mechanics to complex game systems like scoring, timers, and player interactions. The Studio Tools VSCode extension makes writing Lua significantly easier with code highlighting and suggestions.
You don’t need to be an expert programmer to start. Simple scripts for basic interactions are straightforward, and the Highrise creator community shares examples and troubleshooting help regularly.
Definition: A library of 3D models, images, and audio files available within Highrise Studio for use in your worlds.
Where it fits: Phase 3 (Build and Customize).
You can source assets from two primary places: the Highrise Assets Catalog (built into Studio) and the Unity Asset Store (through Unity itself). The Highrise catalog includes items designed specifically for the platform, which can save time on compatibility issues.
Highrise Studio supports multiple camera perspectives including first-person, third-person, and RTS (real-time strategy) views. The camera setup you choose shapes how players experience your world. A social hangout might use third-person for avatar visibility, while an exploration game might benefit from first-person immersion.
You’ve built something worth sharing. Now it’s time to get it onto Highrise servers.
Definition: A pre-upload tool that scans your build for errors and compatibility issues before sending it to Highrise servers.
Where it fits: Phase 4 (Upload).
The Project Validator catches problems before they become upload failures. Pay attention to its warnings. Fixing errors at this stage is far easier than troubleshooting a broken upload.
Upload sends your build files to Highrise servers. Publish (Release) makes the world live and accessible to players.
These are two separate steps. You cannot publish a world with no build uploaded. Many first-time creators complete the upload, then wonder why their world isn’t visible. The answer: you still need to release it through the Creator Portal.
This distinction is the single most common source of confusion for new creators. The terms sound interchangeable, but they aren’t.
The final steps to create and publish a world on Highrise Studio happen in the Creator Portal, not in Unity.
Definition: The web dashboard where you manage your published worlds, including settings, analytics, builds, and monetization.
Where it fits: Phase 5 (Publish/Release) and ongoing management.
After uploading, go to the Creator Portal and locate your world. Here you’ll customize the details that players see: description, thumbnail image, category, and tags. These matter for discoverability. A world with no thumbnail and a generic description won’t attract players.
Definition: A numerical label (like 1.0.0) assigned during the release step to track different builds of your world.
Where it fits: Phase 5 (Publish/Release).
Use version numbers consistently. A common convention: increment the last digit for small fixes (1.0.1), the middle digit for new features (1.1.0), and the first digit for major overhauls (2.0.0).
After releasing, open the Highrise app and access your world through the Worlds tab. Test everything from a player’s perspective. Walk around. Test spawn points. Try every interaction. What works in the Unity Editor sometimes behaves differently on mobile devices.
This step is not optional. Check the latest platform news and updates for any known issues that might affect your world’s behavior.
No guide on how to create and publish a world on Highrise Studio would be complete without addressing the problems that actually stop creators in their tracks. These issues come directly from community forums where creators share real frustrations.
One creator on the Highrise Create Forum reported trying to update their world for days, unable to get past asset validation even after recreating the entire project and reinstalling Unity and Hub. This is a recurring issue.
What to try:
Another creator posted about attempting to upload for over an hour with no success despite making no major changes. Sometimes this is a server-side issue.
What to try:
A creator reported being unable to upload their 3D world due to a persistent font error on macOS, with no help available online at the time.
What to try:
The “failed to create agent because there is no valid NavMesh” error appears when the navigation mesh doesn’t cover the area where agents are trying to spawn or move.
What to try:
The official Highrise news channel acknowledges that worlds can load slowly, heat devices, or drop FPS. Mobile devices have limited processing power compared to your development machine.
What to try:
Publishing isn’t the finish line. It’s the starting point for monetization. Highrise offers multiple ways for creators to earn income from their worlds.
Definition: You earn Gold daily when Highrise+ subscribers (other than yourself) spend time in your world.
Requirements: Your world must maintain a rating of 50% or higher and engage at least one Highrise+ subscriber per day (other than yourself).
The top-performing world on the weekly leaderboard (“Society Lounge”) accumulated 109,607 minutes of player time in a single week. That kind of engagement translates to significant daily payouts.
Definition: A system that lets you sell items, access, or features inside your world using the Payments API. Players pay with Gold, and you earn 90% of the amount as Earned Gold. The remaining 10% covers platform and app store fees.
IWP is where creative monetization happens. Sell cosmetic items, premium areas, power-ups, or special abilities. The Payments API handles the transaction so you can focus on building the experience.
Definition: Earned Gold is Gold you’ve accumulated from engagement payouts and in-world purchases. From Gold payments, creators earn 70% of the Gold collected, deposited as Earned Gold.
Once you’ve accumulated at least 35,000 Earned Gold, you become eligible to cash out through the Creator Exchange Dashboard. Until then, Earned Gold works just like regular Gold within Highrise.
You can also explore the Highrise shop to understand the Gold economy from a player perspective, which helps inform your pricing decisions for in-world purchases.
Definition: A Creator Portal feature that allows you to split profits with collaborators based on percentages you define.
If you build a world with a team (one person handles scripting, another does 3D modeling), Profit Sharing lets you divide earnings fairly without managing external payments.
Your world has its own wallet that holds Gold earned through the Payments API and other mechanisms. The Wallet API lets you programmatically award Gold to players for in-game achievements, creating prize pools, or incentivizing specific behaviors.
Once you’ve successfully created and published a world on Highrise Studio, the learning curve flattens quickly. Your second world will take half the time. Here are ways to keep growing:
Submit design ideas. The Highrise Concepts program lets you submit designs that could be featured on the platform, opening another creative avenue.
Participate in Game Jams. Highrise runs periodic game jams where creators build worlds around specific themes. These events drive visibility and can push your world up the leaderboards.
Study what works. Explore published worlds and pay attention to what keeps you engaged. The worlds that earn the most Gold tend to have clear gameplay loops, social interaction opportunities, and polished visuals.
Stay current. Check the Highrise blog for creator spotlights, feature announcements, and platform updates that could affect your development workflow.
Highrise Studio is available on PC and Mac through Steam as well, giving you flexibility in where and how you develop.
Not for a basic world. The templates and visual tools in Unity let you build functional social spaces without writing a single line of code. But adding Lua scripting opens up interactivity, game mechanics, and monetization through the Payments API. Most successful creators learn at least basic Lua over time.
Uploading sends your build files to Highrise servers. Publishing (called “Release” in the Creator Portal) makes the world live and accessible to players. You must upload before you can publish, and completing one does not automatically trigger the other.
The most common causes are using the wrong Unity version (you need Unity 6), unresolved Project Validator errors, corrupted asset files, or unstable internet connections. Forum creators report that asset validation errors are the most persistent issue, sometimes requiring a fresh project rebuild.
Through two main channels: engagement-based payouts (you earn Gold when Highrise+ subscribers spend time in your world) and in-world purchases via the Payments API (where you keep 90% of each transaction). You need a minimum of 35,000 Earned Gold to cash out through the Creator Exchange.
Yes. Your world must maintain a rating of 50% or higher, and at least one Highrise+ subscriber (other than yourself) must spend time in it each day for you to receive engagement-based payouts.
Yes. The Profit Sharing feature in the Creator Portal lets you split earnings with team members based on percentages you assign. This is useful for collaborative projects involving designers, scripters, and artists.
You can use assets from two sources: the Highrise Assets Catalog (built into Studio) and the Unity Asset Store. The Highrise catalog contains assets designed for platform compatibility, while the Unity Asset Store offers a broader selection. Always check licensing terms for third-party assets.
For a simple world using a template, a focused creator can go from installation to published in a single afternoon. More complex worlds with custom scripting, original 3D models, and game mechanics take days to weeks. The learning curve is steepest during your first project.
© 2026 Pocket Worlds. All rights reserved.
Company