[PR #263] [MERGED] docs: analysing your own DRM-wrapped executable is fine; unpacking how-tos are not #263

New issue

Closed

opened 2026-10-15 20:54:56 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 20:54:56 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/rehan-remade/universal-modder/pull/263
Author: @rehan-remade
Created: 10/12/2026
Status: ✅ Merged
Merged: 10/12/2026
Merged by: @rehan-remade

Base: main ← Head: docs/drm-analysis-rule

📝 Commits (1)

c0cd251 docs: analysing your own DRM-wrapped executable is fine; unpacking how-tos are not

📊 Changes

4 files changed (+17 additions, -0 deletions)

View changed files

📝 .agents/skills/mod-any-game/references/safety.md (+4 -0)
📝 .claude/skills/mod-any-game/references/safety.md (+4 -0)
📝 CONTRIBUTING.md (+5 -0)
📝 skills/mod-any-game/references/safety.md (+4 -0)

📄 Description

Reviews drew this line inconsistently: strict for Limbo (#146, #192), while the merged Dark Souls notes (#147, #249) and the #194 review allowed analysis of a self-made dump. This writes down one rule.

CONTRIBUTING.md, hard rules: analysing your own legally installed copy of a DRM-wrapped exe (Steam stub, Arxan, Denuvo, iOS FairPlay) is fine, from the running game's memory or a private dump kept outside any repository, and so is writing up what you learned in your own words. A note never explains how to strip or unpack the protection, never links an unpacked executable or a DRM-removal tool, and never gives steps whose result is the game running without its DRM.
safety.md: the same for agents. Never write an unpacked exe into the game folder, run it or share it.

The parts that draw takedowns (unpacking how-tos, unpacked binaries, removal tools) stay out; the knowledge stays in.

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/rehan-remade/universal-modder/pull/263 **Author:** [@rehan-remade](https://github.com/rehan-remade) **Created:** 10/12/2026 **Status:** ✅ Merged **Merged:** 10/12/2026 **Merged by:** [@rehan-remade](https://github.com/rehan-remade) **Base:** `main` ← **Head:** `docs/drm-analysis-rule` --- ### 📝 Commits (1) - [`c0cd251`](https://github.com/rehan-remade/universal-modder/commit/c0cd251b6de288e29275e02c4d4fc0109dbab2a9) docs: analysing your own DRM-wrapped executable is fine; unpacking how-tos are not ### 📊 Changes **4 files changed** (+17 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/mod-any-game/references/safety.md` (+4 -0) 📝 `.claude/skills/mod-any-game/references/safety.md` (+4 -0) 📝 `CONTRIBUTING.md` (+5 -0) 📝 `skills/mod-any-game/references/safety.md` (+4 -0) </details> ### 📄 Description Reviews drew this line inconsistently: strict for Limbo (#146, #192), while the merged Dark Souls notes (#147, #249) and the #194 review allowed analysis of a self-made dump. This writes down one rule. - **CONTRIBUTING.md, hard rules:** analysing your own legally installed copy of a DRM-wrapped exe (Steam stub, Arxan, Denuvo, iOS FairPlay) is fine, from the running game's memory or a private dump kept outside any repository, and so is writing up what you learned in your own words. A note never explains how to strip or unpack the protection, never links an unpacked executable or a DRM-removal tool, and never gives steps whose result is the game running without its DRM. - **safety.md:** the same for agents. Never write an unpacked exe into the game folder, run it or share it. The parts that draw takedowns (unpacking how-tos, unpacked binaries, removal tools) stay out; the knowledge stays in. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 20:54:56 +00:00

closed this issue
added the
pull-request
label

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

rehan-remade/universal-modder#263

No description provided.

Rows
Columns