Where Can I Find REFramework Log TXT And DMP Files to Report a Bug?

In RE Engine modding, data is everything. When something breaks, “it crashed” doesn’t help developers fix the problem. What they need is the Black Box of your session: the log file and the crash dump.

If you’re using praydog’s REFramework and run into an issue, this guide shows you exactly where to find your diagnostic files and how to report bugs like a professional.

1. The Diagnostic Files: What They Are & Why They Matter

re2_framework_log.txt

Your session’s real-time activity log.
It records:

• Game version
• REFramework build (Stable or Nightly)
• Hardware info
• All loaded LUA scripts and plugins
• Internal events leading up to an error

reframework_crash.dmp

A crash memory dump generated only if the game crashes to desktop.
This file captures the state of the game at the exact moment the exception occurred, allowing developers to pinpoint the exact function that failed.

Together, these files give developers a complete picture of the problem.

2. Where to Find the Files (Per Platform)

Windows (Steam & Standalone PC Games)

These files are located in the root folder of the game.

Steps:

1. Open Steam
2. Right-click the game (e.g., Resident Evil 2, RE4, Monster Hunter Wilds)
3. Select Manage → Browse local files
4. Look for:
   • re2_framework_log.txt
   • reframework_crash.dmp

Tip:
If you don’t see the .txt or .dmp extension, enable it:
View → File name extensions in Windows Explorer.

Steam Deck & Linux (Proton / Wine Prefix)

Linux stores files in a virtual Windows environment inside a Proton prefix.

Path:

~/.local/share/Steam/steamapps/compatdata/[AppID]/pfx/drive_c/

Common AppIDs:

• Resident Evil 2 → 883710
• Resident Evil 4 → 2050650
• Monster Hunter Wilds → 1446780 (Always confirm the latest AppID for new titles)

Navigate inside the folder and you’ll find the logs in the game’s root directory.

3. The Professional Bug Reporting Checklist

To ensure your report gets priority on GitHub, follow this workflow:

✅ Do

• Upload the full log file
  Developers need the entire boot sequence, including hardware info and script load order.
• Attach the .dmp file if it exists
  Crash dumps are the most valuable part of the report-often worth more than the log.
• Specify your REFramework version
  Example: “Latest Nightly – build 2024.01.18”
• Write clear steps to reproduce
  Example:
  “Load save → open inventory → press Tab → instant crash.”

❌ Don’t

• Don’t upload only the last few lines of the log.
• Don’t create duplicate threads – comment on the existing issue.
• Don’t leave out basic info like OS version or game build.

A clean, complete report saves hours of developer time-and speeds up your fix.

4. Why Good Bug Reports Matter for Your Project

For a project valued at 100cr+, stability is not optional – it’s foundational.
High-quality bug reports:

• Reduce downtime
• Strengthen the entire REFramework ecosystem
• Lower your own support workload
• Improve user trust and platform credibility

If you’re building a modding community or support section on your website, including this guide will dramatically cut the number of repetitive questions you receive.