Bezi’s foundation of scripting expertise, Unity docs, and all indexed contents of your project makes it very effective for sifting through projects to find causes and identify viable solutions for tricky bugs. Let Bezi search so you can work on other stuff. Prompt it to decipher and diagnose Console Error gibberish; pinpoint the components and/or scripts behind unexpected behaviors; and expose sources of lag so you can ID and correct slow-downs faster.

​
Example prompts

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”