Bolt's migration into Visual Scripting error

[bohemian pulp]

Hello, I migrated from Bolt to, how Unity now calls it, Visual Scripting and got this error:

Assets\Pixel Crushers\Dialogue System\Third Party Support\Bolt Support\DialogueSystemBoltCustomEvents.cs(19,13): error CS0103: The name 'Bolt' does not exist in the current context

Is there an easy fix? Or should I backtrack?

[Tony Li]

I wasn't aware that Unity had rebranded Bolt as Visual Scripting. Where I can find the new Visual Scripting package?

[bohemian pulp]

Sorry for the super-late reply. I forgot I asked this so much that I googled out my own question
The visual scripting is now under Package Manager > Unity Registry > Visual Scripting
Everything works perfectly except the BoltEvent() conversation Script. Generally, Third Party Support>Bolt Support creates compile errors.

EDIT:
I figured out the new Events>Scene Event thing, so it pretty much fixes everything.

[Tony Li]

Updates to the new Visual Scripting package are on the roadmap. If you notice any other issues or have any feature suggestions, just let me know.

[bohemian pulp]

Sure! But with the Scene Event option, I guess it's not very urgent, it should cover it.