mirror of
https://github.com/rehan-remade/universal-modder.git
synced 2026-11-05 01:37:40 +00:00
[GH-ISSUE #59] "No Leaks" rule stifles knowledge #17
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rehan-remade/universal-modder#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Selene0623 on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/rehan-remade/universal-modder/issues/59
A lot of modding knowledge (especially for Watch_Dogs series) comes from Beta builds and leaked sources. Without these assets modding these wouldn't be where it's at today. Same thing with Havok modding. Many games use Havok for physics and the stark reality of things is that most of the knowledge comes from leaked sources - as the paywall for obtaining the SDK is massive. Take for example Skyrim or Fallout 4. Any mods you see that alter HKX files use leaked SDKs as no modder can afford the buy-in for a real license. Same deal with Wwise. Any audio mods for Starfield either use a trial version of the SDK or leaked versions. In rare instances they use open source tools - but those are likely RE'd from leaked sources. Maybe the rule should be relaxed a bit?
@rehan-remade commented on GitHub (Oct 5, 2026):
Agreed, and thanks for writing this up. #65 relaxes the rule. Knowledge from beta builds and leaked SDKs or source is fine to write up in your own words, along with where it came from. The leaked material itself stays out, so the repo never distributes it: no pasted code, files, download links or license keys.