Can I import my Unity or Unreal project into Gessa?

Not as source. C# scripts and Blueprints do not port, because Gessa authors behavior over its own Script IR. Test meshes and materials as glTF or GLB, then rebuild the rules with AI and visual scripting.

Do my scripts carry over?

No. C#, Blueprints, Luau and hand-written Three.js code do not convert. Re-express behavior through Gessa’s AI and visual scripting; generated code views let you inspect its Script IR projections.

What should I check after importing assets?

Check geometry, materials, textures, scale, orientation and any animation your game uses. glTF and GLB support asset exchange, but your export settings and supported features determine the result.

Is migrating worth it?

Try a small version of your game in Gessa. Evaluate the connected AI, asset, multiplayer and publishing workflow against your project’s requirements, then use that result to plan the migration.

Migrating to Gessa from Unity, Roblox or Three.js

Bring your game ideas and reusable assets into Gessa, then rebuild the behavior around its project and Script IR model. Start with a small glTF or GLB asset transfer and check the result in the engine. Use free built-in AI and visual scripting to shape the rules, with multiplayer, collaboration and browser publishing in the same platform.

What carries over, and what does not

Use glTF or GLB for supported 3D asset transfers and check geometry, materials, textures, scale and orientation in Gessa. Export settings and material features affect the result. Existing C#, Blueprints, Luau and Three.js applications are not drop-in Gessa projects; plan to rebuild their behavior around Script IR.

Start with one playable loop so you can evaluate the whole workflow: imported assets, game rules, shared play and publishing. Gessa brings those tools together; test the features your particular game needs before expanding the migration.

Coming from Unity or Unreal

Use an export tool compatible with your source project to prepare a small glTF or GLB sample. Unreal documents a glTF exporter with material conversion and baking options. Check the exported result in Gessa, including textures, scale and lighting, before transferring a larger collection.

Rebuild behavior next: describe a rule to the built-in AI, shape it with visual scripting, and inspect the generated code views when useful. For multiplayer, define what players share and test it in Gessa’s server-authoritative runtime; existing replication rules still need to be re-expressed and verified.

Coming from Roblox

A move from Roblox is more of a rebuild than an import. Luau scripts and place files do not port, and Gessa publishes to its own browser play pages rather than to the Roblox platform. Bring only 3D models you own or are licensed to reuse, exported as glTF or GLB; marketplace assets stay under their platform terms.

Rebuild the experience with the free built-in AI and visual scripting. Test it with friends, then publish a browser play page through Gessa’s integrated workflow.

Coming from Three.js or a custom web game

Gessa is built on Three.js's WebGPU renderer, so the rendering foundation is familiar, but Gessa is an engine around that library, not a drop-in host for an existing Three.js codebase. Your hand-written source is not a project import, and Gessa uses its own project and script models.

Test your assets as glTF or GLB and rebuild the game in the engine. Gessa connects physics, server-authoritative multiplayer, collaboration and asset generation; use the AI and editing tools to shape the same project as it grows.

A realistic migration plan

Start by deciding what is actually worth keeping: the models and art you own, and the design ideas, not the code. Import those assets, then rebuild the smallest playable loop with the built-in AI before recreating the whole game.

Define the behavior players need to share, test it with more than one player, and verify the published browser link. Expand from a small working game that reuses your assets rather than assuming a line-by-line port will preserve behavior.

Plan around your project’s requirements

List your target devices, visual requirements, existing integrations and authoring needs. Build a representative scene and interaction in Gessa, then evaluate the result on the devices your players use.

Use that trial to plan the next step. A free integrated AI workflow, multiplayer and browser publishing can simplify your process; the actual project test tells you which assets and rules need more work.

Frequently asked questions

Can I import my Unity or Unreal project into Gessa?: Not as source. C# scripts and Blueprints do not port, because Gessa authors behavior over its own Script IR. Test meshes and materials as glTF or GLB, then rebuild the rules with AI and visual scripting.
Do my scripts carry over?: No. C#, Blueprints, Luau and hand-written Three.js code do not convert. Re-express behavior through Gessa’s AI and visual scripting; generated code views let you inspect its Script IR projections.
What should I check after importing assets?: Check geometry, materials, textures, scale, orientation and any animation your game uses. glTF and GLB support asset exchange, but your export settings and supported features determine the result.
Is migrating worth it?: Try a small version of your game in Gessa. Evaluate the connected AI, asset, multiplayer and publishing workflow against your project’s requirements, then use that result to plan the migration.