Skip to content

Troubleshooting

Joël Deffner edited this page Oct 6, 2026 · 4 revisions

Troubleshooting

The server cannot be found

Check that px-lsp is beside PxToolkit.dll and that the complete release archive was extracted. If a custom launcher is configured, check its path. The release already contains Node.

The DLL does not load

Check that the package matches the architecture of Notepad++, not just Windows. The DLL must be named PxToolkit.dll inside a folder named PxToolkit. Close all instances of the target editor before replacing the files. Under Wine, check that your Wine distribution can run that editor architecture and the included Windows Node runtime. See Installation.

A file has no language features

Check that the file belongs to a recognized mod and has a supported extension and folder location. See Installation. Convert non-ASCII text to UTF-8, confirm the selected game and paths, and allow indexing to finish.

The Problems panel contains diagnostics reported by the server. No rows does not establish that every file in the mod has been checked.

If vanilla definitions are missing, set Game data folder to the game's game subfolder. A blank value disables vanilla file indexing; it does not find installed games. Script docs folder is separate: a blank value uses the bundled documentation for the selected game.

A preview cannot be applied

A target may have changed, become read-only, closed, or moved to a different document version. A file to be created may now exist. Resolve the reported condition and request a fresh preview. The plugin rejects edits outside the active mod and unsupported resource operations.

An unversioned documentChanges edit can require a saved target. Follow the panel message, save that target, and request the fix again.

Completion disappears after movement

In plugin version 0.2.2, old completion responses are discarded when the document, caret, or server session changes. Request completion again at the desired position. The old range is not extended across intervening text.

The server stopped or reported an error

Choose Show server log from the plugin menu. After resolving the cause, choose Restart server. For released 0.2.0, save inactive mod tabs before restarting, or activate them again after restart so that their unsaved contents reach the server.

Plugin version 0.2.2 contains pipe-write cancellation and bounded message queues. A server that stops reading can no longer hold the editor inside a pipe write. A full queue or malformed frame ends the server session and produces a log message. Malformed JSON messages or feature payloads are contained at dispatch and reported through the same log.

These fixes are included in plugin version 0.2.2. They do not change the behavior of an installed 0.2.0 archive.

Orange lines or changing colors after an edit

Plugin version 0.2.2 corrects the folding margin that caused unsaved-change markers to color whole lines orange. It also retains semantic colors on unchanged tokens while waiting for a fresh server response. These fixes require the new plugin DLL; updating only the server cannot fix an installed 0.2.0 DLL.

An LSP update failed

Read %LOCALAPPDATA%\PxToolkit\servers\<arch>\update.log, where <arch> is x86, x64, or arm64. Version 0.2.0 used servers\update.log without an architecture subfolder. A failed or offline check leaves the previous server available. A matching server archive must exist for the plugin architecture. If upstream has no x86 or ARM64 archive, keep using the bundled server and update it with a plugin package. A custom launcher has no managed updates. Under Wine, disable automatic checks if Windows PowerShell is unavailable and install plugin packages manually.

Reporting a problem

Use the repository's bug report form. Include the plugin, LSP, and Notepad++ versions and architecture; Windows version, or host OS and Wine distribution/version; game; file type; exact reproduction steps; and relevant log messages. State whether the file had unsaved edits, whether another mod was open, and whether restart or a caret movement was involved. Attach a small reproducible mod fragment when possible. Remove private paths or file contents that are not needed to reproduce the issue.

This plugin receives limited maintenance. Regular feature development is not planned; reported issues may be fixed when time permits. PX Toolkit for VS Code has priority. See Support. Report vulnerabilities through the security policy, without posting exploit details in a public issue.

Results are hidden at the bottom of the panel

Drag the panel's upper divider upward to give the result list more space, especially when Windows display scaling is enabled. The panel remembers its docked size through Notepad++.