KOHEN AVOCATS · PARIS, FRANCE
Bethesda Skyrim 15th anniversary remaster: Can players share a game mod?

Hassan Kohen is a Paris-based lawyer admitted to the Paris Bar (Avocat au Barreau de Paris). Initial strategic analysis: €80 incl. VAT, personal reply within 24 hours.

100% confidential · Legal professional privilege · No obligation

Article generated by artificial intelligence, through a process designed and supervised by the firm

Sources: U.S. court opinions and official U.S. government publications, read for this article

Maître Hassan KOHEN, avocat au Barreau de Paris
Hassan KOHEN
Attorney at the Paris Bar

Bethesda Skyrim 15th anniversary remaster: Can players share a game mod?

Speak to a lawyer 06 89 11 34 45

Can you publish a game mod that works with a game you own? Sometimes, but ownership of a game or permission to play it is not, by itself, permission to redistribute its art, music, code, or another creator’s work. Start by separating what your download contains from what it merely requires the player to have. Then check the applicable creator terms, the license for every outside asset, and whether your distribution would bypass an access control. The answer can differ for a patch, a standalone file, a video, and a paid download.

In an anniversary announcement, Bethesda described a Skyrim bundle containing five creations by verified creators. That announcement describes a bundle; it does not establish the release of a new anniversary remaster. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no findings about Bethesda’s situation. Federal copyright law supplies the framework below. The cited appellate decisions are from the Ninth Circuit, while the cited district court decision concerns its own record and is not binding precedent throughout the United States. The practical question is narrower than whether modding is good or bad: what may this particular creator distribute, through which channel, and under which written permissions?

I. What can a player actually share?

A. Separate the game, the mod, and the rights in each file

Begin with a file inventory. A game installation can contain software code, images, character models, textures, dialogue, recordings, music, and audiovisual sequences. A mod might add an original quest, change a configuration value, replace a texture, supply a script, or package a modified version of an existing game file. These are different acts. A file that only tells a compatible game where to place an object raises a different practical question from a download that includes the game’s original model or soundtrack.

Under federal 17 U.S.C. § 106, a copyright owner has specified exclusive rights, including reproduction, preparation of derivative works, and distribution, subject to the statute’s limitations. Under federal 17 U.S.C. § 501, a violation of an exclusive right can constitute infringement. Those provisions do not decide whether a particular mod contains protected material, whether a right was licensed, or whether an exception applies. Each question depends on the work and the particular use.

For an artist making a new landscape texture, ask who created the underlying image, whether it came from a stock library or another player, and what the license says about inclusion in a downloadable project. Keep the source file, the permission, the version of the license, and the date on which permission was obtained together. If the asset came from a bundle, check whether the bundle permits distribution of the asset itself or only its use as part of a finished work. A note identifying an artist is valuable, but a credit line alone does not establish what the artist authorized.

For a programmer, distinguish a file written independently to work alongside an installed game from a file containing copied game code. Compatibility alone should not be used as a shortcut for deciding whether a work is derivative. A practical inventory identifies what was copied, what was changed, which files are included, and what the game contributes only when a user runs it. If a release contains material created by several people, document permissions separately; a permission from one contributor does not, by itself, describe the rights of every other contributor.

Compare three possible packages. The first contains only a creator’s own text and scripts, with instructions that a player must provide a separately obtained game. The second contains a revised texture exported from the installed game. The third includes that texture plus a voice recording supplied by another player. These examples do not resolve the legal status of any particular package. They show why the release checklist should identify each component and its source before treating the download as a single item.

A private working copy and a public release are also distinct. A creator may need a local copy to test a project, while a public upload provides files to others. The applicable agreement may treat testing, sharing with collaborators, public downloads, console distribution, and charging money differently. Review the permission for each intended act instead of assuming that the permission to perform one includes all the others.

The distinction can matter for viewers as well as mod authors. Recording a tutorial may show a game’s audiovisual material, a mod creator’s work, an added song, or all three. The source of the visual material and the source of the music should be checked independently. A platform’s availability of a recording feature is useful to know, but it does not by itself answer every copyright or contract question about what appears in the recording.

A good inventory also describes what the recipient receives. If a patch requires the recipient’s own copy, say what files the patch changes and whether the patch includes any original files. If a download bundles a standalone object, list its code, textures, sound, and documentation. If access is restricted to a team, record whether the permission covers that team and any later public release. This information lets each rights holder answer a specific request rather than an open-ended request to use an entire project.

B. Read the game and creator terms before choosing a distribution channel

A useful permission check begins with the agreements actually presented to the user: the game’s license, the current creator or modding policy, the terms for the download platform, and any separate agreement attached to an asset. Save copies with version dates where available. Identify the account or person to whom each permission is granted, the work covered, the permitted audience, and whether payment, attribution, modifications, or redistribution are addressed. A forum post repeating an old policy is not a substitute for the operative terms.

In MDY Industries v. Blizzard Entertainment, 629 F.3d 928 (9th Cir. 2010), decided December 14, 2010 and amended February 17, 2011, the United States Court of Appeals for the Ninth Circuit held that the particular anti-bot terms at issue were contractual covenants rather than copyright-enforceable conditions and reversed the related secondary infringement judgment. The court separately upheld liability under the federal anti-circumvention provision for trafficking in a tool that bypassed an effective control over the game’s dynamic online experience. The distinction matters when reviewing a mod: identify the precise promise, the copyright right involved, and any separate access control. In Ted Entertainment, Inc. v. ByteDance Inc., No. 3:25-cv-10933-JSC (N.D. Cal. Oct. 2, 2026), decided October 2, 2026, the United States District Court for the Northern District of California cited MDY in distinguishing access-control claims from trafficking claims involving protection of a copyright right. The court denied a motion to dismiss at the pleading stage; it did not make a final finding of liability.

The next step is to locate the exact grant, not just a general statement welcoming creative activity. Does the text authorize editing the game, distributing a resulting file, showing a recording, or selling a creation? Is the grant limited to a particular platform or marketplace? Is it limited to works submitted through a specified tool? A creator should compare the words with the intended package and audience, including any outside assets, before choosing where to upload.

The same Roblox Corp. v. WowWee Group Ltd., No. 22-cv-04476-SI (N.D. Cal. Sept. 3, 2024), decision of the United States District Court for the Northern District of California on September 3, 2024, granted summary judgment against an express-license defense as to the copyright and trade-dress claims but denied it as to the trademark and false-advertising claims. The order addressed the scope and effect of the agreements on that record, not a final determination that every underlying claim was proved. For a creator, the useful check is whether the actual license covers the particular work, use, and recipient rather than a different activity.

Suppose a policy permits uploads through an approved game creation service but says nothing clear about uploading the same assets to an independent file host. The practical response is to compare the grant’s wording, the files, and the distribution channel. A permission to display a creation inside a service should not automatically be treated as permission to sell an extracted file elsewhere. Conversely, a restriction appearing in one old agreement should not be asserted as a current universal ban without checking the version that applies.

Keep the original text of a permission request and the response. A helpful request identifies the creator, the asset, the proposed modification, the places where it will be offered, and whether the creator will charge. Ask for clarification if a permission covers a preview but does not address a downloadable file. Where collaborators contributed separately, agree on what happens if one later withdraws permission for uses not already covered by the agreement; the wording and applicable law matter.

There is a further federal limitation for computer programs, but it is not a blanket modding license. 17 U.S.C. § 117 addresses specified copies or adaptations made by an owner of a copy, including an essential-step condition and an archival condition. It also limits transfer of covered adaptations. Whether a particular user owns the copy for this purpose, and whether the statutory conditions fit the acts, requires examination of the transaction and governing law. Merely paying for access does not answer that question for every agreement.

Practical release records should be understandable to someone who did not build the project. A one-page manifest can list the original assets, outside assets, their sources, permissions, and intended distribution channels. Keep it with the submitted version. When a project changes, review the manifest again: adding a song, translating dialogue, or moving from a private test to a public marketplace can change the permission question even if the project has the same name.

II. What should creators check before releasing or responding to a notice?

A. Review creative similarity, fair use, and access controls separately

Copyright analysis does not stop at a file extension. A new animation, scene, or combination of assets may raise a question about protected expression even when the finished project is not a verbatim copy of a whole game. At the same time, a shared idea or familiar feature should not be treated automatically as someone else’s protected expression. Identify the work claimed, the elements used, and the similarities that actually matter.

In Hanagami v. Epic Games, Inc., 85 F.4th 931 (9th Cir. 2023), decided November 1, 2023, the United States Court of Appeals for the Ninth Circuit reversed dismissal of a choreographer’s claims because the complaint plausibly alleged substantial similarity in the selection and arrangement of movements used in a game animation. The decision was made at the pleading stage and did not finally find infringement. For a mod creator, the practical comparison includes the selection and arrangement of expressive elements, not only whether an isolated pose or feature is common. In Woodland v. Hill, 136 F.4th 1199 (9th Cir. 2025), No. 23-55418, decided May 16, 2025, the United States Court of Appeals for the Ninth Circuit cited Hanagami when explaining substantial similarity and affirmed dismissal on the different photographic record. That later case distinguishes an available online work from a plausible allegation that another creator had access to it.

For a disputed visual asset, keep the original and modified files rather than relying on recollection. Record the source, the date you obtained it, the stages of your work, and the components that came from elsewhere. Side-by-side comparisons can be useful when they accurately identify the versions being compared. They should also distinguish a common idea, a stock component used under license, and a specific expressive combination. The cases above concern different art forms and procedural records; neither supplies a numerical percentage that makes every game mod lawful.

Federal 17 U.S.C. § 107 sets out fair-use factors: the purpose and character of the use, the nature of the copyrighted work, the amount and substantiality used in relation to the whole, and the effect on the potential market or value. A review, criticism, or tutorial can be relevant to the first factor, but calling a project educational, transformative, or noncommercial does not settle all four factors. Consider the actual use of each work and the market affected. The statute requires a case-specific assessment; it does not provide an automatic exemption for every free fan project.

A small illustrative screenshot in a tutorial and a downloadable archive of game assets serve different functions. For the first, identify the point the image helps explain and whether the image is needed for that explanation. For the second, identify what files are supplied and how people would use them. In both cases, preserve the reason for the choice and the evidence available at the time. There is no need to present a percentage or number of seconds as a universal safe harbor.

Technical access controls raise a separate question. Federal 17 U.S.C. § 1201 addresses circumvention of effective access controls and certain trafficking in tools, with specified statutory limitations and exceptions. The Ninth Circuit’s decision in MDY illustrates why a conclusion about copyright infringement alone does not resolve every anti-circumvention issue. Determine what the tool actually does, whether it bypasses a measure, and whether a specific exception applies before distributing it. A creator should not assume that an otherwise useful purpose automatically resolves those separate questions.

Do not confuse a freely available tool with permission for every use of it. A tool can automate a workflow without supplying rights to the assets processed by that workflow. Likewise, a platform’s technical ability to import a file does not prove that the person uploading it owns or has permission for the contents. Keep the tool’s terms and the asset permissions in the release record as separate items.

Because the published appellate decisions discussed here are from the Ninth Circuit, their holdings bind federal district courts in that circuit subject to the usual rules of precedent; decisions elsewhere may analyze particular issues differently. The district court’s order is useful for its reasoning and facts but does not bind courts nationally. The recent citing opinions identified above show specific subsequent citations, not a complete search of every later case or a guarantee of the current treatment of every proposition.

B. Build a release record and respond to a rights objection

Before publication, test the actual file that a recipient will download. Open the package on a clean installation if that is feasible and list every included file. Remove backup copies, unused game assets, and third-party materials for which permission is uncertain. Confirm that the instructions accurately describe dependencies and do not imply that a player receives the game itself as part of the download. An accurate manifest is more useful than a broad claim that everything in the package is original.

Then match the package to its documents. For each outside asset, note the person or organization that supplied it, the license version, any allowed distribution channel, attribution requirements, and any limits on changes or payment. If terms require a particular credit, prepare it in the form the permission specifies. If a license is silent or ambiguous on a proposed redistribution, record that uncertainty and seek the relevant rights holder’s clarification before assuming the grant is broader.

For a group project, decide who may submit updates, who controls the account holding the upload, and who keeps the permissions. A project may contain a writer’s dialogue, a programmer’s scripts, a musician’s recording, and a visual artist’s texture. An internal agreement can explain which contribution each person permits the team to use, whether it may be edited, and which channels are covered. It should also address what will happen to the released version if the project changes maintainers.

Consider a mod with an original quest and a borrowed portrait. The quest writer can document the original dialogue and script, but the portrait needs its own permission. If the portrait license covers noncommercial display but not redistribution of the image file, the creator should assess whether the planned package falls within that permission. Replacing the portrait with a separately authorized asset may be a practical way to narrow the unresolved issue. The choice depends on the terms actually received, not the label attached to the project.

Paid distribution adds another item to check. The question is not simply whether money changes hands. Identify whether the agreement distinguishes a paid download, a donation unconnected to a particular file, subscription access, or a platform revenue share. The same investigation applies to a free download if the terms restrict where it may be shared. Keep the commercial arrangement and the content of the release visible in the record so the permissions can be compared to the actual use.

If a platform sends a rights objection, preserve the notice, the version of the file involved, relevant communications, and the terms in effect for that upload. Identify the sender’s stated work and the specific claimed use. Compare the complaint with the package and your license records before responding through the platform’s documented procedure. An objection is a claim to examine; it is not, by itself, a judicial finding that the file infringes.

If the objection concerns an asset supplied by someone else, trace it back to the contributor and the precise permission. Avoid altering old records to make them appear contemporaneous. Instead, preserve the old records and document any later clarification separately. If a corrected release is possible, document what changed and why, so that a reviewer can distinguish the original submission from the revised file.

If a creator receives a request to remove a mod, consider both the platform process and the specific issue raised. A notice about a single recording might require checking a different permission from a claim about code. A notice about a technical control raises a different question from the scope of an asset license. Keeping these issues separate makes the next step clearer: identify the file, the right or agreement invoked, the factual support, and the response available under the relevant process.

Creators who find their own work in another project can use the same method in reverse. Preserve a copy or reliable record of the relevant material and identify the work they created, what they believe was used, and any permission they previously gave. Compare the challenged use with the actual grant and the protected expression. A public accusation is not needed to establish the facts for a platform request or a later dispute; a clear inventory and copies of the relevant agreements are more useful.

Finally, revisit the record when a game, platform, or project changes. A patch may replace an independently created file with a modified original asset. A change in marketplace may affect a distribution permission. A new contributor may bring a separate license. Record the change and check the particular permission that it affects. The goal is a release package whose contents, sources, and authorized uses can be explained without guessing.

Conclusion

Sharing a game mod requires a closer look at the actual files and the permissions attached to them. Separate original contributions from game and third-party material, compare the intended distribution with the written terms, and treat fair use and access-control questions as distinct. A clear manifest, preserved permissions, and an accurate record of changes make it easier to decide what can be released and to address an objection if one arises.

📄 Official circular