Task: TODOS.phase-72.72.14.2.14
V2 mod distribution uses an engineering legal framework gate before a submitted mod can be published through first-party, Steam Workshop, or mod.io paths. The gate verifies the EULA for modders, license terms, content ownership policy, third-party attribution, counsel approval, and commercial-use grants.
This document is an engineering policy scaffold, not legal advice. Final EULA, license terms, content ownership policy language, regional variations, and publisher-specific obligations require counsel approval before distribution gates are allowed to pass.
Runtime Gate#
FV2ModLegalFrameworkPolicy is created by BuildDefaultModLegalFrameworkPolicy
and requires:
- a modder EULA document
- current modder acceptance of required legal documents
- license terms
- content ownership policy
- ownership statements for submitted content
- third-party attribution when third-party content is declared
- counsel approval on legal documents
- an explicit commercial-use license grant for commercial mod distribution
FV2ModLegalDocument records document type, document id, version, title,
document path, effective/expiration timestamps, counsel approval state, and
whether author acceptance is required.
FV2ModLegalAcceptance records the author account, document id, accepted
version, acceptance timestamp, and acceptance state.
FV2ModLegalSubmissionDisclosure records the target mod id, author account,
declared license, ownership statement, third-party attribution, third-party
content flag, and commercial-use request/grant flags.
EvaluateModLegalFramework returns an FV2ModLegalFrameworkReport. The report
includes validity, distribution eligibility, document count, warning/blocking
counts, issues, and actions. Missing legal documents, missing EULA acceptance,
missing counsel approval, missing ownership disclosure, missing third-party
attribution, expired documents, and commercial distribution without an explicit
license grant block distribution.
Distribution Policy#
The legal framework is intended to run before review queue entry and again before publication. A submission can only move forward when:
- required legal documents are present, versioned, path-addressable, and counsel approved
- the author has accepted the current required document versions
- the submitted mod declares license terms and ownership
- third-party content includes attribution
- commercial distribution requests have an explicit recorded grant
Review and publishing UI should surface FV2ModLegalAction entries directly so
authors and reviewers see the next required action instead of receiving a
generic rejection.
Verification#
Run:
python3 V2/ue/Tools/check-v2-mod-legal-framework.py
python3 -m json.tool V2/ue/Content/V2/Modding/ModLegalFramework_V2_Contract.json
The focused checker verifies runtime types, EULA for modders, license terms,
content ownership policy, third-party attribution, counsel approval,
commercial-use grant blocking, automation assertions, docs, CI/Horde wiring, and
TODO evidence for 72.14.2.14.