​
Code

Generate and iterate on scripts. Direct-from-Unity context enables Bezi to make suggestions in full awareness of your entire project, so responses can avoid pitfalls like redundancies, repetition, and inconsistency.

Bezi can help you ‘mass in’ the core fundamentals, so you can focus on the bespoke mechanics; it can help you mock up those mechanics when you aren’t sure how to approach them; and it can simplify small busy work, turning thirty minutes of endless scrolling, copy/pasting, editing, and testing into thirty seconds.

​
Foundational systems:

  • “Make a first person character controller with mouse-based camera movement”
  • “Mock up object pooling for the obstacles and set up the basic obstacle ‘spawning’ and movement system (right to left)”

​
Experimental whitebox mechs:

  • “Prototype a ghost possession mechanic that lets the player take and relinquish control of other characters when in range and spacebar is pressed”
  • “I want a camera system that moves to a fixed CameraLocation when they enter a collider tagged FixedCam, then lerps back to third person when out— what would that code look like?”

​
Adjustments and additions:

  • “Add crouch and jump behavior to the player movement script”
  • “Instead of using a Raycast to detect treasure, can we use a collider on the @Hunter?”
  • “Incorporate the isFalling, isFlying, and isMoving animation bools from @Sarah.controller into CharacterControls.cs”

​
Debug

Troubleshoot errors, whether they’re lighting up the console or glitching out your gameplay. Bezi is backed by scripting expertise, Unity docs, and all indexed contents of your project, so it can decipher and diagnose Console Error gibberish; pinpoint the components and/or scripts behind unexpected behaviors; and expose sources of lag so you can better ID and correct slow-downs.

​
Console errors

  • “What’s up with that NullReference exception?”
  • “How do you fix ‘We can’t assign a new GUID because the asset is in an immutable folder. The asset will be ignored.’?”
  • “I made this shader but now I’m getting this endless loop of errors— why?”

​
Behavioral issues

  • “When I press play, the whole sky turns red. Is it the cloud render feature?”
  • “My character vibrates and hops when stationary on a slanted surface”
  • “Why does the portal gun not work in the Entry scene?”

​
Optimization

  • “Every time the player enters the Dungeon level, the framerate plummets. Why?”
  • “How can I optimize the searching part of Seeker.cs?”
  • “Optimize my project for mobile”

Simplify the process of hunting through assets, scenes, and scripts— no parameter is too specific. Bezi understands the contents of your project, the objects in your scene, and the properties on your assets, so it’s equipped to help you parse through it all to find what you need. Ask Bezi to find the little details that could take endless time to recover (like, “where is this method called?” and “what objects have this box checked?”).

Currently, Bezi’s context does not dive into node graphs/state machines/visual scripting, so while Bezi will know that they’re there, it can’t see how such objects as animators and shader graphs are set up.

​
Property/Type

  • “Find all objects set to Static”
  • “Do I have multiple cameras tagged MainCam?”
  • “List all food prefabs”

​
Dependencies

  • “What tile palettes were used to build this level?”
  • “Return all scripts that instantiate Prey prefabs”
  • “Which animation clips does my character movement system actually use?”

​
Efficiency

  • “List all 4K textures”
  • “What models do I actually use across my scenes?”
  • “Models that are too high poly to run on mobile”

​
Learn

Get concise, thorough project- and documentation-rooted answers. When you’re struggling to understand a Unity intricacy, walking through an unfamiliar script, or working with a new plugin, the sheer volume of info to wade through can be overwhelming and tough to extrapolate. Bezi combines its deep knowledge of your project with Unity docs, ReadMes, and other web resources to give detailed explanations. Before spending hours in the rabbit hole that is Stack, Reddit, and uncommented code, try using Bezi to synthesize relevant info.

​
Unity info

  • “What’s the difference between a MeshRenderer and a SkinnedMeshRenderer?”
  • “What are the main differences between Unity 6 and Unity 2022?”
  • “Teach me about the core tabs of the Lighting window— specifically, what are Adaptive Probe Volumes?”

​
Packages

  • “Explain the key features of the PortalsForVR package”
  • “Best packages for stylized water (provide Pros, Cons, and recommendations)”
  • “How can I set up my project for Passthrough with MetaXR?”

​
How-tos

  • “How do you use set up custom sprites to use with a TileMap?”
  • “Tutorial for making an inventory system for a desktop exploration game”
  • “How do you use the Profiler?”

​
Existing assets

  • “Walk me through PlayerInteraction.cs”
  • “How does the multiplayer system in this game work?”
  • “What are the controls for this game? List what mechanics there are, and explain how to use each to test.”

​
Code

Generate and iterate on scripts. Direct-from-Unity context enables Bezi to make suggestions in full awareness of your entire project, so responses can avoid pitfalls like redundancies, repetition, and inconsistency.

Bezi can help you ‘mass in’ the core fundamentals, so you can focus on the bespoke mechanics; it can help you mock up those mechanics when you aren’t sure how to approach them; and it can simplify small busy work, turning thirty minutes of endless scrolling, copy/pasting, editing, and testing into thirty seconds.

​
Foundational systems:

  • “Make a first person character controller with mouse-based camera movement”
  • “Mock up object pooling for the obstacles and set up the basic obstacle ‘spawning’ and movement system (right to left)”

​
Experimental whitebox mechs:

  • “Prototype a ghost possession mechanic that lets the player take and relinquish control of other characters when in range and spacebar is pressed”
  • “I want a camera system that moves to a fixed CameraLocation when they enter a collider tagged FixedCam, then lerps back to third person when out— what would that code look like?”

​
Adjustments and additions:

  • “Add crouch and jump behavior to the player movement script”
  • “Instead of using a Raycast to detect treasure, can we use a collider on the @Hunter?”
  • “Incorporate the isFalling, isFlying, and isMoving animation bools from @Sarah.controller into CharacterControls.cs”

​
Debug

Troubleshoot errors, whether they’re lighting up the console or glitching out your gameplay. Bezi is backed by scripting expertise, Unity docs, and all indexed contents of your project, so it can decipher and diagnose Console Error gibberish; pinpoint the components and/or scripts behind unexpected behaviors; and expose sources of lag so you can better ID and correct slow-downs.

​
Console errors

  • “What’s up with that NullReference exception?”
  • “How do you fix ‘We can’t assign a new GUID because the asset is in an immutable folder. The asset will be ignored.’?”
  • “I made this shader but now I’m getting this endless loop of errors— why?”

​
Behavioral issues

  • “When I press play, the whole sky turns red. Is it the cloud render feature?”
  • “My character vibrates and hops when stationary on a slanted surface”
  • “Why does the portal gun not work in the Entry scene?”

​
Optimization

  • “Every time the player enters the Dungeon level, the framerate plummets. Why?”
  • “How can I optimize the searching part of Seeker.cs?”
  • “Optimize my project for mobile”

Simplify the process of hunting through assets, scenes, and scripts— no parameter is too specific. Bezi understands the contents of your project, the objects in your scene, and the properties on your assets, so it’s equipped to help you parse through it all to find what you need. Ask Bezi to find the little details that could take endless time to recover (like, “where is this method called?” and “what objects have this box checked?”).

Currently, Bezi’s context does not dive into node graphs/state machines/visual scripting, so while Bezi will know that they’re there, it can’t see how such objects as animators and shader graphs are set up.

​
Property/Type

  • “Find all objects set to Static”
  • “Do I have multiple cameras tagged MainCam?”
  • “List all food prefabs”

​
Dependencies

  • “What tile palettes were used to build this level?”
  • “Return all scripts that instantiate Prey prefabs”
  • “Which animation clips does my character movement system actually use?”

​
Efficiency

  • “List all 4K textures”
  • “What models do I actually use across my scenes?”
  • “Models that are too high poly to run on mobile”

​
Learn

Get concise, thorough project- and documentation-rooted answers. When you’re struggling to understand a Unity intricacy, walking through an unfamiliar script, or working with a new plugin, the sheer volume of info to wade through can be overwhelming and tough to extrapolate. Bezi combines its deep knowledge of your project with Unity docs, ReadMes, and other web resources to give detailed explanations. Before spending hours in the rabbit hole that is Stack, Reddit, and uncommented code, try using Bezi to synthesize relevant info.

​
Unity info

  • “What’s the difference between a MeshRenderer and a SkinnedMeshRenderer?”
  • “What are the main differences between Unity 6 and Unity 2022?”
  • “Teach me about the core tabs of the Lighting window— specifically, what are Adaptive Probe Volumes?”

​
Packages

  • “Explain the key features of the PortalsForVR package”
  • “Best packages for stylized water (provide Pros, Cons, and recommendations)”
  • “How can I set up my project for Passthrough with MetaXR?”

​
How-tos

  • “How do you use set up custom sprites to use with a TileMap?”
  • “Tutorial for making an inventory system for a desktop exploration game”
  • “How do you use the Profiler?”

​
Existing assets

  • “Walk me through PlayerInteraction.cs”
  • “How does the multiplayer system in this game work?”
  • “What are the controls for this game? List what mechanics there are, and explain how to use each to test.”