Derivative Works and Reskins

Intermediate40-60 minutesCross-platformSteam Workshop

The Unturned™ modding community produces a wide range of content that builds on existing work. At one end of the spectrum: a modder authors an entirely original weapon from scratch — an original mesh, original textures, original animations. At the other end: a modder takes an existing community mod, replaces the texture, and uploads it as a new Workshop item. Between these extremes lies a large space of modifications, adaptations, and creative recombinations that are neither clearly original nor clearly a straight copy.

This article addresses that middle space through the lens of US copyright law's derivative works doctrine — the legal framework that governs when a modification of an existing work creates a new work and what rights and obligations accompany that creation. It is the 57 Studios™ reference for reskin legality, derivative work analysis, and the workshop policy implications of reusing existing mod content.

Modders who need foundational background on licensing terminology and attribution requirements before engaging with derivative works should first review Asset Licensing and Attribution. Modders dealing with an active DMCA notice should review How the Steam DMCA Process Works. Modders wondering about Smartly Dressed Games' specific position on community content should review Smartly Dressed Games Modding Policy.

The legal landscape for Unturned modding and derivatives

The Unturned™ modding ecosystem exists within a specific legal context. Mods are distributed through the Steam Workshop, which operates under Valve's Terms of Service. The underlying game is owned by Smartly Dressed Games. Community modders hold copyright in their original mod content. These three layers — Valve, SDG, and community modders — each contribute to the legal environment in which derivative work questions arise.

For the purposes of this article, the relevant copyright principles are those of US copyright law (17 U.S.C. et seq.). Smartly Dressed Games and Valve are US-based entities; the Steam Workshop operates under US legal jurisdiction for the purposes of DMCA compliance. Modders based outside the US remain subject to their local copyright law in addition to US copyright principles where applicable.

This is compliance documentation, not legal advice

This article is published by 57 Studios™ as compliance documentation for modders in the Unturned community. It describes how US copyright law applies to common modding scenarios, so that modders can make informed decisions. It is not legal advice, and 57 Studios is not a law firm. Modders with significant legal exposure — commercial mods with large revenue, active litigation, or disputes involving significant assets — should consult a licensed attorney.

Why derivative work rules matter more for modders than for players

Players who download and play a mod are consumers. Their relationship with the mod's copyright is governed by the license — typically the Steam Subscriber Agreement and the Workshop terms — and they have no obligations under copyright law beyond playing the game as licensed.

Modders are creators and distributors. When a modder builds on existing content, they step into the role of a derivative author. That role carries the obligations of a copyright actor: securing authorization, complying with license conditions, and attributing sources. The derivative works doctrine exists to balance the interests of original creators (who have invested creative labor in their work) with the interests of the broader creative community (who build on prior work to create new value).

In the modding context, this balance is particularly important because the community ecosystem depends on a norm of reciprocal respect: original authors share their work, often for free; in exchange, the community respects their rights and requests permission before building derivatives. When that norm breaks down — when reskins are uploaded without permission, when attribution is omitted — it erodes the trust that sustains the open sharing culture.

The relationship between copyright and Workshop moderation

Steam Workshop moderation and copyright law are distinct mechanisms that operate in parallel.

Workshop moderation enforces Valve's Terms of Service, which prohibit uploads that infringe others' intellectual property rights. Moderation actions include content removal and account restrictions. Moderation is triggered by user reports and DMCA notices.

Copyright law establishes the underlying rights. A DMCA notice is the legal mechanism by which a rights holder requests removal of infringing content from the Workshop. See How the Steam DMCA Process Works for the full DMCA framework.

A mod may be moderated without being legally infringing (e.g., removed for Terms of Service violations unrelated to copyright), and a legally infringing mod may not be reported or moderated. Legal compliance and Workshop compliance are both required, but they are not the same thing.

What is a derivative work under US copyright law

Under the US Copyright Act (17 U.S.C. § 101), a derivative work is defined as "a work based upon one or more preexisting works, such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment, condensation, or any other form in which a work may be recast, transformed, or adapted." The statute lists examples, but the definition is broad: any work that incorporates a preexisting copyrighted work in a modified, adapted, or transformed form is potentially a derivative work.

The critical implication: creating a derivative work requires the permission of the copyright holder of the underlying work. Without that permission, creating and distributing a derivative work is copyright infringement, even if the derivative has been substantially changed from the original.

Permission for derivatives is separate from permission to view or download

The right to download or use an asset does not include the right to create a derivative work from it. These are separate rights under 17 U.S.C. § 106. A modder who downloads a CC-BY-ND asset has permission to distribute it unchanged, but does not have permission to create a derivative work — those are two distinct rights that the ND condition explicitly withholds.

The two requirements for derivative work copyright

A derivative work can itself receive copyright protection, but only if it meets two requirements:

1. The derivative was created with the authorization of the underlying work's copyright holder (either through a permissive license or explicit permission).
2. The derivative contains a sufficient amount of original expression — new creative content contributed by the derivative's author.

A reskin that changes only one pixel, or substitutes a color with a virtually identical one, likely does not contain sufficient original expression to qualify as an independently copyrightable work. A reskin that involves substantial artistic reworking — new color palettes, new surface details, new pattern elements — may qualify.

The copyright in the derivative work, if it qualifies, covers only the new original expression. It does not extend to the underlying work's elements, which remain under their original copyright.

What constitutes a derivative work in the Unturned modding context

In Unturned™ modding, derivative works arise across multiple asset types. The following examples illustrate the range:

Modification type	Likely derivative?	Analysis
Retexturing an existing mod's mesh with a new texture from scratch	Yes	The mesh is from the original; the texture is new. The combined work is a derivative of the original mesh.
Recoloring an existing texture by shifting the hue in Photoshop	Yes — borderline	The underlying texture composition is unchanged. The recolor adds minimal original expression.
Using an existing mesh as a blocking shape to model a new mesh around	No	The new mesh is independently authored; the original mesh was only used as a reference, not incorporated.
Taking an existing weapon mod's entire prefab, changing the barrel length, and republishing	Yes — clear derivative	The prefab contains substantial original expression from the original mod. The barrel modification is minor.
Adapting a vanilla Unturned mesh to add attachment rails	Depends on SDG's policy	Vanilla assets are owned by Smartly Dressed Games. Whether community modification of vanilla assets is permitted is governed by SDG's modding policy, not by general derivative works analysis. See Smartly Dressed Games Modding Policy.
Building a new prefab that uses the same animation rig structure as an existing mod	Borderline	Animation rigs are potentially copyrightable; if the rig was independently authored, no derivative issue. If the rig was copied, it is a derivative.
Writing a new .dat configuration file that balances a community mod differently	No	Configuration data with minimal creative expression is unlikely to qualify for copyright protection.

This table is analytical, not advisory

The above table reflects a documentary analysis of common modding scenarios, not legal advice. The derivative work determination in any specific case depends on the specific facts of that case. When in doubt about a particular modification, consult the original author and request permission.

Reskins: the most common derivative work scenario

A "reskin" in modding terminology typically refers to replacing or significantly modifying the texture of an existing mod without replacing the underlying mesh, prefab, or other structural elements. Reskins are by far the most common form of derivative work in the Unturned community.

Is a reskin always a derivative work?

Not necessarily. The derivative work analysis depends on what elements of the original mod are incorporated into the reskin and what the original author contributed to those elements.

A reskin is a derivative work when:

• The reskin uses the original mod's mesh, UV layout, or prefab structure.
• The reskin includes modified copies of the original textures (e.g., the original texture used as a base layer with modifications on top).
• The reskin uses animation clips or rigs authored by the original modder.

A reskin is not a derivative work when:

• The modder authors an entirely new mesh that is inspired by the original's design but does not copy its geometry.
• The modder authors entirely new textures from scratch on a model that is independently authored.
• The modder authors a new .dat configuration for an existing item category without using any of the original mod's authored assets.

The practical implication for Workshop reskins

The Unturned Workshop community has historically treated reskins as a grey area. In practice, many reskins are uploaded without the original author's permission and without attribution, and many of them are not challenged. The absence of a challenge does not mean the use is lawful. It reflects the practical reality that rights holders in the modding community often lack the time or inclination to pursue every infringement.

57 Studios does not rely on the practical absence of enforcement as a substitute for legal authorization. Every reskin produced under the 57 Studios umbrella goes through the derivative works checklist documented later in this article.

The most reliable approach for reskins

If you want to reskin an existing community mod, contact the original author and ask for permission. Many community modders are willing to grant permission for reskins — particularly non-commercial ones — when asked. A brief, respectful message explaining the project and asking for permission takes minutes and eliminates the legal uncertainty entirely.

The transformative-use standard

Transformative use is a concept most prominently applied in the fair use doctrine of US copyright law (17 U.S.C. § 107). It is not a general license — it is a defense to copyright infringement that a court may recognize under specific circumstances. Understanding transformative use is important for modders because it is frequently misapplied as a general justification for derivative works.

What transformative use actually means

A use is transformative when it adds new meaning, expression, or message to the original work — when it does not merely supersede the original but instead adds something new. Courts look at four fair use factors:

1. The purpose and character of the use — including whether the use is commercial or non-profit educational, and whether it transforms the original.
2. The nature of the copyrighted work — creative works receive stronger protection than factual compilations.
3. The amount and substantiality of the portion used — how much of the original was taken, and whether the "heart" of the original was taken.
4. The effect of the use on the potential market — whether the derivative substitutes for the original in the market.

Fair use is a defense, not a license

Fair use is a legal defense that must be evaluated by a court on the specific facts of each case. It is not a license granted in advance. A modder who believes their reskin is "transformative" cannot know in advance whether a court would agree. Relying on fair use without a strong factual basis for each of the four factors is a significant legal risk.

What "transformative" does NOT mean in common modding usage

The word "transformative" is frequently used colloquially in the modding community to mean "I changed it enough." This informal usage does not correspond to the legal transformative-use standard. Changing the hue of a texture, adding detail to a mesh, or altering the configuration of a prefab does not automatically constitute transformative use in the legal sense. Transformation in the legal sense requires that the new work add a new purpose, meaning, or message to the original — not merely a modification of the original's elements.

A reskin that changes an existing weapon texture from military camouflage to a neon pattern has been modified, but has not been transformed in the legal sense unless the neon pattern adds a distinct artistic statement or purpose that the original did not have.

Transformative use and the Unturned modding community

The Unturned modding community is a small, specialized ecosystem. The four fair use factors applied to a typical modding reskin tend to produce unfavorable results for a transformative use claim:

Factor	Typical modding reskin analysis
Purpose and character	Commercial or non-commercial, but primarily creative; no educational or commentary purpose distinguishing it from the original
Nature of the work	The original mod is a creative work; creative works receive stronger protection, making fair use harder to establish
Amount taken	The mesh, prefab, and/or rig — often the most substantial creative elements of a mod — may be taken in full
Market effect	A reskin may directly substitute for the original mod in the player community, particularly if it is visually superior

This analysis does not mean that transformative use can never apply to a modding reskin — it means that the factual basis for a transformative use claim in a standard modding reskin is typically weak, and modders should not rely on it as a primary justification for using another creator's work without permission.

When a reskin needs original-author permission

The following scenarios require explicit permission from the original mod's author before the reskin may be legally created and distributed:

Scenario	Permission required?
Reskin uses original mesh, original author's license is CC-BY-SA	No permission required, but attribution and ShareAlike conditions apply
Reskin uses original mesh, original author's license is proprietary (no stated license)	Yes — explicit permission required
Reskin uses original mesh, original author's license is CC-BY-ND	No derivatives permitted — this reskin cannot be done legally without separate permission
Reskin uses entirely independent mesh, only inspired by original design	No permission required
Reskin uses original prefab with modified attachment hooks	Yes — prefab is part of the original work
Reskin replaces texture only, uses original mesh, no license stated on original	Yes — treat as proprietary, contact original author

How original expression is identified in mod assets

The derivative work analysis turns on whether the original mod's "protectable expression" appears in the new work. Not all elements of a mod are equally protectable. Understanding what copyright protects — and what it does not — is essential for accurate derivative work analysis.

What copyright protects in mod assets

Asset element	Copyright protection	Notes
Mesh geometry (specific vertex positions and polygonal topology)	Yes, if original	A mesh modeled by a human with creative input is protected. A mesh auto-generated by an algorithm with no creative input may not be.
Texture artwork (painted or composed visual elements)	Yes	Textures are pictorial works protected from the moment of creation.
UV layout (the specific unwrapping of a mesh's surface)	Borderline	UV layouts that reflect creative decisions (seam placement, island arrangement) may be protectable; purely functional UV layouts may not be.
Animation keyframe data	Yes, if original	Animation authored by a modder is a choreographic or audiovisual work; specific keyframe sequences are protectable.
Prefab hierarchy (GameObject organization in Unity)	Borderline	A purely functional prefab hierarchy may not receive copyright protection; one with creative structural choices may.
.dat parameter values	No (generally)	Pure data and configuration parameters with no creative expression are not copyrightable.
Mod name and branding	Trademark potential, not copyright	Mod names and logos may be protected under trademark principles; not typically under copyright as short phrases.
Workshop description prose	Yes	Written descriptions are literary works protected by copyright.
Sound recordings packaged with the mod	Yes	Recorded audio is protected as a sound recording separate from the underlying musical composition.

The idea-expression dichotomy

Copyright protects expression — the specific creative choices a modder made in creating an asset. It does not protect ideas, concepts, or functional requirements. The idea of a tactical rifle with a folding stock is not protected. The specific mesh a modder created to represent that rifle — with its particular vertex positions, edge flow, and surface detail — is protected.

Thin copyright vs. thick copyright

"Thick" copyright applies to works with a high degree of creative expression — a hand-painted texture with original artistic composition, a complex mesh with distinctive design details. Derivative works that incorporate thick-copyright elements require more substantial transformation to qualify as independent works.

"Thin" copyright applies to works with minimal creative expression above the minimum threshold — a simple geometric shape, a solid-color texture, a purely functional prefab with no creative structural choices. Thin-copyright works receive copyright protection, but only against very close copying. A derivative that makes even modest changes may not infringe a thin-copyright work.

Asset type	Copyright thickness	Implication for derivatives
Hand-painted, detailed weapon texture with distinctive artistic style	Thick	Requires substantial transformation; close reskins are infringing
Procedurally generated seamless metal texture	Thin	Only close copies infringe; modest modifications may not
Highly detailed, custom-modeled weapon mesh	Thick	Requires substantial transformation
Simple primitive-based placeholder mesh	Thin	Only very close copies infringe
Custom-choreographed idle animation with distinctive timing	Thick	Close copies of the animation sequence infringe
Standard idle animation with minimal movement	Thin	Only very close copies infringe

SDG's documented position on community reskins

Smartly Dressed Games (SDG) — the developer of Unturned™ — has published documentation regarding community modding and Workshop content. The official modding documentation is available at https://docs.smartlydressedgames.com/en/stable/.

SDG's documentation addresses the use of vanilla Unturned assets in community mods, the permissibility of community modifications to SDG's content, and the Workshop policies that apply to uploaded mods. 57 Studios does not summarize SDG's position in place of the primary source; modders should read the current official documentation directly, as SDG's policies may be updated and the most current authoritative statement is the documentation itself.

What can be stated from the perspective of this knowledge base:

1. SDG's modding permissions pertain specifically to vanilla Unturned™ assets and SDG's own content. They do not extend to or govern the relationship between two community modders regarding community-authored assets.
2. Community-to-community reskins are governed by the copyright of the original community modder, not by SDG's policies.
3. SDG's Workshop moderation may respond to community reports of reuploaded or reskinned mods regardless of the underlying copyright analysis — Workshop moderation and copyright law operate on separate tracks.

Community asset disputes

When two community modders dispute whether a reskin was authorized, SDG's Workshop moderation may or may not intervene. The authoritative resolution of such a dispute is between the modders themselves, or through the Steam DMCA process if the rights holder files a formal notice. SDG is not a mediator for inter-community copyright disputes.

Workshop policy on reuploaded assets

Steam's Workshop Terms of Service prohibit uploading content that infringes the intellectual property rights of others. This applies both to Smartly Dressed Games' vanilla assets and to community modders' original assets. The practical mechanism for enforcing this is the DMCA notice-and-takedown process. See How the Steam DMCA Process Works for the full process.

Separately from the DMCA process, Unturned's Workshop community has informal norms against:

• Reuploading another modder's work without modification or credit.
• Uploading a reskin of another modder's work without the original author's permission.
• Presenting a reskin as an original work without disclosing the original it is based on.

These community norms are not legally binding but reflect the cooperative standards that maintain trust in the modding community. Violating them, even in cases that do not rise to legal infringement, typically results in community backlash and potential Workshop reporting.

The 57 Studios derivative-works checklist

Before a 57 Studios mod that modifies or builds upon existing community content is published to the Workshop, the following checklist must be completed. It is incorporated into the 57 Studios pre-publication review process.

Checklist items

Item	Status required before publication
All elements from existing community mods identified	Complete
Copyright holder identified for each borrowed element	Complete
License confirmed for each borrowed element	Complete
License permits derivatives confirmed	Complete
License permits commercial use confirmed (if commercial mod)	Complete
Attribution block written for each licensed element	Complete
Attribution included in Workshop description draft	Complete
ShareAlike conditions addressed if any SA assets used	Complete
Original author notified of derivative (best practice)	Recommended
Asset log updated with all borrowed elements	Complete

Notification to original authors

57 Studios recommends notifying the original author when publishing a derivative work, even when the license does not require notification. This is not a legal requirement — it is a community courtesy. Many original authors appreciate knowing that their work has inspired a derivative, and the notification opens a channel for feedback or collaboration.

Sample permission request template

When explicit written permission is required to create a derivative work from an existing community mod, the following template provides a starting point. Modders should adapt it to the specific circumstances.

Subject: Permission request — derivative work based on [Original Mod Name]

Hello [Original Mod Author Name/Username],

My name is [Your Name/Studio Name], and I am a modder working on [brief description of the new mod].

I would like to create a derivative work based on your mod "[Original Mod Name]" (Workshop link: [URL]). Specifically, I would like to use the following elements from your mod:

- [List the specific elements: e.g., "the weapon mesh for the [weapon name]", "the texture files for the [item]"]

My intended use is:
- Distribution: [Steam Workshop, free / Tebex, commercial]
- Modification: [describe what you will change]
- Attribution: I will credit you as "[credit format]" in the Workshop description of my mod.

Could you confirm in writing whether you grant permission for this use? If there are specific conditions or credit formats you prefer, please let me know and I will comply with them.

Thank you for your time and for your work on [Original Mod Name].

[Your Name / Username]
[Studio: 57 Studios™]
[Contact: [your contact method]]

Keep the permission response

When the original author responds granting permission, save the complete message — including the date, the author's username, and the specific permission granted. This documentation goes into the mod's asset log. If questions arise later, the saved permission response is the evidence of authorization.

How license conditions apply to derivatives in practice

The interaction between license conditions and derivative work creation is the area where most practical compliance questions arise. This section works through the most common license-condition combinations encountered in Unturned modding.

CC-BY derivatives: the attribution condition

A derivative of a CC-BY asset inherits the CC-BY attribution condition. The attribution must identify the original author of the work being built upon — not just the original author of the top-level asset, but any CC-BY authors whose work appears in the derivative chain.

Example: Modder A releases a base mesh under CC-BY 4.0. Modder B creates a textured derivative and releases it under CC-BY 4.0. Modder C creates a further derivative by reskinning Modder B's work. Modder C's attribution must credit both Modder A (for the mesh) and Modder B (for the texture), if both elements appear in Modder C's work.

Attribution chains in multi-layer derivatives

Attribution obligations compound through derivative chains. A modder who builds on a derivative of a derivative must attribute all upstream authors whose work appears in the final product. Tracing this chain is part of the pre-publication checklist.

CC-BY-SA derivatives: the ShareAlike propagation

CC-BY-SA's ShareAlike condition means the derivative must be distributed under CC-BY-SA or a compatible license. "Compatible" is defined by Creative Commons and does not simply mean "any open-content license." A modder who creates a derivative of a CC-BY-SA asset and wants to release the derivative under CC-BY (without ShareAlike) cannot do so — the ShareAlike condition requires the SA condition to propagate.

Practically:

Scenario	Permissible?
Derivative of CC-BY-SA asset released under CC-BY-SA	Yes
Derivative of CC-BY-SA asset released under CC0	No — CC0 does not satisfy the SA requirement
Derivative of CC-BY-SA asset released as proprietary	No — proprietary release does not satisfy SA
Derivative of CC-BY-SA asset released under CC-BY	No — CC-BY lacks the ShareAlike condition
Derivative of CC-BY-SA 4.0 released under CC-BY-SA 3.0	Generally Yes — same license family, earlier version

CC-BY-ND derivatives: the no-derivatives condition

CC-BY-ND permits distribution of the unmodified original with attribution, and nothing more. A modder who wants to incorporate a CC-BY-ND mesh into their mod must use it exactly as provided — no geometry modifications, no UV adjustments, no scaling changes. Any modification constitutes a derivative work, which the ND condition prohibits.

The only path to creating a derivative of a CC-BY-ND asset is explicit written permission from the rights holder, superseding the ND condition for that specific use. See Asset Licensing and Attribution for the permission request template and documentation standard.

MIT derivatives: the license-text condition

MIT-licensed assets permit derivative works without restriction, provided the copyright notice and license text are preserved and distributed alongside the derivative. For a Unturned mod, this means:

1. The MIT license text (including the original copyright notice) must be included in the mod distribution — either in the Workshop description or in a bundled LICENSE.txt.
2. The license text must not be modified or stripped.
3. Attribution in the Workshop description is recommended but not strictly required by the MIT license itself — the license text is the required preservation.

Managing derivatives in collaborative mods

When multiple contributors work on the same mod, derivative work management becomes more complex. Each contributor may bring their own asset sources, their own derivative dependencies, and their own permissions. 57 Studios manages this through the following practices.

Contributor asset declaration

Every contributor to a 57 Studios collaborative mod is required to declare the license status of all third-party assets they introduce to the project at the time of contribution. The declaration includes:

• The asset name and file(s)
• The source and author
• The license
• Whether the asset is a derivative of any existing community mod
• If derivative: the original mod, the elements used, and the permission obtained

Contributions that introduce undocumented third-party assets are not accepted until the declaration is complete.

Derivative dependency tracking

When a collaborative mod incorporates an asset that is itself a derivative of a prior work, the derivative dependency must be tracked through the entire chain. The mod's asset log records:

• The top-level asset (the file used in the mod)
• The intermediate derivative (if any — e.g., a textured version of an original mesh)
• The original upstream work

All attribution and license conditions from the upstream chain apply to the mod.

Joint authorship and copyright ownership

When two or more modders contribute original expression to the same asset (for example, one modder authors the mesh and another paints the texture), the resulting asset may qualify as a joint work under US copyright law. Joint authors hold the copyright jointly, which means either author may license the work without the other's consent (but must account to the other for any revenue from commercial licensing). 57 Studios' internal agreements establish how copyright in jointly authored mod assets is allocated and managed.

Reskin community norms and enforcement mechanisms

Beyond the legal framework, the Unturned community has established informal norms around reskins and derivative content. Understanding these norms helps modders navigate community expectations alongside legal requirements.

Informal norm: credit and communicate

The community standard — distinct from any legal requirement — is that modders who build on another modder's work should credit the original and communicate with the original author. This norm exists even for uses that are clearly legally permissive (e.g., a CC-BY asset that requires only attribution). The communication step — a message to the original author saying "I've created a derivative of your work and released it here" — is considered courtesy, not obligation.

57 Studios treats communication as a best practice, not a requirement, but recommends it in all cases where the derivative relationship is discernible by inspection.

Informal norm: don't publish competing reskins of paid work

For commercial mods sold through Tebex or similar platforms, the community norm strongly disfavors reskins that directly compete with the original commercial product. Even if legally permissible under the original's license, publishing a reskin of a paid mod at a lower price (or for free) effectively undercuts the original author's commercial value. This is distinct from the legal question — a legally permissible act can still be a community norm violation.

57 Studios' policy is to avoid publishing reskins that would materially compete with the original author's commercial distribution, regardless of the legal permissibility.

The role of the original author's Workshop page

The original mod's Workshop page is the primary public record of its copyright status and license. When a reskin is published, rights holders typically discover it through:

• Community reports from players who recognize the derivative.
• Steam Workshop recommendation algorithms surfacing the reskin alongside the original.
• Direct notification from the reskin author (the recommended best practice).
• Periodic searches by the original author for mods using their assets.

Rights holders who discover unauthorized derivatives often prefer a non-adversarial resolution — they want attribution, or they want the unauthorized elements removed. Starting with a cooperative contact to the reskin author is standard in the Unturned community before escalating to formal mechanisms.

Enforcement mechanisms available to original authors

When a community modder believes their work has been used in an unauthorized reskin, the available enforcement mechanisms are:

Mechanism	Description	Appropriate when
Direct contact	Message the reskin author requesting attribution correction or takedown	First step; most disputes resolve here
Workshop report	Report the mod to Steam/Valve for intellectual property infringement	Original author contact was ignored or refused
DMCA notice	File a formal DMCA takedown notice with Steam	Clear infringement with no resolution through direct contact
Community report	Post publicly in the relevant community spaces	After other mechanisms have been exhausted; should be factual and documented

57 Studios cooperates promptly with rights holders who contact us regarding our mods. Direct contact is always the recommended first step.

Building a culture of derivative transparency

The long-term health of the Unturned modding ecosystem depends on a culture where derivative relationships are acknowledged openly, attribution is treated as a professional standard, and modders feel confident sharing their work knowing it will be respected.

57 Studios contributes to this culture through:

• Publishing this documentation to make the legal framework accessible to all modders.
• Applying the derivative-works checklist consistently to every published mod.
• Crediting original authors in Workshop descriptions with more detail than the minimum required.
• Notifying original authors when their work has inspired or served as a basis for a 57 Studios derivative.
• Responding promptly and cooperatively to any rights-holder inquiry regarding 57 Studios mods.

The modding community is not adversarial. The vast majority of disputes about reskins and derivatives arise from ignorance of the applicable framework, not from malicious intent. This documentation exists to reduce that ignorance so that the community can maintain the cooperative, open-sharing culture that has made it valuable.

Modders who want to continue building their legal compliance knowledge after this article should review Smartly Dressed Games Modding Policy for the SDG-specific framework, and Asset Licensing and Attribution for the broader asset licensing reference. The 57 Studios legal documentation series is designed to be read in sequence: licensing foundation, derivative work analysis, and then the SDG-specific policies that govern how vanilla content may be used in community mods.

Reskin documentation in the Workshop description

When a 57 Studios mod is a derivative of an existing community mod, the Workshop description must disclose the derivative relationship clearly. This serves several purposes: it satisfies attribution license conditions, it is transparent with the community, and it allows rights holders to quickly identify their work in 57 Studios mods.

The disclosure appears in a dedicated section of the Workshop description. The section heading, "Derivative Content," is placed above the standard "Asset Credits" section when both apply. This positioning ensures rights holders see the disclosure before reading the generic asset credits.

Disclosure format

--- DERIVATIVE CONTENT ---

This mod contains content derived from the following community mods. All
derivative uses are made with the permission of or under the license granted
by the original authors. Attribution is provided below.

[Original Mod Name] by [Author Username]
  Workshop: [Workshop URL — or "URL no longer available" if the original has been removed]
  License: [License identifier or "Written permission granted [Date]"]
  Elements used: [Specific elements — mesh, texture, prefab, animations, audio]
  Modifications: [Describe modifications made]
  Attribution: As required by [License], [Author Username] is credited as the
               original author of the [element] used in this mod.

--- END DERIVATIVE CONTENT ---

When the original mod is no longer available

If the original mod from which a derivative was created has been removed from the Workshop, the disclosure should note the removal and provide whatever identifying information is still available — the original mod's name, the author's username, and the date the original was accessed. The absence of the original from the Workshop does not eliminate the copyright relationship or the attribution obligation. The rights holder's copyright persists regardless of whether the work is currently published.

Archiving for compliance purposes

57 Studios recommends archiving a local copy of the Workshop page, the mod description, and the license statement for any community mod used as the basis for a derivative. This archive provides documentation of the license that was available at the time the derivative was created, which is relevant if the license changes or the mod is removed after publication.

Appendix A: Derivative work vs. original work — key indicators

Use the following indicators to assess whether a planned mod component is likely to be treated as a derivative work of an existing mod or as an independent original work.

Indicator	Points toward derivative	Points toward independent original
Source geometry	Mesh geometry is copied or exported from the original mod	Mesh geometry is modeled from scratch, only inspired by the original
Texture relationship	Existing texture used as base layer; modifications layered on top	New texture painted from scratch with no underlying original texture
UV layout	UV layout is inherited from the original mesh	UV layout is authored independently for the new mesh
Prefab structure	Prefab hierarchy is copied from the original and modified	Prefab is assembled independently with original configuration
Rig and animations	Armature or animation clips are taken from the original	Armature authored independently; animations keyframed from scratch
Degree of change	Modifications are incremental (color shift, minor detail add)	Modifications are comprehensive (fundamental redesign of visual identity)
Identifiability	The original is readily identifiable in the derivative	The original is not recognizable in the derivative

"Identifiability" is a practical indicator, not a legal test

Whether the original is "identifiable" in the derivative is a practical proxy, not a legal test. A work can be a legal derivative even if it is not readily identifiable as such. And a work where the original is identifiable may still be an independent work if the underlying elements are not actually copied. Use identifiability as a first-pass indicator; confirm with the full checklist.

Appendix B: Common misunderstandings about derivative works in modding

Misunderstanding	Correct understanding
"I changed it more than 50%, so it's original."	There is no percentage threshold in US copyright law. The question is whether copyrightable expression from the original was incorporated, not by how much it was changed.
"The original author isn't active, so I can use it."	Copyright is not abandoned by inactivity. Rights persist for the life of the author plus 70 years regardless of whether the author is active in the community.
"It's just a reskin; it's not like I'm selling it."	Reskins that incorporate the original's copyrightable elements are derivative works regardless of whether they are sold or free.
"Everyone in the community does it."	Community practice does not establish legal permission. Widespread infringement is still infringement.
"I credited the original, so I'm covered."	Attribution satisfies the attribution condition of licenses like CC-BY, but it does not substitute for the derivative-permission condition of licenses like CC-BY-ND, nor for the requirement to obtain explicit permission for proprietary works.
"I bought the original mod on Tebex, so I own it."	Purchasing a commercial mod grants a license to use the mod, not ownership of the copyright. The copyright remains with the original author.
"The original author said it was fine in Discord."	A verbal or chat-based permission is better than nothing, but it is the weakest form of documentation. A written, preserved message from the verified rights holder is the minimum standard for documented permission.

Appendix C: The 57 Studios derivative-works documentation standard

When a 57 Studios mod contains derivative content, the Workshop description must include a "Derivative Content" section in addition to the standard Asset Credits section. The Derivative Content section follows this format:

--- DERIVATIVE CONTENT ---

[Name of derived element, e.g., "Weapon mesh basis"]
  Original mod: [Original Mod Name] (Workshop link: [URL])
  Original author: [Author Name/Username]
  Elements used: [Specific elements taken from the original]
  License: [License of the original, e.g., "CC-BY 4.0"]
  Modifications made: [Describe what was changed]
  Permission: [License grant / Written permission date / Explicit permission granted by message dated [Date]]
  Attribution: [Full attribution text as it appears in the Workshop description credits]

--- END DERIVATIVE CONTENT ---

This documentation standard exists to ensure that rights holders can quickly identify whether their work has been used in a 57 Studios derivative, and that 57 Studios can demonstrate compliance with license conditions for any element in any published mod.

Detailed reskin scenarios and analysis

The following scenarios represent common reskin situations encountered in the Unturned community. Each is analyzed against the derivative works framework to illustrate how the principles apply in practice.

Scenario 1: Recolor of an existing weapon texture

Description: A modder downloads a community weapon mod, opens the texture file in Photoshop, applies a hue/saturation adjustment layer to shift the color from green camouflage to urban grey, and uploads the result as a new Workshop item.

Analysis: The underlying texture composition — the scratches, wear patterns, surface detail, panel layout — is entirely from the original mod. The hue shift adds no new artistic expression beyond a color change applied algorithmically. The result is a derivative work that incorporates the original's thick copyright expression with minimal transformation. The mesh and prefab are also taken from the original.

Required: Explicit permission from the original mod author (assuming the original mod has no permissive license), OR the original mod must be under a CC-BY, CC-BY-SA, or CC0 license that permits derivatives.

Attribution: Full attribution block for the original mod's mesh, texture, and prefab.

Scenario 2: New texture on original mesh

Description: A modder downloads a community weapon mod's mesh (the mod is licensed CC-BY 4.0), paints an entirely new texture from scratch in Substance Painter, and publishes the result.

Analysis: The mesh is from the original (CC-BY 4.0); the texture is original. This is a derivative work of the original mesh — the mesh, which constitutes substantial creative expression, is present in the new work. The CC-BY 4.0 license permits derivatives; attribution to the original mesh author is required. The new texture is an original work by the modder.

Required: Attribution to original mesh author per CC-BY 4.0.

Note: The derivative work (new mod) as a whole is a new work that includes the CC-BY mesh. The modder holds copyright in the new texture; the original author holds copyright in the mesh.

Scenario 3: Inspired redesign with independent authoring

Description: A modder is inspired by an existing community weapon mod's aesthetic and creates a new weapon from scratch — independently modeling a mesh that evokes a similar silhouette, painting new textures, and configuring new animation clips. No files from the original mod are used.

Analysis: Copyright protects expression, not ideas. A weapon design aesthetic, silhouette, or concept is an idea. The specific creative expression — vertex positions, texture composition, animation keyframes — are protectable. Since no expression from the original mod appears in the new mod, there is no derivative work relationship. The new mod is independently authored.

Required: No permission or attribution to the original mod needed, though voluntary credit acknowledging the inspiration is considered good community practice.

Scenario 4: Prefab modification for a weapon pack

Description: A modder is creating a weapon pack themed around a particular era. They take an existing community rifle mod (no license stated) and add a bayonet attachment hook to the prefab hierarchy, author a new bayonet mesh and texture, and package the modified rifle with the new bayonet as a bundle.

Analysis: The original rifle mod — mesh, texture, animation, prefab — is present in the new bundle. The no-license status means the original is proprietary. The bayonet is original. The combination is a derivative work of the original rifle mod. The rifle elements cannot be included without explicit permission.

Required: Explicit written permission from the original rifle mod author for the rifle's mesh, texture, prefab, and animation components.

Scenario 5: Soundpack reskin — audio-only modification

Description: A modder takes an existing weapon mod (CC-BY-SA 4.0 license covering all assets), replaces only the firing sound effect with a custom-recorded sound, and republishes the result.

Analysis: The weapon mod's visual assets (mesh, texture, prefab, animations) are taken in full. The sound is new. The CC-BY-SA 4.0 license permits derivatives with attribution and ShareAlike. The combined work must be distributed under CC-BY-SA 4.0 (or compatible), and the original author must be attributed.

Required: Attribution per CC-BY-SA; republished mod must use CC-BY-SA or compatible license.

Pre-publication derivative work audit

The 57 Studios pre-publication audit for mods containing derivative content proceeds in the following sequence. This audit is completed independently of the standard asset log review, even for mods that have undergone informal review during development.

Audit step	Action	Documentation
1. Asset inventory	List all assets in the mod by file	Asset log
2. Origin classification	For each asset: original, derivative, or licensed	Asset log column
3. Derivative identification	For each derivative asset: identify the original work	Asset log — source field
4. License confirmation	Confirm the original work's license; confirm it permits derivatives	Asset log — license field
5. Commercial use check	Confirm license permits commercial use if mod is commercial	Asset log — commercial cleared field
6. Attribution block	Write attribution block for each derivative element	Workshop description draft
7. ShareAlike check	If any SA assets: confirm mod's license is compatible	Workshop description — license statement
8. Permission documentation	If proprietary: confirm written permission is on file	Asset log — permission documentation
9. Description review	Review Workshop description draft for completeness	Pre-publication sign-off
10. Author notification	Send notification to original authors (best practice)	Communication log

Frequently asked questions

What is the difference between a reskin and a derivative work?

"Reskin" is modding community terminology; "derivative work" is a legal term. A reskin is a type of derivative work when it incorporates copyrightable elements from an existing mod — specifically when the new mod uses the original's mesh, texture (as a base), prefab, rig, or animation clips. Not every reskin is a derivative work in the legal sense: a reskin built on an independently authored mesh with an independently authored texture is not a derivative of any existing mod, even if it is visually inspired by one.

Can I reskin a vanilla Unturned item?

Vanilla Unturned™ items are owned by Smartly Dressed Games. Whether community modifications to vanilla items are permitted is governed by SDG's modding documentation, available at https://docs.smartlydressedgames.com/en/stable/. Consult the current official documentation for SDG's current position. Do not rely on community summaries of SDG's policy — read the primary source.

Can I upload a reskin of another community modder's work if I credit them?

Attribution satisfies the attribution condition of CC-BY and similar licenses, but it does not automatically authorize creating a derivative work. For a derivative to be permissible, the original's license must include permission to create derivatives. CC-BY-ND, for example, requires attribution but prohibits derivatives — attribution alone does not make the derivative legal. If the original's license does not include derivative permission, or if the original has no stated license (and is therefore proprietary), you need explicit written permission from the rights holder.

Does fair use allow me to reskin without permission?

Fair use is a legal defense, not a license. It must be evaluated case-by-case against all four statutory factors. In most standard modding reskin scenarios, the fair use analysis does not strongly favor the reskin creator — particularly on the purpose-and-character factor (creative use, not transformative commentary) and the market-effect factor (the reskin may substitute for the original). 57 Studios does not advise relying on fair use without a strong factual basis for each of the four factors.

What if the original author is no longer reachable?

If the original author cannot be reached, their copyright has not lapsed. Treat the work as proprietary. If you cannot obtain permission and the work's license does not authorize the use, replace the elements with independently authored content or find a licensed alternative. An unreachable rights holder is not a blank check.

Does using a CC-BY-SA asset force my entire mod to be CC-BY-SA?

The CC-BY-SA ShareAlike condition requires that derivative works be licensed under CC-BY-SA or a compatible license. This applies specifically to the derivative work that incorporates the CC-BY-SA asset — it does not necessarily apply to every other mod you have published or will publish. For the specific mod that includes the CC-BY-SA asset, the distribution must be compatible with CC-BY-SA terms. This effectively means the mod's assets cannot be declared proprietary if they constitute a derivative of the CC-BY-SA source.

Is a new .dat configuration for an existing mod a derivative work?

A .dat configuration file is a collection of parameters and values. Configuration data with minimal creative expression is generally not protectable by copyright — it is functional, not creative. A new .dat configuration for an existing mod item is therefore unlikely to constitute a derivative work in the copyright sense, though the specific facts matter. The mesh, texture, and prefab that the .dat references may still be derivative if they are taken from the original mod.

What if the community mod's author explicitly says "no reskins" in their description?

A Workshop description stating "no reskins" or "no derivatives" is a clarification by the rights holder of their position. For mods with no explicit license, this statement reinforces the default "all rights reserved" position. For mods with a permissive license (e.g., CC-BY), a description-based "no reskins" statement does not override the license — once a permissive license has been granted, the licensor cannot unilaterally restrict what the license permits for existing distributions. However, the rights holder may revoke the license for new distributions by updating the mod's terms. Respect the rights holder's stated intent. If they say no reskins, contact them to ask for permission rather than relying on the license's technical terms to override their stated preference.

What is the difference between inspiration and copying?

Inspiration means that a prior work influenced the direction, aesthetic, or concept of a new work — without the prior work's actual expressive elements being incorporated into the new work. Copying means the prior work's actual expression — its specific geometry, texture composition, sound recording, animation sequences — appears in the new work. Copyright protects expression, not ideas or concepts. Being inspired by a mod's weapon design and creating a new weapon that shares a similar concept is not copying. Importing a mesh from the mod and repainting it is copying.

Does a permission message on Discord count as written permission?

A Discord message from the verified rights holder that clearly grants the requested permission constitutes written permission in a practical sense. It is not a formal legal document, but it documents the holder's consent. Save the message with a timestamp, the holder's username, and the specific permission granted. This documentation is sufficient for the 57 Studios asset log standard. If the holder later disputes the permission, the saved message is the evidence of consent.

Can I use a mod's sounds or animations without using its visual assets?

Sound recordings and animation clips are independently copyrightable works, separate from the visual mesh and texture. Using a mod's audio without permission is infringement of the audio copyright, regardless of whether the visual assets are used. Using a mod's animation clips without permission is potentially infringement of the animation copyright. The derivative work analysis applies to each type of asset independently.

What does "recast, transformed, or adapted" mean in the copyright definition?

"Recast" means presenting the same work in a different format (e.g., converting a 3D mesh to a 2D rendering). "Transformed" means substantially altering the work's presentation while retaining its expression (e.g., significantly modifying a texture while retaining its base composition). "Adapted" means modifying the work for a new context or use (e.g., adapting a real-world weapon mesh for a game mod). The three terms are overlapping and are interpreted broadly. If a new work incorporates a prior work's expression in any of these ways, it is likely a derivative work.

How do I know if an animation rig is independently authored or copied?

In practice, animation rigs for similar weapon types share structural similarities because the underlying anatomical constraints are the same (the weapon has a trigger, a barrel, a magazine well). Structural similarity alone does not establish copying. Copying is established when the specific bone names, hierarchy, and weight painting data from one rig are found in another. If you authored your rig from scratch — even if it resembles other rigs structurally — it is an independent work. If you exported or copied another mod's rig data and used it in your project, it is a derivative.

Cross-references

• Asset Licensing and Attribution — the previous article; covers the licensing frameworks that determine whether derivative use is permitted.
• How the Steam DMCA Process Works — covers what happens when a derivative work dispute escalates to a formal takedown notice.
• Smartly Dressed Games Modding Policy — the next article; covers SDG's documented position on community content and vanilla asset use.
• Steam Workshop Submission — covers the Workshop publication process, including description formatting for attribution and derivative disclosures.
• Official Unturned modding documentation: https://docs.smartlydressedgames.com/en/stable/ — SDG's primary reference for vanilla asset policies, Workshop requirements, and the modding framework that defines what community creators may do with vanilla Unturned content.
• Unturned on Steam: https://store.steampowered.com/app/304930/Unturned/ — the Steam store page; gateway to the Workshop and the subscription base for community mods. The Workshop is the primary distribution channel for Unturned mods and operates under Valve's DMCA-compliance obligations, making it the platform through which community copyright disputes are formally adjudicated.

Cross-reference: derivative works and the DMCA process

When a derivative work dispute is not resolved through direct communication, the rights holder may escalate to a formal DMCA takedown notice. Understanding the relationship between the derivative works analysis in this article and the DMCA process is important for modders on both sides of a dispute.

A DMCA notice is appropriate when: (1) the rights holder has a good-faith belief that the uploaded content infringes their copyright, (2) the infringement is the incorporation of the rights holder's copyrightable expression without authorization, and (3) direct contact with the uploader has not resolved the issue or is not reasonably possible.

A DMCA counter-notice is appropriate when: (1) the uploader has a good-faith belief that the content was removed as a result of a mistake or misidentification, (2) the uploader has authorization for the use (license, written permission, or a strong fair use basis), and (3) the uploader agrees to the jurisdiction of the Federal District Court.

The derivative works analysis in this article is directly relevant to both the notice (does the derivative infringe?) and the counter-notice (does the modder have authorization?). Modders who have documented their derivative relationships per the 57 Studios checklist are in a much stronger position to evaluate both questions accurately and to respond to notices promptly with clear evidence. See How the Steam DMCA Process Works for the full process, timelines, and documentation requirements.

Closing note

Derivative works and reskins occupy the most legally complex territory in the Unturned™ modding ecosystem. The legal framework is not designed for the modding context — it was designed for commercial publishing, academic adaptation, and professional creative industries. Applied to community modding, it produces results that are sometimes counterintuitive: a heavily modified reskin may still be a derivative work, while a mod that is visually similar to an existing one may be entirely independent.

57 Studios approaches this complexity through process: the derivative-works checklist, the asset log, the permission request template, and the Workshop description documentation standard. These processes are not bureaucratic obstacles — they are the mechanisms by which 57 Studios maintains clear authorization for everything it publishes, protects the rights of original authors in the community, and avoids the community reputation and legal risks that accompany unauthorized derivative work.

The modding community's trust in 57 Studios as a publisher depends in part on this integrity. Modders who discover a 57 Studios mod that incorporates their work without authorization should contact 57 Studios directly. The issue will be investigated and resolved promptly, either by obtaining retroactive permission, replacing the element, or removing the mod from distribution.

Document history

Version	Date	Author	Notes
1.0	2025-08-14	57 Studios	Initial publication. Derivative works framework and reskin analysis.
1.1	2025-11-20	57 Studios	Added derivative-works checklist and permission request template.
2.0	2026-05-18	57 Studios	Major revision. Added transformative use section, Workshop policy section, FAQ expansion, appendices.
2.1	2026-05-18	57 Studios	Added reskin scenario analysis, pre-publication audit table, commercial mod guidance, license-condition interaction section, derivative documentation format, DMCA cross-reference section, copyright thickness framework, collaborative mod management section, and community norms discussion.