Hi Epic team—first, thank you for Unreal Engine. Blueprints feel intuitive and make learning joyful. When I switch to C++, the flow breaks: I jump to an external IDE, editor responsiveness can suffer, and sometimes I have to restart or reconnect pieces before I can iterate again. Live Coding helps, but the context-switch is still a barrier for many learners moving from Blueprints to code.
My request is a single-window workflow: a Blueprint ↔ Code toggle inside the Blueprint editor, plus a Simple Script mode—a beginner-friendly text language that feels like Blueprints (clear types, small syntax, instant feedback). The Code view would be a docked tab with autocomplete, go-to, inline errors, and an Apply/Hot-Reload button. Errors should jump both to the exact line in text and the Blueprint node that called it. Add two explicit bridges without mentioning specific languages: from a Blueprint function or event, generate a matching Simple Script function; from a Simple Script function marked for exposure, auto-create the Blueprint node. No full round-trip conversion—just clean, intentional bridges.
This keeps Blueprints first-class, lowers the on-ramp to text scripting, and reduces context switching so teams iterate faster.