Nexus Mods Will Require AI Disclosure for New Mod Uploads

Nexus Mods will require mod authors to declare whether they used AI in their work, the platform said in a post titled “AI-Generated Content on Nexus Mods,” published on 3 November 2026. The Nexus Mods announcement sets out the policy, and the accompanying help article fills in the definitions and timeline.
Authors whose mods are tagged as AI-assisted must publish an explanation of how and where AI was used. Nexus Mods says it will make those tags more prominent on mod pages. There is no outright ban on AI-generated mods, so disclosed AI-assisted work remains eligible for upload.
The “AI Generated Content” category applies when the core work of a mod was produced by AI tools. The examples given are AI-generated code and synthetic voice lines, meaning audio created by a text-to-speech or voice model rather than recorded by a person. Using AI for peripheral tasks, such as drafting a changelog, places a mod outside the category, according to the help article. A mod whose central functionality or audio was generated by a model falls inside it.
On data use, Nexus Mods states that it will not use mods to train AI models, and that it will not sell or license mods to anyone doing so. For a catalogue of user-created scripts, texture packs, 3D models and audio, that is a specific commitment about how content is used, not a general privacy statement.
On the display side, Nexus Mods is launching controls that let users hide AI-generated content on game pages and on the homepage. Search controls are planned next, so filtering will not cover search results at launch. The Recently Added section is also changing. The platform will limit how many mods from a single author appear in that feed at one time, and it will apply tighter restrictions to uploads from new accounts. Both changes target volume and provenance rather than authorship type directly.
Existing authors have 60 days to bring current mods into line with the new requirements. The grace period runs from 3 November 2026 to 2 January 2027, and enforcement begins after it ends. According to the help article, the grace period applies only to the new requirements, not to any other part of the site’s rules.
In my view, the most consequential element is the pairing of disclosure with filtering, rather than disclosure alone. A tag tells a user what a mod contains. A hide control lets that user decide how much of it appears in front of them. Modding communities have long relied on informal trust in authors’ track records, and a required public explanation turns that trust into a record others can check. The open question is how consistently authors will describe partial AI use, and whether a line drawn at “core work” holds up when a mod’s code is only partly generated.
The broader context here is a narrow, operational standard. The policy does not decide whether AI-assisted modding is legitimate. That judgment stays with users, who will see the tags and can filter on them. Authors who use AI tools transparently get clear rules on what to write down and where. Users who want to avoid generated content get a practical way to do so. The 60-day window gives both groups time to adjust before enforcement starts on 2 January 2027.


