DEV Community: A Plus Games Studio

AI Agents in Game Engines: Unity AI, MCP and Unreal

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

AI agents can now work inside game editors, not just answer questions about them. Unity AI, in open beta for Unity 6, includes an in-editor agent and an MCP server that lets external AI tools automate editor tasks. Epic has announced MCP integrations as part of Unreal Engine 6. They are genuinely useful for repetitive work, but every change still needs review, version control and a person who owns the result.

What MCP is

The Model Context Protocol is an open standard for connecting AI assistants to tools and data. In a game engine, an MCP server exposes actions such as creating objects, editing components, running tests or reading project structure. An AI assistant that supports MCP can then call those actions instead of only suggesting code for you to paste.

What is available now

Tool	What it offers
Unity AI (open beta, Unity 6)	Ask, Agent and Plan modes in the editor, an MCP server for editor automation and an AI Gateway for third-party models
Unreal Engine 6 (announced)	Epic lists MCP integrations for AI assistants among its pipeline plans
Community MCP bridges	Open-source servers for various engines; quality and maintenance vary

Where agents genuinely help

Repetitive editor work : setting up many similar objects, renaming, organising folders.
Boilerplate code : data classes, editor tools, simple state machines.
Test scaffolding : generating test cases for systems with clear rules.
Explaining unfamiliar code in an inherited project.
Documentation : summarising systems and writing setup notes.

Where they still struggle

Game feel and design judgement. Whether a jump feels good is a human call made through playtesting.
Performance. Agents can introduce costly patterns that only show up on low-end devices.
Large, interconnected changes where a small mistake breaks other systems.
Platform rules such as store policies and certification requirements.

How to use agents safely

Commit your work before every agent session, and use a branch.
Start with read-only or narrow tasks, then widen permissions as you build trust.
Review every diff, including scene and prefab changes, not only code.
Run the game and tests after changes; do not rely on the agent's summary.
Keep secrets, keys and personal data out of prompts and project files the agent can read.
Check the data and licence terms of any model you connect.

A sensible team workflow

Plan : describe the task, the files involved and what must not change.
Run : let the agent work on a branch with limited permissions.
Review : read the diff, including scenes, prefabs and project settings.
Test : play the affected parts of the game and run automated tests.
Merge : only after a person signs off, as with any other change.

Treat the agent like a fast junior teammate: helpful, but not trusted to merge its own work.

Teams that get the most from agents also write short project notes the agent can read, such as naming rules, folder structure and coding conventions. Clear conventions produce more consistent results and fewer surprises in review.

Data, security and licensing

When an assistant reads your project, project data may be sent to the model provider. Check where data goes, whether it is used for training, and how long it is kept. Keep API keys, credentials and personal data out of files the agent can access. For generated code and assets, check the licence terms of the tools you use and keep a record of what was generated, especially for content that will ship in the game.

Questions to ask a studio that uses AI

Which tools do you use, and what project data do they send outside your company?
Who reviews AI-generated code and assets?
How do you handle licensing of generated content?
Will you disclose AI use where a platform requires it?

At A Plus Games Studio we use AI tools where they save time on routine work, and every change goes through the same review and testing as human work. Clients own their source code either way.

What it means for budgets

Agents reduce the cost of routine tasks, which can shorten some parts of a schedule. The biggest costs in game development, such as design iteration, art direction, performance work, testing and live operations, are still driven by people. Expect modest savings and faster iteration rather than a dramatic drop in total cost. Our is AI replacing game developers? guide covers this in more depth.

Getting started

Pick one repetitive task your team dislikes, such as setting up level props or writing editor tools, and try an agent on a branch for a week. Measure time saved and problems introduced. That small trial will tell you more than any announcement. For engine news, see Unreal Engine 6 and Unity Spark.

Sources: Unity Discussions: Unity AI open beta for Unity 6 · Unity Learn: build with Unity AI · Unreal Engine: State of Unreal 2026 · Model Context Protocol. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

COPPA Rule Update 2026: What Kids Game Developers Must Do

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

The FTC's amended COPPA Rule had a compliance date of April 22, 2026. Games directed at children under 13, or that knowingly collect their data, now need separate parental consent before sharing children's data with third parties for purposes such as targeted advertising, more detailed notices naming who receives data, and written security and data retention policies. If you have not reviewed your SDKs and ad setup since then, do it now. This is not legal advice.

Who COPPA applies to

COPPA applies to websites, apps and online services directed at children under 13, and to general-audience services that have actual knowledge they collect personal information from children under 13. Many casual, educational and family games fall into the first group, and games with large young audiences can fall into the second.

What changed

Area	New requirement
Third-party sharing	Separate verifiable parental consent before disclosing children's data to third parties for non-integral purposes, such as targeted advertising
Notices	Direct notices and privacy policies must identify third parties or categories receiving data, and why
Security	A written information security program appropriate to the data
Retention	A written data retention policy; keep data only as long as necessary, then delete it
Personal information	Expanded definition, including biometric identifiers
Consent methods	New options such as text plus, where data is not disclosed to third parties

Key dates

April 22, 2025: amendments published in the Federal Register.
June 2025: amendments took effect.
April 22, 2026: compliance deadline for most requirements.
February 2026: FTC policy statement on limited enforcement where data is collected only for age verification.

What it means for monetisation

Targeted advertising to children generally requires separate parental consent under the new rule, which most games will not obtain. In practice, games directed at children usually rely on contextual advertising, which uses the content being viewed rather than the child's data, along with ad networks configured for child-directed traffic, or move away from ads toward premium or parent-approved purchases.

Auditing your SDKs

Most COPPA problems in games come from third-party code. Analytics, ads, attribution, crash reporting and social SDKs can all collect identifiers.

List every SDK in the game and what data each collects.
Mark which are integral to running the game and which are not.
Configure child-directed settings in every SDK that supports them.
Remove SDKs that cannot be configured safely.
Update notices to name the third parties or categories and purposes.

Security and retention

Write down how you protect children's data: who can access it, how it is stored, how incidents are handled. Write a retention policy: what you keep, for how long and why, and how it is deleted. Then follow both. Small studios can keep these short, but they must exist and match what you actually do.

Parental consent flows

If your game needs consent, design the flow for parents, not children: clear language, a simple way to approve or decline, and a working game experience if consent is not given. Test it end to end. Platform tools help, including app store parental controls and the new age APIs described in app store age verification laws.

Mixed-audience games

Many games appeal to children and adults. If your game is directed at a mixed audience, you may be able to age-screen players and apply COPPA protections only to those under 13, but the screen must be neutral and must not encourage children to lie. Child players then get the protected experience: no targeted ads, limited data collection and parental consent where needed. Get legal advice on whether your game counts as directed at children, because content, art style, music and advertising all affect the answer.

Common problems we see

An ad SDK still collecting device identifiers in a child-directed game.
Analytics events that include free-text fields where children type names.
Privacy policies that do not match what the game actually collects.
No written retention policy, so data is kept indefinitely.
Social features switched on by default for young players.

Store rules add to COPPA

Apple and Google have their own rules for apps aimed at children, including limits on third-party analytics and ads in Kids categories and Families programs. Meeting COPPA does not automatically meet store rules, and vice versa. See app store rules for kids games.

A practical checklist

Decide whether your game is directed at children or has actual knowledge of child users.
Audit and configure every SDK.
Switch to contextual or child-safe advertising, or remove ads.
Update your privacy policy and direct notices.
Write and follow security and retention policies.
Test parental consent and the no-consent experience.
Get legal advice for your situation.

Getting help

We build educational and family games with privacy designed in from the start. See mobile game development and our educational game cost guide.

Sources: Federal Register: Children's Online Privacy Protection Rule (2025) · Davis Polk: new COPPA obligations take effect · Latham & Watkins: FTC publishes updates to COPPA Rule. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Cozy Game Design: How to Make a Relaxing Game Players Love

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

A cozy game makes players feel safe, unhurried and satisfied. Keep stakes low, let players set their own goals, build a satisfying loop of growing, crafting or decorating, and wrap it in warm art and gentle sound. The hard part is making simple actions feel rewarding without turning them into a grind.

What makes a game cozy

Ingredient	What it means in practice
Low stakes	No harsh failure; mistakes are small and recoverable
Gentle goals	Players choose what to do next; no pressure
Satisfying loops	Plant, grow, harvest; gather, craft, decorate
Warmth	Soft colours, rounded shapes, pleasant sounds
Self-expression	Decorate, customise, build your own space
Abundance	Resources feel plentiful rather than scarce
Kindness	Friendly characters and supportive community

Design the core loop first

Every successful cozy game has a loop players enjoy repeating. Pick one, such as farming, cafe management, creature care or home decorating, and make it satisfying in isolation before building a world around it. Feedback matters enormously: a pleasing sound when a plant is watered, a small animation when an item is placed, a visible change in the world as the player progresses. Our guide to game feel explains how this works.

Goals without pressure

Cozy players dislike being rushed. Use gentle goals: requests from characters, collections to complete, areas to restore. Let players ignore them and return later. If you use time, such as days and seasons, make missing something a mild inconvenience, not a punishment.

Art and sound

Soft, warm palettes and clear, readable shapes.
Small, charming animations that reward attention.
Gentle music with variety, so it does not become tiring.
Satisfying sound effects for every common action.
Readable UI with comfortable text sizes.

Customisation and expression

Decorating a room, designing a garden or dressing a character lets players make the game their own. Customisation also drives sharing: players post screenshots of their creations, which is free marketing.

Give players plenty of items to collect and arrange, and make placing them easy and forgiving, with undo and free movement.

Pacing for different sessions

Some players want ten minutes before bed, others a whole afternoon. Provide natural stopping points, such as the end of a day, and make it easy to pick up where you left off. On mobile, short sessions should still feel complete.

Progression without pressure

Cozy games still need progression, or players drift away. Unlock new tools, recipes, areas and decorations at a steady pace, and let players see what is coming next. Progress should feel like the world blooming rather than a checklist being ticked off, so tie unlocks to visible changes in the player's space.

Pitfalls to avoid

Busywork : repetitive tasks with no satisfaction or purpose.
Grind : long waits or repetition to unlock basic content.
Pressure timers that punish players for stepping away.
Aggressive monetisation that breaks the feeling of safety.
Too many systems at once , overwhelming new players.

Monetisation that fits

On PC and console, cozy games usually sell as premium titles, sometimes with paid expansions. On mobile, cosmetics and decoration items fit the genre well, while energy systems and pay-to-skip timers clash with the cozy feeling. See ads vs in-app purchases.

Scope for a first cozy game

One core loop and one or two supporting activities.
A small world that feels lived in.
A handful of characters with personality.
Content that can grow through updates after launch.

Characters and community

Cozy games often feel like a small community where the player belongs. Give characters simple routines, personal requests and small stories that unfold over time. Friendships that grow through gifts and conversations give players a reason to return each session. Keep dialogue warm and short, and let characters react to what the player builds or changes, so the world feels alive.

Accessibility fits the genre

Cozy games attract a broad audience, including players new to games and players with disabilities. Readable text, remappable controls, colour-blind friendly palettes, adjustable game speed and the option to turn off timers all fit naturally with cozy design and widen your audience.

Updates after launch

Many cozy games grow for years after release with seasonal events, new items and new areas. Plan your content pipeline so adding decorations, recipes or creatures is quick. Seasonal updates also give you natural moments to bring players back and attract new ones.

Testing cosiness

Playtesting a cozy game is about feelings as much as bugs. Ask testers how they felt after a session, whether they wanted to keep playing, and whether anything stressed them. Watch for moments where players hesitate, feel lost or feel pressured, and smooth them out. A cozy game should feel easy to return to after a break.

Marketing a cozy game

Cozy games have a passionate community. Share development clips that show satisfying moments, build a wishlist early, and connect with streamers who play cozy games. A Steam Next Fest demo can work well; see Steam Next Fest February 2027.

Sources: Wikipedia: Cozy game · Wikipedia: Game design · Game Accessibility Guidelines. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

How to Make a Horror Game: Design Techniques That Work

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

A good horror game is built on anticipation, not shocks. Make the player expect something bad, keep them vulnerable, let sound and darkness do the work, and give them quiet moments so the scary ones land. Keep the scope small: one location, one threat and a playtime of an hour or two is enough for a strong first horror game.

Fear comes from anticipation

The scariest moment is usually just before something happens. Players imagine worse things than you can show. Design for that: hint at danger, delay the reveal, and let the player's imagination fill the gap.

Tension and release

Constant fear becomes numbness. Build cycles: tension rises as the player explores, peaks with a threat or scare, then releases into a safe moment. The safe moment makes the next rise effective. Map these cycles across your level like a heartbeat.

Sound does most of the work

Silence makes players listen, and listening makes them nervous.
Distant, directional sounds suggest something is out there.
Music that stops is often scarier than music that swells.
Footsteps and breathing make the player feel present and exposed.

Budget real time for sound. Many small horror games succeed with simple visuals and excellent audio. See how video game music is made.

Light and visibility

Limited light creates uncertainty. Flashlights with narrow beams, flickering bulbs and fog all restrict what the player sees. Be careful not to make the game so dark it becomes frustrating: players should be able to navigate, just not see everything.

Vulnerability

A player with a powerful weapon is not afraid. Limit ammunition, healing and abilities, or remove combat entirely and make hiding and running the main tools. Vulnerability is the core of most horror.

Designing the threat

Reveal it slowly: sounds, then shadows, then glimpses.
Give it consistent rules players can learn and fear.
Let players outsmart it sometimes, so they keep trying.
Avoid showing it in full, bright light too often.

Jump scares: use sparingly

Jump scares work best when they are rare and earned by tension. Too many make players expect them, and the game feels cheap. A good rule is to fake out the player more often than you actually scare them.

Pacing a horror game

Section	Purpose
Opening	Establish normality and the first hint that something is wrong
Exploration	Rising tension, clues, environmental storytelling
First encounter	Reveal the threat partially; teach its rules
Escalation	Fewer safe places, more pressure
Climax	Face or escape the threat
Ending	Release, and perhaps a final unsettling note

Scope a horror game you can finish

One location, such as a house, hospital, ship or forest.
One main threat with clear rules.
One to two hours of play.
Simple mechanics: walk, look, interact, hide, run.

Short horror games are popular with streamers, because viewers enjoy watching reactions. That makes them a good fit for small teams. See game development mistakes to avoid for scoping advice.

Horror on mobile and in VR

On phones, horror works best with headphones, short sessions and simple controls; design scares that still land on a small screen in a bright room. In VR, horror is far more intense, so comfort matters even more: avoid forced camera movement, give players control over locomotion, and be careful with scares that make people step back physically.

Accessibility and comfort

Warn about flashing lights and offer a way to reduce them.
Provide subtitles and captions for important sounds.
Offer brightness and gamma settings.
Consider an option to reduce intensity or skip the scariest sections.

Playtesting horror

Watch players rather than asking them. Note where they hesitate, lean back, laugh nervously or get bored. Laughter in the wrong place usually means a scare did not work. Test with people who did not build the game; developers are immune to their own scares.

Environmental storytelling

Horror works best when players piece the story together themselves. Notes, photographs, damaged rooms and objects left behind can tell what happened without cutscenes. Each discovery should raise a question as well as answer one, which keeps players moving forward even when they are afraid. Our storytelling techniques guide covers this in more detail.

Common mistakes

Making the game so dark players cannot navigate.
Too many jump scares, so players stop reacting.
A monster that is shown clearly too early.
Long stretches with no tension at all, or no relief at all.
Puzzles so hard they break the mood with frustration.

Marketing a horror game

Horror is one of the best genres for streaming and short video, because viewers enjoy watching reactions. Send early builds to creators who play horror, release short clips of tense moments, and time announcements around Halloween and Friday the 13th. A free demo or short prequel can build an audience before launch.

Engine choice

Unity and Unreal both suit horror. Unreal's lighting helps realistic atmospheres, while Unity is a common choice for stylised and mobile horror. Atmosphere matters more than graphical fidelity. We have built horror and escape games, such as Pumpkin Man Haunted Escape and Scary Santa Horror House.

Sources: Wikipedia: Survival horror · Wikipedia: Psychological horror · Game Accessibility Guidelines. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Nintendo Switch 2 Game Development: How to Get There

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

To develop for Nintendo Switch 2, a studio registers on the Nintendo Developer Portal and must be approved by Nintendo before it gets platform tools and hardware. Unity supports Switch 2 as an add-on to Unity 6 for approved developers, and Unreal Engine supports Nintendo platforms for approved developers too. Plan for performance work, controls, certification and some lead time for hardware. Studios without approval often work with a partner who already has it.

Step 1: get approved

Nintendo controls access to its platforms. Developers register on the Nintendo Developer Portal and apply. Approval gives access to documentation, tools and the process for obtaining development hardware. Nintendo looks at the company and its plans, and it has been careful about the quality of titles coming to its store.

Step 2: choose your engine path

Engine	Switch 2 support
Unity	Unity announced Switch 2 support as an add-on to Unity 6 for approved Nintendo developers
Unreal Engine	Supported for approved Nintendo developers through Epic and Nintendo channels
Godot	Console support usually comes through third-party porting companies
Custom engine	Possible, with platform SDK access after approval

Most smaller studios use Unity or Unreal for console projects because platform support and documentation are already in place.

Step 3: plan for hardware lead time

Reports from 2025 and 2026 said some studios waited for development hardware. Build that uncertainty into your schedule: you can do a lot of preparation on PC first, such as controller support, performance budgets and UI scaling, so the console phase is shorter when hardware arrives.

Step 4: the technical work

Performance in two modes

Switch 2 runs docked on a TV and handheld. Games need stable performance in both, usually with different resolution or quality settings. Profile early and often on the real hardware.

Controls

Support Joy-Con and Pro Controller layouts, show correct button prompts, and test that every menu works without touch where touch is not available.

UI and text

Text must be readable on the handheld screen and on a TV across the room. Add text scaling if your game is text-heavy.

Saves, accounts and suspend

Players suspend and resume constantly on a hybrid console. Saves must be robust, and the game must handle sleep and resume cleanly.

Step 5: certification and release

Before release, Nintendo checks games against its technical requirements. Failing certification means fixing issues and resubmitting, which costs time. You also need age ratings for each region and store assets for the eShop. Plan testing time specifically for certification requirements, not just general bug fixing.

Should you port an existing game?

Porting a game that already sells well on PC or mobile is often the lowest-risk way onto Switch 2, because you know the game works and have marketing material. Games that suit handheld play, short sessions and controller input tend to fit best. Our game porting guide covers how ports are scoped and priced.

Working with a partner

A porting or co-development partner with Nintendo approval and console experience can shorten the path, handle certification and avoid common mistakes. Check that the partner has shipped console titles, that you keep ownership of your code, and that the contract covers certification fixes. See how to choose a game development studio.

A realistic timeline

Phase	What happens
Approval	Register on the Developer Portal and wait for Nintendo to approve the company
Preparation on PC	Controller support, UI scaling, performance budgets, save handling
Hardware and platform setup	Obtain development hardware and set up the engine add-on
Porting and optimisation	Get the game running, then tune docked and handheld modes
Certification and ratings	Test against requirements, submit, fix and resubmit if needed
Launch and patches	Release on the eShop and fix any console-specific issues

The length of each phase depends heavily on the game, so ask a partner for a phase-by-phase estimate rather than a single number.

Starting the preparation work on PC while approval and hardware are pending is the single best way to shorten the overall schedule, because most controller, UI and save-system work does not need the console at all.

Performance tips for a hybrid console

Set separate quality presets for docked and handheld play.
Watch memory closely; console memory budgets are fixed.
Reduce overdraw and expensive post-processing in handheld mode.
Keep loading times short, since players often play in short sessions.
Test battery-heavy scenes for heat and frame-rate drops over long sessions.

Budget items people forget

Development hardware and test units.
Certification testing and resubmission time.
Age ratings in each region.
eShop assets and localisation.
Post-launch patches for console-specific issues.

Is Switch 2 worth it for an indie game?

For the right game, yes: Nintendo players buy many games that suit handheld and couch play. But reports also suggest that success on the platform is not automatic for third-party titles, and visibility in the eShop takes marketing effort. Treat Switch 2 as one part of a multi-platform plan rather than the whole strategy.

Sources: Nintendo Developer Portal · Unity: support for developers targeting Nintendo Switch 2 · LevelUp: reports on Switch 2 dev kit access. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

WebGPU for Browser Games in 2026: What Changed

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

WebGPU is the modern replacement for WebGL, and it is now supported across Chrome, Edge, Safari and Firefox, including Safari on iPhone and iPad. It gives browser games better access to the GPU, including compute shaders, with less CPU overhead. For most new 3D browser games, use WebGPU where it helps and keep a WebGL 2 fallback for older devices. Simple 2D and casual games can stay on WebGL with no real downside.

Where WebGPU runs

Browser	Support
Chrome and Edge (desktop)	Windows, macOS and ChromeOS from version 113
Chrome on Android	From Chrome 121 on Android 12 and later
Safari	Safari 26 on macOS, iOS, iPadOS and visionOS
Firefox	Windows from version 141; Apple silicon Macs from 145; other platforms in progress

Coverage is broad, but not universal. Older phones, older operating systems and some Linux and Android setups still need WebGL.

What WebGPU improves over WebGL

Compute shaders. Run particle systems, physics, culling and other work on the GPU.
Lower CPU overhead. More objects on screen before the CPU becomes the bottleneck.
A modern design closer to Vulkan, Metal and Direct3D 12, which engines already target.
Better error handling and more predictable behaviour across browsers.

Engine support

Engine or library	WebGPU status
Unity	Experimental WebGPU option for Web builds, enabled manually in Player settings, with WebGL 2 as a fallback
Babylon.js	Supports WebGPU alongside WebGL
three.js	Offers a WebGPU renderer alongside WebGL
Godot	Web exports use WebGL 2
PlayCanvas	Has added WebGPU support alongside WebGL

When to use WebGPU

3D games with many objects, effects or detailed scenes.
Product configurators and showrooms with high-quality rendering.
Simulations and training that benefit from GPU compute.
WebXR projects that need extra performance.

When WebGL is still fine

Casual 2D games, puzzles and hyper-casual web games.
Games that must run on the widest range of old devices.
Projects where download size and load time matter more than visual quality.

Building with a fallback

The safest approach is to detect WebGPU support at start-up and fall back to WebGL 2 when it is missing. Engines such as Unity, Babylon.js and three.js make this easier. Test both paths, because players on older devices will see the fallback.

Performance tips for the web

Keep the initial download small and stream extra content later.
Compress textures and audio for the web.
Watch memory, especially on iPhones, where browsers enforce limits.
Test on mid-range Android phones, not just desktop.
Cap frame rate on mobile to save battery and heat.

Common pitfalls

Assuming every player has WebGPU. Always detect support and fall back.
Ignoring load time. Better graphics do not help if players leave during loading.
Desktop-only testing. Phones behave very differently, especially for memory and heat.
Synchronous GPU readback. WebGPU does not allow it; engines provide asynchronous alternatives.
Shader differences. Shaders may need changes when moving from WebGL to WebGPU.

WebGPU for product showcases and training

Beyond games, WebGPU helps any interactive 3D on the web: product configurators, furniture and car viewers, architectural walkthroughs and training simulations. These projects often run on company laptops and phones where installing an app is a barrier, so a fast, high-quality web version can reach far more people. We build these alongside AR versions; see AR in retail for examples.

Questions to ask before starting

Which devices and browsers do your players actually use?
How large can the first download be before players leave?
Do you need effects that only WebGPU makes practical?
Will the game also ship as a native app, and can the code be shared?

Distribution for WebGPU games

Browser games reach players through web game portals, social and messaging platforms, your own website, and playable ads that link to app stores. Each channel has its own size limits and technical rules, and many portals still expect games that run on WebGL. Check the requirements of your target portals before choosing WebGPU-only features, and keep the fallback path in good shape so the game can be listed widely. Our playable ads guide covers the strict limits ad networks set.

The bottom line

WebGPU removes a long-standing ceiling on browser graphics. Use it where it clearly improves the experience, keep WebGL 2 as a fallback, and keep download size and load time under control. For simple games, the best web experience is still the one that loads instantly.

What it means for web games as a business

Browser games are growing again through web portals, social platforms and playable ads. WebGPU raises the ceiling on what those games can look like, which makes the web more attractive for 3D titles, product showcases and training. Our web games guide covers distribution and monetisation, and WebXR covers VR and AR in the browser.

A sensible plan

Decide whether your game needs WebGPU features or just runs well on WebGL.
If it does, choose an engine with mature WebGPU support and a fallback.
Prototype the heaviest scene and profile it on target phones.
Ship with feature detection and monitor which path players use.

Sources: web.dev: WebGPU is now supported in major browsers · MDN: WebGPU API · Unity: WebGPU · W3C: WebGPU specification. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

How to Make a Roblox Game in 2026: A Practical Guide

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

To make a Roblox game, install the free Roblox Studio, start from a template, learn Luau for your game logic, build a small core loop, test it with friends, then publish it as an experience. You can earn Robux through game passes and developer products, and creators who meet Roblox's rules can convert earned Robux to money through the Developer Exchange. The hard part is not publishing; it is building something players come back to.

What you need

A Roblox account and Roblox Studio, which is free on Windows and Mac.
A basic understanding of Luau, Roblox's scripting language based on Lua.
Time to playtest with real players, not just yourself.

Step 1: learn the editor with a template

Roblox Studio includes templates such as obstacle courses and racing games. Open one, move parts, change materials and press Play. Learn the Explorer and Properties panels, and how parts, models and scripts fit together. An afternoon with a template saves days of confusion later.

Step 2: learn enough Luau

Luau scripts control what happens: doors that open, points that add up, enemies that move. Start with the basics: variables, functions, events such as a player touching a part, and the difference between server scripts and local scripts. Roblox's own documentation has step-by-step tutorials. Most games need only a small set of patterns used well.

Step 3: pick a small core loop

Successful Roblox games usually have a simple loop players repeat: complete a course, collect and upgrade, survive a round, or build and show off. Pick one loop and make it satisfying before adding anything else.

Genre	Core loop	Good first project?
Obby	Run and jump through a course	Yes, easiest to start
Tycoon	Earn, buy upgrades, earn faster	Yes, teaches data and saving
Simulator	Collect, upgrade, unlock areas	Moderate
Round-based survival	Survive events with others	Moderate, needs good server logic
Roleplay	Social play in a shared world	Harder, depends on community

Step 4: save data and multiplayer

Most games need to remember player progress, which Roblox handles through its data storage services. Roblox games are multiplayer by default, so think about what the server controls and what each player's device controls. Keep important logic, such as currency, on the server to prevent cheating.

Step 5: test with real players

Use Studio's local test with several simulated players, then invite friends. Watch where they get confused or bored. The first minute matters most: players decide quickly whether to stay.

Step 6: publish

Publish the place to Roblox from Studio.
Set the experience to public when you are ready.
Create a clear icon and thumbnails that show what players do.
Write a short description and choose the right genre settings.
Fill in the content and age questionnaire honestly.

How Roblox games make money

Option	What it is
Game passes	One-off purchases for permanent perks, such as a speed boost or VIP area
Developer products	Repeatable purchases, such as in-game currency or extra lives
Other options	Roblox also offers creator earnings such as subscriptions and Premium-based payouts; check the Creator Hub for current programs

Price items fairly and make paid perks optional. Games that feel pay-to-win tend to lose players.

How creators get paid

Creators earn Robux, and those who meet Roblox's eligibility rules can exchange earned Robux for money through the Developer Exchange (DevEx). Roblox publishes the current requirements and rate on its Creator Hub, so check there rather than relying on figures quoted online. The creator economy is large: Roblox reported Developer Exchange fees of $363 million in the second quarter of 2026.

Safety and young players

Many Roblox players are children, and Roblox has detailed rules on content, chat, advertising and purchases. Answer the experience questionnaire honestly so your game reaches the right age group, avoid designs that pressure players into spending, and follow Roblox's policies on promoting purchases. Respecting these rules protects your game from moderation action and builds trust with parents.

Common beginner mistakes

Building a huge map before the core loop is fun.
Trusting the player device with currency or important logic, which invites cheating.
Forgetting to save progress, or saving too often and hitting limits.
Weak icons and thumbnails that do not show what the game is.
Launching and then not updating, so early players have no reason to return.

Growing a Roblox game

Update often. New content and events bring players back.
Build community. Groups and social channels help players come back together.
Test thumbnails and icons. They decide whether players click.
Watch analytics. Retention and session length show whether the loop works.

Roblox for brands

Many brands build Roblox experiences to reach younger audiences. Those projects need careful planning around Roblox's rules for advertising and young players, plus a game that stands on its own rather than a thin advert. Studios usually scope them like a small live game. See gamification for brands for how branded games are planned.

Next steps

If you are learning, our how to learn game development guide and tutoring can help. If you are comparing platforms, see UEFN and Fortnite islands and how to make a video game.

Sources: Roblox Creator Hub documentation · Roblox: Luau · Roblox: earning on Roblox · Roblox Q2 2026 results (SEC filing). Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

UEFN: Building and Earning From Fortnite Islands

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

UEFN is a free version of Unreal Editor for building Fortnite islands, using Fortnite's assets, your own assets and Epic's Verse language. Epic's engagement payouts send 40% of net revenue from the Fortnite Item Shop and most real-money purchases to eligible island publishers each month, split by how much players engage with each island. It is a real opportunity for studios and brands, but payouts follow engagement, so islands need to be fun, replayable and regularly updated.

What UEFN is

Fortnite Creative let players build islands from in-game pieces. UEFN goes further: it is a version of Unreal Editor made for Fortnite, so creators can import custom models, build custom logic in Verse and use many of Unreal's tools. Islands still run inside Fortnite, which gives them access to a very large player base without players installing anything new.

How engagement payouts work

Epic puts 40% of net revenue from the Item Shop and most real-money purchases into a pool each month.
The pool is divided among eligible island publishers, including Epic's own islands.
Each island's share depends on player engagement, including how popular it is, how engaged players are and whether it attracts new or returning players.
Net revenue means revenue after platform fees, or after payment processing for direct sales, as Epic defines it.

Publishers must meet Epic's eligibility rules, including being a legal adult and meeting activity or other requirements. Epic said at State of Unreal 2026 that it had paid over $1 billion to UEFN developers.

Verse: the language to learn

Verse is Epic's programming language for UEFN. It is designed for game logic in shared, live worlds. Epic has said Unreal Engine 6 will move gameplay programming towards Verse, so learning it through UEFN is also preparation for the next Unreal. See Unreal Engine 6: what developers should know.

Island types that do well

Type	Why it works
Competitive modes (box fights, zone wars)	Quick, repeatable rounds for skilled players
Tycoons and simulators	Progression that brings players back
Horror and story maps	Shareable experiences, strong with creators and streamers
Party and social games	Groups of friends play together
Branded experiences	Campaigns reaching Fortnite's audience

Building an island step by step

Install the Epic Games Launcher and UEFN.
Start from a template or a blank island and learn the devices system.
Prototype the core loop with built-in devices before writing Verse.
Add Verse where devices are not enough.
Import custom art carefully: performance budgets apply across all platforms Fortnite runs on.
Playtest with a group, then publish following Epic's rules and review.

Performance and platforms

Fortnite runs on PCs, consoles and phones, so islands must perform across very different hardware. Keep memory and object counts within UEFN's budgets, test on lower-end devices, and avoid heavy effects that only work on high-end PCs.

Rules to respect

Epic's content rules and ratings requirements.
Rules on using third-party intellectual property; you need rights to what you import.
Rules on promotion, advertising and rewards, especially for brand islands.
Rules on young players, since Fortnite's audience includes children.

UEFN for brands

Brands use islands to reach Fortnite players with an experience rather than an advert. The best brand islands are good games first, with the brand built into the theme and rewards. Plan the island like a small live game, with updates and a measurement plan, and check Epic's rules for branded content. See gamification for brands.

UEFN or Roblox?

Both offer huge audiences and creator payouts. UEFN suits teams with Unreal experience, higher visual fidelity and competitive or action modes. Roblox suits social, simulation and younger-audience games with its own long-established creator economy. Our Roblox guide covers the other side.

Costs and team

UEFN itself is free. The costs are people and time: level design, art, Verse programming, testing and ongoing updates. A simple competitive map can be built by a very small team, while a polished tycoon or story island with custom art is closer to a small game production. Budget for updates after launch, because engagement, and therefore payouts, usually depends on giving players new reasons to return.

Common mistakes

Copying a popular island format without a clear twist.
Importing heavy custom assets that hurt performance on consoles and phones.
Publishing once and never updating.
Using third-party characters or music without rights.
Treating a brand island as an advert rather than a game.

A simple launch plan

Soft-launch the island to friends and a small community for feedback.
Fix confusing moments and performance problems on lower-end devices.
Prepare a short trailer and thumbnail that show the fun in seconds.
Reach out to creators who play your island type.
Plan the first update before launch, so returning players find something new within weeks.

Measuring success

Payouts follow engagement, so track the same numbers Epic cares about: how many players try the island, how long they play, and whether they come back. Update regularly to keep returning players, and use creators and streamers to bring new ones.

Sources: Epic: Fortnite developer program FAQs · Fortnite: UEFN and Creator Economy 2.0 · Epic: Verse language reference · Unreal Engine: State of Unreal 2026. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Holiday LiveOps Calendar 2026: Events From Black Friday On

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

Plan holiday events 6 to 8 weeks ahead, submit app updates early, and switch events on with server-side configuration so you are not waiting on store review during the busiest weeks. Key dates this season: US Thanksgiving on November 26, Black Friday on November 27, Cyber Monday on November 30, Christmas on December 25, New Year on January 1, and Lunar New Year in early February 2027.

The 2026 holiday calendar

Date	Moment	Event ideas
November 26	US Thanksgiving	Gratitude login rewards, community goals
November 27	Black Friday	Limited bundles, starter-pack deals
November 30	Cyber Monday	Last-chance offers, digital-only items
December 1 to 24	Advent period	Daily login calendar, seasonal map or theme
December 25	Christmas	Gifts, free premium items, gifting between friends
December 31 to January 1	New Year	Countdown events, year-in-review stats, New Year challenges
Early February 2027	Lunar New Year	Themed cosmetics and red-envelope style rewards for relevant markets

Why timing matters

More players and new devices. Holidays bring returning and new players.
Slower reviews. Store review can take longer near major holidays, so do not rely on a last-minute build.
Higher ad costs. Advertisers compete in the fourth quarter, which usually raises user acquisition costs.
Team time off. Plan coverage so a bug on December 25 does not wait a week.

Preparation timeline

When	What to do
8 weeks before	Choose events, offers and themes; agree success metrics
6 weeks before	Build content and the configuration to switch it on remotely
4 weeks before	Test events end to end, including time zones and edge cases
3 weeks before	Submit any app updates; set up store event listings
1 to 2 weeks before	Code freeze; prepare support replies and social posts
During events	Monitor crashes, purchases and economy; adjust offers carefully

Make events server-driven

The safest holiday events need no new build. Ship the content in an earlier update, hidden, and switch it on with remote configuration. That lets you start, extend or fix events without store review. It also lets you test the event early with a small group.

Use store features

Apple lets developers show in-app events on the App Store, and Google Play offers promotional content in Play Console. Both can put your event in front of players browsing the store. Set them up early, because they have their own review and timing rules.

Event ideas that work

Login calendars that reward daily visits through December.
Limited bundles with clear value, for Black Friday and Cyber Monday.
Gifting between friends, which also brings new players.
Seasonal cosmetics that players can show off.
Returning-player rewards for lapsed players who come back over the holidays.
New Year challenges that start January with a goal.

Protect the game economy

Generous holiday rewards are good for goodwill but can damage your economy if they flood players with currency. Model the effect of every reward, cap repeatable gifts, and avoid discounts that teach players to wait for sales. Track spending and progression daily during events. Our mobile game KPIs guide explains what to watch.

Stability first

Freeze code a week or two before the busiest period.
Load-test servers for higher traffic.
Prepare a rollback plan for every event.
Agree an on-call rota across holidays.

Measuring an event

Metric	What it tells you
Daily active players during the event	Whether the event brought people in
Returning lapsed players	Whether reactivation offers worked
Event completion rate	Whether goals were reachable and fun
Revenue per daily active player	Whether offers were attractive
Retention one week after	Whether the event had lasting value

Compare against a normal week, not just the previous day, so seasonal effects do not mislead you.

Marketing around events

Events work best when players know about them. Announce them in the game a few days early, post on social channels, update store screenshots or promotional content, and send push notifications sparingly to players who have opted in. If you run paid user acquisition, consider whether higher fourth-quarter prices are worth it for your game, or whether to focus spend on early December and January, when costs are often easier.

Regional calendars

If your players are global, the western holiday calendar is only part of the picture. Plan for the moments that matter in your biggest markets, such as Lunar New Year in East Asia, Ramadan and Eid in the Middle East, and Diwali in South Asia. Check exact dates each year, localise event names and art, and make sure events start at sensible local times rather than at midnight in one time zone.

After the holidays

January is a good time to review: which events brought players back, which offers worked, and what broke. Use the results to plan the next season. If your team is small, outside help with live operations can keep events running without burning out the core team; see LiveOps outsourcing and launching a live-service game.

Sources: Apple: in-app events · Google Play Console: promotional content · Apple: App Review. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Meta VR in 2026: Why Quest 3 Is Still the Build Target

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

Meta reported that Reality Labs revenue fell 6% to $443 million in the third quarter of 2026 because of lower Quest headset sales, partly offset by AI glasses growth, and said future VR hardware will need major breakthroughs. For developers, the takeaway is that Quest 3 and Quest 3S remain the devices to build for, with no new generation to wait for. Build to Quest 3S performance, use OpenXR, and plan for a long life on today's hardware.

What Meta reported

Reality Labs revenue of $443 million in Q3 2026, down 6% year on year.
The decline came from lower Quest headset sales, partly offset by growth in AI glasses revenue.
Meta said it will bring new VR devices to market only when they represent major breakthroughs.
Meta described realigning Reality Labs investment toward AI integration.

Reality Labs continued to report large operating losses, which is why Meta is pacing its hardware investment.

What it means for VR developers

Quest 3 and 3S are the target for the foreseeable future

Without a near-term successor to plan around, the installed base you can reach is Quest 3 and Quest 3S. Set your performance budget to Quest 3S, the lower-cost model, and treat Quest 3 as the device where you can add extra polish.

Long hardware life is good for budgets

A stable device target means fewer surprises. Performance work done now keeps paying off, and training content stays usable on the same headsets for longer.

Open standards reduce risk

Building on OpenXR keeps the door open to other headsets, including PC VR and devices from other vendors. New multitasking standards are arriving too; see OpenXR spatial containers.

What it means for VR training

Enterprise training buyers want devices they can rely on for several years. Quest 3 and 3S remain capable training devices, but buyers should plan device management carefully, because Meta ended its Quest for Business offering. We explain the options in what the end of Quest for Business means. For return on investment, see enterprise VR training ROI.

What it means for VR games

The VR games market rewards focused, polished experiences rather than huge scope. With a stable device base, studios can plan content updates and live operations with confidence. Keep scope tight, launch on the Horizon Store with a strong first impression, and consider a PC VR version through Steam for extra reach.

Where AI glasses fit

AI glasses are growing, but they are a different category. They suit quick, glanceable information and voice interaction, not full immersive training or games. If a client asks whether to build for glasses instead of VR, the honest answer depends on the use case; our smart glasses guide explains what glasses can and cannot do.

A practical build plan for 2026 and 2027

Decision	Recommendation
Primary device	Quest 3S as the performance floor, Quest 3 for extra quality
API	OpenXR through Unity or Unreal
Store	Horizon Store; Steam for PC VR where it makes sense
Reach	Consider a WebXR or flat-screen companion for people without headsets
Training fleets	Plan device management and updates up front
Future hardware	Do not plan deadlines around unannounced headsets

Performance checklist for Quest 3S

Hold a stable frame rate at the target refresh rate during real use, not just in empty scenes.
Keep draw calls and transparent overdraw under control.
Use baked lighting where possible and limit real-time shadows.
Test comfort: locomotion options, stable horizons, and readable text.
Profile on the device regularly, not only in the editor.

Reaching people without headsets

A smaller VR hardware push makes reach more important. Many projects benefit from a companion that works without a headset: a WebXR version that runs in a browser, a flat-screen mode for desktop, or a mobile app for preparation and results. Training programmes often use a browser module for theory and VR for practice. See WebXR in the browser for what runs where.

Questions to ask before you commission a VR project

Which headsets do your users already own, and how many?
Who will manage the devices, updates and charging?
Does the app need to work offline?
What will you measure to decide whether it worked?
Is there a flat-screen or browser alternative for people who cannot use VR?

Clear answers to these questions matter more than the headset model, and they keep the project focused on outcomes rather than hardware.

The bottom line

Meta is slowing new VR hardware while it waits for real breakthroughs. That is not bad news for developers: it means a stable target. Build well for Quest 3 and 3S, keep your app portable through OpenXR, and focus on quality. Our VR packages start at $999 for a single-scenario proof of concept and $2,999 for a complete app.

Sources: CNBC: Meta Q3 2026 earnings · Road to VR: Meta confirms lower Quest sales · Meta Q3 2026 earnings call transcript. Checked October 27, 2026.

Related: VR development · VR packages · Get a quote

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Google Play Fees 2026: What Game Developers Now Pay

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

Google Play now separates its service fee from its billing fee. When you use Google Play billing in the EEA, UK or US, the billing fee is 5%. The in-app purchase service fee drops to 20% for new installs, developers in Google's new quality programs pay 20% on existing installs and 15% on new installs, and recurring subscriptions carry a 10% service fee. The changes roll out region by region between June 2026 and September 2027. Check Play Console for the exact rates that apply to your account.

What changed

Google's March 2026 announcement followed the resolution of its disputes with Epic Games. The main changes:

Item	What Google announced
Billing fee	Separate from the service fee; 5% in the EEA, UK and US when using Google Play billing
IAP service fee, new installs	20% for first-time installs after the new fees launch in a region
Program participants	20% on transactions from existing installs, 15% from new installs
Recurring subscriptions	10% service fee
Programs	New Apps Experience Program and a revamped Google Play Games Level Up program, with quality benchmarks
Registered App Stores	Optional program giving qualifying sideloaded stores a smoother install flow

When it applies

By June 30, 2026: EEA, UK and US.
By September 30, 2026: Australia.
By December 31, 2026: Korea and Japan.
By September 30, 2027: the rest of the world.

If you sell in several regions, you will have different fee structures for a while. Revenue models should be built per region.

What "new installs" means for games

The lower rates apply to transactions from installs that happen after the change launches in a region. For a live game, that means revenue from long-time players and newer players can carry different fees. Games that acquire many new players benefit sooner; games that earn mostly from a loyal existing base see a smaller change at first.

Google Play Games Level Up

Level Up is Google's program for games, revamped as part of these changes. Participants who meet its benchmarks pay the lower program rates. Google said the programs would launch by September 30 for the EEA, UK, US and Australia, with more details published over time. Check Play Console for current requirements; they focus on quality across Android devices and form factors.

US: external links and alternative billing

In the US, developers enrolled in the external content links and alternative billing programs must report transactions and pay the relevant service fees, as set out in Play Console Help. If you link players to web purchases, read the current US requirements carefully, including reporting deadlines.

How to model the impact

Split revenue by region and by install cohort (before and after the change).
Separate subscriptions from one-off purchases.
Apply the service fee plus the 5% billing fee where you use Google Play billing in the EEA, UK and US.
Estimate the effect of joining Level Up if your game can meet its benchmarks.
Compare with your web shop costs if you use external links, including payment processing and the service fees that still apply.

What it means for monetisation design

Subscriptions look more attractive at a 10% service fee, for games where a subscription fits, such as VIP passes or ad-free tiers.
Acquisition matters more , because new installs carry lower rates.
Quality programs are worth tracking : device performance and stability now have a direct link to fees.

For choosing a model, see ads vs in-app purchases and mobile game KPIs.

A worked example

Imagine a game in the US that earns from one-off in-app purchases and uses Google Play billing. A purchase from a player who installed after the change launched carries the new-install service fee plus the 5% billing fee. The same purchase from a long-time player carries the existing-install rate plus billing. If the game joins Level Up and meets its benchmarks, both rates drop further. Subscriptions sit at a 10% service fee plus billing. The exact numbers for your account appear in Play Console, so use this structure to build a spreadsheet, then fill in your own rates.

Common mistakes when budgeting

Using one global rate for every region during the rollout period.
Forgetting the separate billing fee when using Google Play billing.
Assuming web purchases through external links are fee-free in the US.
Not tracking which purchases come from new installs.
Ignoring tax, refunds and payment processing on web shops.

Getting these right matters most for games with thin margins, such as those that rely on paid user acquisition, where a few percentage points can decide whether a campaign is profitable.

What about the App Store?

Apple's fees and rules are separate and differ by region, including US changes to linking to web purchases. Budget per store and per region rather than assuming one rate. Our 2027 trends guide covers the wider shift in store rules.

The bottom line

Most Android games will keep more of each sale under the new structure, especially from new players, subscriptions and developers in Google's programs. The details vary by region and timing, so model them properly rather than using a single headline rate.

Sources: Android Developers Blog: a new era for choice and openness · Play Console Help: policies for developers serving US users · Play Console Help: service fees. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Steam Next Fest February 2027: Dates and Prep Plan

A Plus Games Studio — Tue, 27 Oct 2026 00:00:00 +0000

The short answer

Steam Next Fest February 2027 runs from February 22 to March 1, 2027, starting and ending at 10:00 AM Pacific. Registration closes on January 10, 2027. You need a Steamworks account in good standing and a public store page. Valve lists further deadlines for your demo and event materials on the Steamworks event page, so register early and work back from those dates.

Key dates

Milestone	Date
Registration closes	January 10, 2027
Event starts	February 22, 2027, 10:00 AM Pacific
Event ends	March 1, 2027, 10:00 AM Pacific
Demo and asset deadlines	Listed on the Steamworks event page; check after registering

Is your game ready for this edition?

Each game can take part in Next Fest once, so choose the edition carefully. February 2027 is right if you can show a polished demo and you plan to release within a few months after the event. If your game is a year or more from release, a later edition may serve you better, because wishlists convert best when launch follows soon after.

Week-by-week plan

Now to mid-November

Decide on the edition and make sure your store page is live as Coming Soon.
Lock the demo scope: one strong slice of the game, usually 20 to 40 minutes.
Start sharing development clips to build your first wishlists.

Mid-November to mid-December

Polish the first five minutes of the demo, where most players decide whether to continue.
Finish capsule art, screenshots and a short trailer that shows gameplay in the first seconds.
Run external playtests and fix crashes and confusing moments.

December to January 10

Register for the event before January 10.
Reach out to press and content creators with demo access and a clear one-line pitch.
Plan a livestream schedule for the event week.

January to the event

Meet Valve's demo and asset deadlines listed on the event page.
Test the demo build that will actually go live, on low-end PCs and Steam Deck if possible.
Prepare posts and a short devlog for the launch of the event.

Event week

Stream regularly and talk to players.
Watch reviews, discussions and crash reports, and patch quickly.
Remind players to wishlist at the end of the demo.

After the event

Thank players and share what you learned.
Announce a release date while interest is high.

What makes a Next Fest demo work

A strong start: no long cutscenes or menus before the fun begins.
A clear goal and an ending that leaves players wanting more.
Stable performance on modest hardware.
A wishlist prompt at the end of the demo.
Controller support if your genre suits it; many players use Steam Deck.

Store page checklist

Capsule art that reads at small sizes.
A short description that says what the player does, not just the setting.
Screenshots of gameplay, not menus.
A trailer that shows gameplay within the first few seconds.
Accurate tags for your genre.

Measuring success

Watch wishlists added during the event, demo players, median play time and how many players finish the demo. Median play time tells you whether the demo holds attention; wishlists tell you whether players want the full game. Our Steam wishlists guide explains how wishlists turn into launch sales.

Common mistakes

Registering late. Miss January 10 and you wait for the next edition.
A demo that is too long or too short. Too short and players cannot judge the game; too long and there is no reason to buy it.
A slow opening. Long intros and tutorials lose players before the fun starts.
No wishlist prompt. Ask clearly at the end of the demo.
Silence during the event. Players and creators reward developers who show up, stream and respond.
Untested builds. A crash on launch during the event is hard to recover from.

Working with press and creators

Next Fest has thousands of demos, so outside attention helps a great deal. Send content creators a short email with a one-line pitch, a key image, a short trailer and a demo key or link, a few weeks before the event. Target creators who already cover your genre rather than the biggest names. After the event, share creator videos on your store page news and social channels to extend the momentum.

Using the demo after Next Fest

You can keep a demo available after the event, and many developers do, because it keeps generating wishlists. Update it with fixes from event feedback, and consider removing it shortly before launch if you want players to buy the full game rather than replay the demo. Whatever you choose, keep the store page news active so new visitors see a game in active development.

Getting help with your demo

If your demo needs polish, performance work or Steam Deck support before the deadline, a short co-development sprint can help. See our general Next Fest guide and PC game development.

Sources: Steamworks: Steam Next Fest February 2027 · Steamworks: Steam Next Fest overview · PC Gamer: Steam events for the first half of 2027. Checked October 27, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.