-
Notifications
You must be signed in to change notification settings - Fork 38
9.2 Known Issues
Chris edited this page Jul 30, 2026
·
3 revisions
I'll add a list of issues I'm aware of here, Some may be fixed in future. Some of them may not be able to be fixed
- No support for omod type files, These are very rare and often converted to fomod, They contain c# scripts that we can't parse
- No support for c# type fomods, Same as above
- Adding a custom game can be quite confusing, This system was designed to be very flexible by providing a lot of options and settings and as a result is hard to document via text/wiki
- Flathub release, Not worth my time
- Importing from other managers, Despite using a similar file and folder format to mo2, there are some subtle differences that would make it fairly janky
- Wabbajack support, It's out of scope for this project and is much more complex than Nexus collections
- Payday 2 may not work until SuperBLT is updated to support the 64bit update
- Symlinks do not work for games installed via heroic flatpak unless it is given permission to access the game's staging folder (Newest versions of the manager will grant it access automatically)
- Community shaders upscaling (Current version) is currently broken when running the game with proton 11
- Some mods may not work with some Proton 11 versions (Community shaders upscaling is one example)
- Cyber engine tweaks (For Cyberpunk) only works when hardlinked
Getting started
Managing mods
- Installing a mod
- Mod Files Tab
- Updating a Mod
- Installing a collection
- Creating and uploading a collection
- Installing VNV and TTW
- Mods not working
- Profile Specific Saves
Load order and conflicts
Deploying and playing
Tools and advanced
Reference