Verse Language Server disconnects when running a Verse script

Development Programming & Scripting Verse
, , , ,
1

Verse Language Server disconnects when running a Verse script

Hi,

I’m having an issue with the Verse extension. Whenever I run a Verse script, I get the following error in VS Code:

[Error - 2:25:03 PM] Connection to server is erroring. Shutting down server.

Screenshot 2026-07-04 144335
Screenshot 2026-07-04 1443351884×119 4.42 KB

After this happens, the Verse extension stops working completely (no syntax highlighting, autocomplete, or other language features).

Has anyone experienced this issue before or knows how to fix it?

Thanks!

2

That error is the Verse language server dying when UEFN compiles. VS Code then drops highlighting and IntelliSense until you restart the server. Common, not a bad script.

Do this in order:

  1. In VS Code: Command Palette → Verse: Restart Language Server (or Developer: Reload Window).
  2. Close extra VS Code windows. One window on the UEFN project is enough. Two instances fighting over the same .verse digest will crash the LS.
  3. Don’t “Run” the Verse file from VS Code. Compile / Push Changes from UEFN. The LS is not a runtime.
  4. If it still dies on every compile: quit UEFN and VS Code, delete the local Verse cache under your project (Binaries, .vs, and the generated *.digest.verse is fine — it comes back on compile), start UEFN first, then open the project in VS Code.
  5. Update the official Verse extension. An old LS against a new UEFN build is a frequent cause of Connection to server is erroring.

If it only happens on one device: look at the Verse output panel for the line before the shutdown. A parse error in a huge module, or a path with non-ASCII characters, will take the LS down with it. Fix that file and the disconnects stop.