docs: add drm alert before debugging a newly created mod project

[Nenkai]

Had this figured for a while but figured it wasn't exactly documented behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 35755860-734e-49bd-ae1a-414be4ab9556

📥 Commits

Reviewing files that changed from the base of the PR and between 2014272 and f9956b8.

📒 Files selected for processing (1)

• docs/ProjectSetup.md

---

Walkthrough

A warning admonition block is added to the "Debugging Your Mod" section of docs/ProjectSetup.md. The warning states that some games using Steam DRM may not trigger breakpoints after attaching a debugger, and describes a workaround: unpack the executable (e.g., using Steamless) and configure the application in Reloaded-II to point to the unpacked executable.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the new DRM warning added to the debugging docs.
Description check	✅ Passed	The description is brief but still related to documenting the DRM/debugger behavior.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Sewer56]

Correct.

Has been an annoyance of mine for a while too- I even have a special code path in the loader (as you may have noticed) for handling this DRM, since game is encrypted at boot.

(It mass hooks Windows functions then loads when one is called)

In any case, I would suggest replacing original executable for simplicity instead, instructions wise.

I once considered bundling Steamless but the license (at the time) has not allowed it. That has however since changed IIRC.

[Sewer56]

Also thinking about it.

The games which use this DRM have a console message attached to them when the .bind section is enabled. So you can tell in the Reloaded logs.

So maybe make a subsection, and mention this in a troubleshooting section. A copy of the console message may be helpful to attach.