Where Does REFramework Store Config and Mods?
REFramework lives in the game folder as dinput8.dll plus a reframework directory for autorun scripts, plugins, and config.
Last updated
REFramework installs per game with a tiny footprint: one DLL beside the executable and one folder for everything else. The dinput8.dll hooks the game at launch, then the reframework folder supplies autorun Lua scripts, native plugins, and data files. Logs and crash dumps land beside them for bug reports.
Placement is the entire installation manual. The DLL must sit next to the game's exe, using the per-game build from the releases page. Linux and Deck setups add a Proton DLL override so the custom library loads instead of the system one.
Where RE Framework stores this, by platform
[GameFolder]\reframework\autorun
Lua scripts here load automatically; plugin DLLs go in the plugins sibling. The framework generates the tree on first run, so create autorun manually when adding scripts early.
[GameFolder]\re_framework_config.txt
Menu key and options in re_framework_config.txt; crash logs (re2_framework_log.txt, reframework_crash.dmp) beside it. Proton setups need WINEDLLOVERRIDES so the custom dinput8 loads.
Frequently asked questions
The REFramework menu never appears. What is wrong?
Place dinput8.dll (plus the reframework folder when included) directly beside the game's main exe. The menu fails to appear in nearly every case because the DLL landed in a subfolder instead.
How do I change the menu key or add scripts?
Check re_framework_config.txt in the game folder for the menu key binding. Lua scripts go in reframework/autorun and plugin DLLs in reframework/plugins; both load automatically at startup.
Notice an outdated path? Let us know.