Troubleshooting Guide
Having trouble? This guide covers the most common issues and their solutions.
Installation Issues
Plugin not appearing in Plugins list
Symptoms: After extracting the plugin, it doesn’t show in Edit → Plugins.
Solutions:
-
Verify folder structure
The plugin folder should be directly inside
Plugins/:YourProject/└── Plugins/└── PluginName/ ✓ Correct├── PluginName.uplugin└── Source/Not nested:
YourProject/└── Plugins/└── PluginName-3.2.0/ ✗ Wrong - extra folder level└── PluginName/ -
Check .uplugin file exists
Look for
PluginName.upluginin the plugin root folder. -
Restart Unreal Editor
A full restart (not just reload) is required.
-
Regenerate project files
Right-click your
.uprojectfile → Generate Visual Studio/Xcode Files
”Module ‘PluginName’ not found” error
Cause: The plugin module failed to load.
Solutions:
-
Check Unreal version compatibility
Download the correct version for your UE version from your Dashboard.
-
Check binaries exist
Look in
Plugins/PluginName/Binaries/[Platform]/If empty, you may have downloaded source-only (Ultimate) without building.
-
Check Output Log
Window → Developer Tools → Output Log
Search for the plugin name to find specific error messages.
-
Delete intermediate files
Delete these folders and restart:
Intermediate/Binaries/DerivedDataCache/
Plugin causing Editor to crash on startup
-
Start without plugins
Rename the plugin folder temporarily and start the Editor.
-
Check crash logs
- Windows:
%LOCALAPPDATA%/UnrealEngine/5.x/Saved/Crashes/ - macOS:
~/Library/Logs/Unreal Engine/
- Windows:
-
Verify dependencies
Some plugins require other plugins to be enabled first.
-
Clean rebuild
Delete Binaries, Intermediate, and regenerate project files.
License Issues
”Invalid license key” error
Verify the key format:
- Should be
GDNA-XXXX-XXXX-XXXX - Check for extra spaces before/after
- Ensure no characters were missed when copying
Copy fresh from Dashboard:
- Go to Dashboard → Licenses
- Click the copy button (not manual selection)
- Paste directly into Unreal
”All seats in use” error
Cause: Your license has reached its activation limit.
Solution:
- Go to Dashboard → Licenses
- Click “Manage Activations” on your license
- Find the old machine and click “Deactivate”
- Try activating again on the new machine
Contact support@gamedna.studio to request a seat transfer.
”License expired” error
Your update period has ended. You have two options:
- Continue using current version - It will work forever
- Renew for updates - Go to Dashboard → Licenses → Renew
Activation fails with “Network error”
-
Check internet connection
Activation requires internet access.
-
Check firewall/proxy
Allow connections to
store.gamedna.studioandapi.gamedna.studio -
Try offline activation
See Licensing Guide
-
Check Unreal’s network settings
Edit → Editor Preferences → General → Network
Plugin-Specific Issues
Online Subsystem Blueprintable
”Online Subsystem not initialized”
-
Check DefaultEngine.ini
Ensure you have:
[OnlineSubsystem]DefaultPlatformService=Steam ; or EOS, etc. -
Enable platform plugin
Edit → Plugins → Enable “Online Subsystem Steam” (or your platform)
-
Steam-specific
- Ensure Steam client is running
- Check
steam_appid.txtexists with correct ID
-
EOS-specific
- Verify all credentials in DefaultEngine.ini
- Check deployment is published in EOS portal
”Login failed: User cancelled”
This usually means the platform overlay closed without completing login.
Steam: Ensure the user is logged into Steam client.
EOS: Check that login method is enabled in your EOS portal.
Discord Messenger
”Webhook URL invalid”
- URL must start with
https://discord.com/api/webhooks/ - Check for extra characters or missing parts
- Create a new webhook if the old one was deleted
”Bot token unauthorized”
-
Regenerate token
Discord Developer Portal → Your App → Bot → Reset Token
-
Check intents
Enable required intents in Bot settings
-
Verify bot is in server
Re-invite the bot using OAuth2 URL Generator
Analytics Toolkit
Events not appearing in dashboard
-
Check backend credentials
Verify API keys in Project Settings
-
Enable debug logging
Project Settings → Analytics Toolkit → Enable Debug Logging
Check Output Log for errors
-
Check batching
Events are batched. Wait for batch interval or call Flush.
-
Check consent
If GDPR mode is enabled, ensure user has consented.
Build & Packaging Issues
Plugin works in Editor but not in packaged build
-
Check plugin is set to package
In .uplugin file, ensure:
{"Installed": true} -
Add to packaging settings
Project Settings → Packaging → Additional Asset Directories to Cook
Add the plugin’s Content folder if it has assets.
-
Check platform whitelist
Some plugins have platform restrictions in their .uplugin.
”Missing module: PluginName” in packaged game
-
Verify build configuration
Package with the same configuration (Development/Shipping) you tested.
-
Check plugin dependencies
Ensure all required plugins are also packaged.
-
Review packaging log
Check
Saved/Logs/for packaging errors.
Compile errors after engine upgrade
When upgrading Unreal versions:
-
Download matching plugin version
Get the version compatible with your new UE version from Dashboard.
-
Delete old plugin folder
Remove the old version completely before extracting new.
-
Regenerate project files
Right-click .uproject → Generate Project Files
-
Clean rebuild
Delete Intermediate and Binaries folders.
Performance Issues
Plugin causing frame drops
-
Profile with Unreal Insights
Look for plugin-related hitches.
-
Check async settings
Ensure async operations aren’t blocking the game thread.
-
Reduce call frequency
Cache results instead of calling every frame.
-
Contact support
If persistent, report with profiling data.
High memory usage
-
Check for leaks
Use Unreal’s Memory Profiler.
-
Review object lifecycle
Ensure you’re not creating objects without cleanup.
-
Check plugin settings
Some plugins have memory-related options.
Getting More Help
Before contacting support
Gather this information:
- Unreal Engine version (exact, e.g., 5.4.2)
- Plugin version (from Dashboard)
- Platform (Windows, Mac, Linux)
- Full error message (screenshot or copy)
- Output Log contents (filtered to the plugin name)
- Steps to reproduce
Contact options
| Issue Type | Best Channel |
|---|---|
| Quick questions | Discord #support |
| Detailed bugs | Email: support@gamedna.studio |
| License issues | Email: support@gamedna.studio |
| Feature requests | Discord #suggestions |
| Security issues | Email: security@gamedna.studio |
Debug information
To help support diagnose issues faster:
In DefaultEngine.ini:
[Core.Log]LogOnline=VerboseLogPluginName=Verbose- Window → Developer Tools → Output Log
- Right-click → Save to File
- Attach to support request