Verse: false errors on Await() for events in Visual Studio Code
In 43.00, Visual Studio Code may show errors when you call Await() on an event or a listenable, for example Interactable.SucceededEvent.Await(). You may see:
- Unknown member Await in listenable(agent)
- Invalid access of internal function (/Verse.org/Verse/event:)Await
- All the top level expressions in a ‘race’ macro must be async
- We’re investigating now
The VS Code Verse extension shows incorrect errors when you call Await() on an event or listenable, for example Interactable.SucceededEvent.Await(). Errors include Unknown member Await in listenable(agent) and Invalid access of internal function (/Verse.org/Verse/event:)Await. Your Verse code still compiles and runs correctly in UEFN, so these errors can be ignored.
Widget Blueprints: adding an Event variable causes compile errors
In 43.00, adding a Verse Event variable to a Widget Blueprint causes the widget to fail to compile, and the event can’t be used from Verse. Widget Blueprints created before 43.00 that already have Event variables still compile.
Workarounds:
- Top-level widget: after adding the Event variable, reload the asset (right-click it in the Content Browser and select Reload) or restart UEFN.*
- Child widgets: add the Event variables to the parent widget instead.*
- We’re working on a fix.