Nebula includes a file browser that opens directly inside the launcher, giving you a way to inspect the FusionCore and BepInEx directory tree without switching to a separate file manager app. Because mod problems often reveal themselves through log files and configuration values, being able to read and edit those files in-place saves considerable back-and-forth during debugging.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Nebula-Modmakers/Nebula-Launcher/llms.txt
Use this file to discover all available pages before exploring further.
Opening the file browser
Tap Browse Files on the Nebula main screen. The browser opens at the root of the shared FusionCore/Nebula storage directory — the same location that holds the BepInEx runtime, plugin folders, configuration files, and logs for Among Us.What you can do
Navigate the directory tree
Tap any folder in the list to enter it. Tap the Up button in the toolbar to move to the parent directory. Navigation stops at the shared storage root — you cannot browse above it.
Open supported files for editing
Tap a file to attempt to open it. If the file type is not supported, a message appears. If the file is within the 256 KB size limit and has a supported extension, the built-in editor opens immediately.
Edit supported text files
Tap a supported text file (
.cfg, .txt, .log, .ini, .json, .xml, .yml, .yaml, .csv, .config) to open it in the built-in editor. Make your changes, then tap Save to write them back to disk.Refresh the current directory
Tap Refresh to reload the current folder listing. Useful after a launch that may have written new files or after a log rotation.
Limitations
The file browser is designed for inspection and lightweight editing, not general file management. Keep these constraints in mind:- Supported file types only. The editor accepts
.cfg,.config,.ini,.json,.log,.txt,.xml,.yml,.yaml, and.csvfiles, plus the special filesdoorstop_config.iniandlast_error.txt. Tapping any other file type shows the message: “This file type is not editable in the built-in browser yet.” - Size limit. Files larger than 256 KB cannot be opened in the editor. Tapping an oversized file shows the message: “This file is too large for the built-in editor.” Large log files fall into this category once they accumulate enough output.
- No file management operations. The browser cannot move, rename, copy, or delete arbitrary files. It can only read and write the content of files that are already present.
Common uses
Read the latest BepInEx log
Navigate to
BepInEx/LogOutput.log inside the FusionCore shared directory. This file records every plugin load attempt, BepInEx startup message, and runtime error. It is the first place to check when a mod does not load or causes a crash.Inspect plugin installation results
Browse the
BepInEx/plugins/ folder to confirm that your expected .dll files are present after installing or importing a mod. Missing files here explain why a mod does not appear in-game.View or tweak BepInEx config files
Open
.cfg files under BepInEx/config/ to review or adjust per-mod configuration values without leaving Nebula. Save changes before your next launch so they take effect immediately.Check the Nebula runtime marker file
The file
.nebula-runtime.sha256 inside the BepInEx directory records the SHA-256 fingerprint of the currently installed runtime bundle. Nebula compares this value at launch to decide whether to re-extract the runtime. Viewing it confirms which runtime version is active.