Guide contents
Do not delete everything first. Confirm the current loader and Mod requirements, compare the platform path, read the log, and remove one recent change at a time.
This page keeps platform, version, dependency, and source boundaries visible so a safe test has a clear result.
Follow the smallest useful path.
Check version and requirements
Compare the current loader and Mod requirements with the official or original source.
The version caveat and dependency list are recorded before cleanup.
Inspect path and log
Check the platform-specific path, UE4SS.log, and obvious leftover loader files.
You have one concrete error or missing signal rather than a broad guess.
Rollback one change
Remove the newest Mod or confirmed leftover, then launch again.
The symptom changes or the clean baseline returns, identifying the next branch.
Use the symptom to choose the next check.
| Symptom | Check | Recovery |
|---|---|---|
| A clean launch works but the Mod does not. | Re-add only the Mod and its named dependency after checking the platform route. | Keep the failing item isolated and use its original page for the next check. |
| The log contains old-loader files. | Compare the file names with the current loader material. | Remove confirmed leftovers one at a time and keep a rollback copy. EvidenceANeeds source review |
Questions this source set can answer.
Should I uninstall the whole game?
Not as the first step. The research notes that uninstalling the game may not remove Mods, so isolate the loader and Mod changes first.
How many Mods should I test at once?
One change at a time keeps the failure signal attributable and makes rollback safer.
If the current source disagrees with an older tutorial, pause the change and re-check the release, platform, and original Mod page before continuing.