Repository navigation
Troubleshooting
Common issues and solutions for Verse Auto Imports.
- Extension Not Working
- Wrong Imports Being Suggested
- Path Conversion Issues
- Cache Issues
- Viewing Logs
- Getting Help
If the extension doesn't seem to be doing anything:
Ensure you're working with .verse files. The extension only activates for Verse language files.
Make sure Verse language support is enabled in VS Code. You should see "Verse" in the bottom-right language indicator when editing a .verse file.
View extension logs for error messages:
- Open
View>Output - Select
Verse Auto Importsfrom the dropdown (shows important messages) - Or select
Verse Auto Imports - Debugfor detailed debug logs
Look for "Verse Auto Imports" in the VS Code status bar (bottom). Click it to open the Status Bar Menu and verify the extension is enabled.
Try reloading VS Code:
- Press
Ctrl+Shift+P - Type "Reload Window"
- Press Enter
Open the status bar menu and look at the Auto Import row. Snoozed (M:SS) means a snooze is counting down and will end on its own, or immediately if you reload the window.
If the row reads as off entirely, check verseAutoImports.general.autoImport in your user settings. Versions before 0.9.0 wrote that setting to false when you snoozed, and a reload or crash during the snooze could leave it off permanently. Re-enable Auto Import from the status bar menu once and it will stay on — the snooze no longer touches your settings.
If the extension suggests incorrect imports:
For classes that exist in multiple modules, specify your preferred module:
{
"verseAutoImports.behavior.ambiguousImports": {
"vector3": "/UnrealEngine.com/Temporary/SpatialMath",
"vector2": "/UnrealEngine.com/Temporary/SpatialMath",
"rotation": "/UnrealEngine.com/Temporary/SpatialMath"
}
}If auto-import picks the wrong option, switch to manual quick fix mode:
{
"verseAutoImports.general.autoImport": false
}Then use Ctrl+. on errors to manually choose the correct import.
Change how the extension handles multiple import options:
{
"verseAutoImports.behavior.multiOptionStrategy": "quickfix"
}Options:
-
"quickfix"- Always show a menu to choose (recommended) -
"auto_shortest"- Auto-select the shortest path -
"auto_first"- Auto-select the first option -
"disabled"- Don't handle multi-option scenarios
How conversion resolves modules is described on the Path Conversion page.
If "Use absolute path" doesn't find your module:
- Ensure the module exists in your project's
Content/folder - Check that your
.uefnprojectfile is properly configured
If the path conversion options don't appear:
- Check that CodeLens is enabled:
{
"verseAutoImports.pathConversion.enableCodeLens": true
}- Try setting visibility to "always":
{
"verseAutoImports.pathConversion.codeLensVisibility": "always"
}What the cache holds and how it invalidates is described on the Path Tree Caching page.
If import suggestions seem outdated:
-
Rebuild the cache manually:
- Press
Ctrl+Shift+P - Search for "Verse Auto Imports: Rebuild Project Path Cache"
- Wait for the rebuild to complete
- Press
-
Check cache status:
- Press
Ctrl+Shift+P - Search for "Verse Auto Imports: Show Cache Status"
- Verify the cache is up to date
- Press
-
Start cold if the cache looks corrupt:
- Press
Ctrl+Shift+P - Search for "Verse Auto Imports: Clear Project Path Cache"
- This wipes both the in-memory cache and its persisted copy without rebuilding, so the next lookup starts from scratch
- Press
If changes to .verse files aren't reflected:
- Check that caching is enabled:
{
"verseAutoImports.cache.enableProjectCache": true
}- Try adjusting the watcher debounce delay:
{
"verseAutoImports.cache.watcherDebounceMs": 1000
}- Manually rebuild the cache as described above
If VS Code starts slowly:
- Disable auto-rebuild on startup:
{
"verseAutoImports.cache.autoRebuildOnStartup": false
}The cache will use persisted data from the previous session and update incrementally as you work.
The extension provides two output channels for debugging:
Shows INFO, WARN, and ERROR level messages:
-
View>Output - Select
Verse Auto Imports
Shows all messages including TRACE and DEBUG:
-
View>Output - Select
Verse Auto Imports - Debug
To share logs when reporting issues:
- Click "Verse Auto Imports" in the status bar
- Go to
Utilities - Click
Export Debug Logs
When a command fails — a toggle, either debug-capture command, or Rebuild Path Cache — the failure is recorded in the log, so an export taken after the problem holds the failure you are reporting.
Still having issues?
- GitHub Issues: Report a bug
- Discord: Ask questions
When reporting issues, please include:
- VS Code version
- Extension version
- Relevant log output
- Steps to reproduce the problem
Install from the Marketplace · Report an issue · Discord · Changelog
Verse Auto Imports is an independent extension by VukeFN. Not affiliated with or endorsed by Epic Games. Verse, UEFN and Fortnite are trademarks of Epic Games, Inc.
How it works
Reference
Help