What is Modding?
Modding is the practice of creating, modifying, or extending the content of an existing video game. The term derives from "modification" and encompasses everything from small cosmetic adjustments to complete reimaginings of a game's core mechanics. For Unturned™, modding is a core pillar of the game's ongoing relevance, and studios such as 57 Studios™ produce professional-grade mods that are sold and distributed to a global player base. This article establishes a complete working definition of modding, surveys the categories of mods, and explains how mods reach end users.
The article that follows is the second foundational orientation document in the 57 Studios Modding Knowledge Base. The first orientation article, What is Unturned?, establishes the game itself and the ecosystem around it. The present article establishes the practice of modding as a discipline, the categories of work that the discipline encompasses, the distribution channels through which mod work reaches end users, and the economic model that supports professional mod studios. Together, the two articles form the conceptual scaffolding on which every later technical chapter rests.
A note on scope. This article is descriptive rather than prescriptive. The aim is to convey what modding is and how the practice fits into the broader ecosystem, not to instruct the reader on any specific tool or technique. The instructional chapters of the knowledge base begin with the file-system foundations (What is a File? and What is a Folder?) and proceed through the modding-tool installation chapters, the topical chapters on each mod category, and the commercial-distribution chapters.
Prerequisites
- Completion of What is Unturned?
- Familiarity with the concept of a video game
- Approximately thirty minutes of uninterrupted reading time
- A willingness to think about modding as a discipline rather than as a single activity
What you'll learn
- The historical origins of game modding
- The five major categories of mod content
- The primary distribution channels for Unturned mods
- The economic models that support professional mod development
- How 57 Studios fits into the broader Unturned modding ecosystem
- The structural differences between hobbyist and commercial mod publishing
- The relationship between modding and the broader games industry
- The full lifecycle of a published mod from authoring to long-term maintenance
- The legal and ethical foundations of responsible mod authoring
Background
Game modding predates the modern internet. The earliest widely recognized modding community formed around id Software's Doom in 1993, when players began creating custom WAD files containing new levels, enemies, and graphics. The release of editing tools and the open format of WAD files turned Doom into the first major platform for community-created content.
The Doom modding community established several practices that the broader modding world subsequently inherited. The open file format permitted community-built editing tools to flourish, which lowered the entry barrier for new mod authors. The free distribution of mods through bulletin board systems and early internet forums established the cultural expectation that mods are shared rather than hoarded. The willingness of id Software to publicly endorse the modding community as a desirable extension of the base game established the cultural expectation that publishers would treat modders as collaborators rather than as adversaries. Each of these practices remains foundational to modern modding communities, including the Unturned ecosystem.
As shown in the flowchart above, modding has evolved continuously over three decades. Each major modding platform has built on lessons from the previous generation, with Unturned representing a modern continuation of that lineage that combines official tool support with community distribution infrastructure.
An extended timeline of modding history
The headline flowchart compresses many smaller events into the five labeled stages. The expanded timeline below records the principal inflection points that shaped the modern modding ecosystem.
The timeline shows that modding has matured across multiple generations of games. Each major platform shift produced lessons that subsequent platforms inherited: Doom established the practice; Half-Life established the publisher partnership; Morrowind established first-party editor tooling; Minecraft established the community-scale ecosystem; Steam Workshop established the universal distribution platform; Unturned added the permissive commercial-publishing layer on top of all of the above.
Did you know?
Counter-Strike, one of the most commercially successful multiplayer titles in history, began as a Half-Life mod created by two community developers. The mod was eventually acquired by Valve and turned into a standalone product. Many beloved games have similar origins as community mods that grew into full releases.
Did you know?
The Morrowind Construction Set, shipped by Bethesda in 2002, was the first widely-used first-party editor tool for a major commercial RPG. The toolset enabled a generation of mod developers who later founded studios, became Bethesda engineers, or built careers across the broader industry. The pattern of first-party editor tools driving long-term modding communities was established by this release and has since been replicated across many subsequent titles, including Unturned.
Categories of mods
Mods fall into several broad categories. Most professional mod developers specialize in one or two categories rather than working across all of them.
Items
Item mods add new weapons, tools, clothing, food, medical supplies, ammunition, attachments, and other inventory objects to the game. In Unturned, items are defined by configuration files and accompanied by 3D models, textures, and icons. Item mods are the most common entry point for new mod developers because they involve a manageable scope and produce visible results quickly.
The item category itself is internally diverse. Weapons require ballistic configuration and fire-mode behaviour; clothing requires equip-slot definitions and visual fitting; consumables require effect definitions and inventory-stack behaviour. A new mod developer entering the item category typically begins with a configuration-only reskin of an existing item, progresses to a custom-icon item, then to a custom-texture item, and ultimately to a custom-mesh item. Each step in the progression introduces one new technical skill while building on the foundation of the previous step.
Vehicles
Vehicle mods add new cars, trucks, motorcycles, boats, helicopters, and other transports. Vehicles are more complex than items because they require physics tuning, animation, multiple seating positions, and sometimes weapon mounts. Vehicle mods are popular content on roleplay servers, where custom vehicles establish the visual identity of the server.
A vehicle mod is typically a multi-week to multi-month project depending on scope. The bare minimum scope is a single seating position, a single drivable configuration, and a single visual configuration. The maximum scope is a multi-variant vehicle pack with bespoke physics, custom dashboard animations, weapon mounts, lighting configurations, and full localisation. Established commercial mod studios typically position their vehicle portfolios in the upper half of the scope range; the differentiation versus free Workshop content is the production value, the maintenance commitment, and the bespoke customisation options available to server operators.
Maps
Map mods are entirely new playable worlds. Creating a map involves terrain sculpting, asset placement, lighting design, navigation mesh generation, and balance testing. Maps are the largest and most time-intensive category of mod, often taking months or years to produce.
Map mods occupy a special position in the Unturned ecosystem. A map is the canvas on which every other mod category is displayed; a server running a custom map establishes its identity through that map more directly than through any other content choice. Commercial map mods are typically licensed by server operators on a per-server or per-population basis and represent some of the highest-value transactions in the commercial mod marketplace.
Server-side scripts
Server-side mods modify gameplay behavior on a community server without requiring clients to download anything. Common examples include economy plugins, custom roleplay systems, anti-cheat enhancements, and administrative tools. Server-side mods are written in C# and run on the OpenMod or RocketMod plugin frameworks.
The server-side category is the dominant entry point for engineering-trained mod developers. The category does not require 3D modelling, texture authoring, or any visual-arts skill; the entire workflow happens within a C# integrated development environment. The customer base (server operators) values reliability, support quality, and feature responsiveness, all of which align with the strengths of an engineering-trained developer.
Total conversions
A total conversion replaces large portions of the base game's content to produce what is effectively a new game running on the original engine. Total conversions might replace all weapons, all vehicles, the map, the user interface, and the core game systems. They represent the highest level of ambition in mod development.
Total conversions are the rarest mod category because they require fluency across every other category. A single developer authoring a complete total conversion may spend two to five years on the project. Most total conversions are team efforts; established commercial mod studios occasionally produce total conversions as flagship projects that anchor their portfolio. The commercial value of a successful total conversion can exceed the cumulative revenue from a year of single-category releases, but the risk profile is correspondingly high.
The pie chart above shows the approximate distribution of published Unturned mods by category. Items dominate because of their lower complexity, while total conversions are rare because of the scope of work involved.
Comparison of mod categories
| Category | Typical scope | Skill level | Tool dependencies | Distribution |
|---|---|---|---|---|
| Items | Hours to days per item | Beginner | Unity Editor, image editor | Workshop or store |
| Vehicles | Days to weeks per vehicle | Intermediate | Unity Editor, Blender | Workshop or store |
| Maps | Months to years | Advanced | Unturned Map Editor | Workshop or store |
| Server-side scripts | Days to weeks | Intermediate to advanced | C# IDE, OpenMod | Direct download |
| Total conversions | Months to years | Expert | All of the above | Workshop or store |
Pro tip
New mod developers should begin with a single item mod, complete it end to end including publication, and only then move to more complex categories. The discipline of finishing a project is more valuable than the technical complexity of the work itself.
Extended comparison across additional dimensions
The headline comparison covers the foundational dimensions. The expanded comparison below addresses additional dimensions that affect category selection for new mod developers.
| Category | Typical revenue per release | Maintenance load | Audience reach | Portfolio diversification value |
|---|---|---|---|---|
| Items | Low to moderate | Low | Broad | Moderate (high volume offsets low per-release revenue) |
| Vehicles | Moderate to high | Moderate | Moderate (roleplay-focused) | High (visual differentiation) |
| Maps | High | High | Moderate to broad | Very high (anchor content for a server) |
| Server-side scripts | Moderate to high | High (continuous updates) | Moderate (server-operator focused) | High (recurring-revenue base) |
| Total conversions | Very high (when successful) | Very high | Variable | Defining portfolio anchor |
| Translation / localisation | Low | Low | Region-specific | Useful complement, low risk |
| Sound / music | Low to moderate | Low | Variable | Useful complement |
The extended comparison shows that no single category dominates across all dimensions. The most resilient commercial mod studio portfolios contain a mix of categories: a steady stream of item releases for visibility and recurring revenue, a smaller number of vehicle releases for differentiation, occasional map releases as anchor content, and a portfolio of server-side plugins for the recurring-revenue base.
The flowchart above illustrates the recommended progression by primary skill background. Each entry point converges on the broader portfolio over time. The total conversion endpoint is reachable from any entry path but is not a recommended early scope.
Distribution channels
Unturned mods reach end users through three primary channels.
Steam Workshop
The Steam Workshop is the official mod distribution platform integrated into Steam. Players subscribe to a Workshop mod, and Steam automatically downloads and installs it. Workshop mods are free to end users. Mod developers do not receive direct revenue from Workshop distribution, but the reach of the platform is unmatched.
Steam Workshop serves three functions for a commercial mod studio: reputation building, free-tier customer acquisition, and discoverability. A free Workshop release introduces the studio's quality standards to a broad audience; some fraction of that audience converts to paying customers for the premium variants of the same content. The Workshop is not a revenue channel directly but is a documented driver of revenue on the commercial channels that follow.
Third-party marketplaces
Several independent marketplaces sell premium Unturned mods. 57 Studios produces and sells professional mods through such marketplaces, particularly Tebex. Mods sold through these channels typically offer higher production value, ongoing support, and content that would not be commercially viable to give away. Server operators are the primary customers for paid mods.
Tebex is the dominant marketplace for Unturned commercial mods. The platform handles payment processing, customer-facing storefront pages, license-key delivery, and customer-support routing. Mod studios configure their storefronts, upload their mods, and let the platform handle the operational overhead. The platform fee is a percentage of each transaction; the remaining revenue is paid to the studio on a regular settlement schedule.
Direct distribution
Some mods are distributed directly by their authors through Discord servers, GitHub repositories, or private storefronts. Direct distribution offers maximum control to the developer but requires the developer to handle delivery, updates, and customer support without platform support.
Direct distribution is the dominant channel for two specific subsets of the mod ecosystem: open-source server-side plugins that the developer wants to keep entirely free, and bespoke commercial work where the developer maintains a direct contractual relationship with a single server operator. For typical commercial publishing, the established platforms (Workshop for free, Tebex for paid) are the dominant channels.
Best practice
Most successful Unturned mod developers maintain a presence on multiple distribution channels: free showcase mods on the Workshop to build reputation, and premium mods on a third-party storefront to generate revenue.
Decision flowchart: choosing a first mod project
The decision flowchart above helps a new mod developer select an appropriate starting project based on their existing skills and interests. Each path leads to a well-scoped first project.
The economics of professional mod development
Professional Unturned mod studios such as 57 Studios operate on a recurring sales model. Server operators purchase mods, often with optional update subscriptions, and use those mods to differentiate their servers from competitors. A successful mod studio produces a portfolio of mods across multiple categories and supports them with regular updates.
The economic model rewards quality, consistency, and customer service. Mods that ship with bugs, lack documentation, or fail to receive timely updates lose customers quickly. Mods that demonstrate polish and reliability build long-term reputation and recurring revenue.
The sequence above shows the full commercial-revenue loop. The free Workshop release plants the seed; the player encounter on a community server creates the operator demand; the commercial marketplace converts the demand into revenue. The loop relies on multiple touchpoints across the ecosystem, and the studio that maintains presence across all touchpoints captures the most revenue.
Common mistake
New developers sometimes assume that publishing a mod is the end of the project. In professional mod development, publication is the beginning. Ongoing updates, bug fixes, customer support, and version compatibility maintenance often take more total hours than the original development.
Revenue model details for new commercial mod developers
The table below summarises the documented revenue model for established commercial Unturned mod studios. The figures are illustrative ranges; substantial variation by studio, portfolio, and reach is normal.
| Revenue dimension | Documented range | Notes |
|---|---|---|
| Single-item commercial mod license fee | Low single-digit US dollars per server | Often bundled into packs |
| Vehicle mod license fee | Mid single-digit to low double-digit US dollars | Higher for multi-variant packs |
| Map mod license fee | Mid double-digit to low triple-digit US dollars | Highest per-license revenue |
| Server-side plugin license fee | Mid single-digit to mid double-digit US dollars | Often subscription rather than one-time |
| Platform fee on commercial channels | High single-digit percent | Tebex and equivalent marketplaces |
| Active server-operator customer base | Hundreds to low thousands | Varies by studio reputation |
| First-year revenue for a new studio | Low to mid triple-digit US dollars | Reputation building phase |
| Mature-year revenue for an established studio | Mid four-digit to low six-digit US dollars | Sustained operation |
The progression from new-studio first-year revenue to mature-year revenue typically takes two to five years of sustained portfolio building. The dominant pattern across established studios is to treat the first year as portfolio investment rather than revenue generation, the second year as proof-of-concept revenue, and the third year onward as sustained commercial operation.
Did you know?
57 Studios began publishing commercial Unturned mods in 2019 and has since grown into one of the established professional mod studios in the ecosystem. The studio's portfolio spans items, vehicles, maps, and bespoke roleplay-server branding work, and is operated by the founder as a solo studio with occasional contractor support.
Advanced considerations
The line between modding and original game development has become increasingly blurred. Many professional game developers begin their careers in modding communities, where they learn industry-standard tools, build portfolios, and develop reputations. Modding can be a viable long-term career path, particularly for developers who specialize in technical art, game scripting, or live-service content production.
The career-portability of mod development skill is one of the most documented benefits of the field. Unity proficiency, asset-pipeline experience, customer-facing publishing experience, and community-management experience all translate directly into junior game-development hiring criteria. Mod developers who pursue commercial publishing additionally acquire small-business operation experience, payment-processing familiarity, and customer-support discipline, all of which are valuable across multiple adjacent career paths.
Critical warning
Always respect the intellectual property rights of original game developers, asset creators, and other modders. Distributing content that infringes on another party's copyright can result in legal action, account bans, and permanent removal from distribution platforms.
Critical warning
Never publish a mod that contains malicious code, undisclosed remote-execution payloads, data-exfiltration scripts, or any behaviour outside the published documentation. The Unturned community and Smartly Dressed Games take such incidents extremely seriously. Documented infractions have resulted in permanent platform bans, public community blocklist entries, and in egregious cases legal consequences.
Common mistake
Treating customer support as a low-priority afterthought. The dominant pattern across established commercial mod studios is to treat customer-support responsiveness as a first-class operational discipline. Server operators choose between competing mod studios partly on the perceived support quality, and the studio with the better support reputation captures more long-term recurring revenue.
The mod publishing lifecycle
A published mod has a multi-phase lifecycle that extends well beyond the initial authoring. The phases are summarised in the flowchart below.
Each phase has a distinct character and a distinct set of operational requirements.
| Phase | Duration | Principal activity | Operational cost |
|---|---|---|---|
| Concept | Days to weeks | Design and scope decisions | Low (creative work only) |
| Authoring | Weeks to months | Production work on assets and code | High (the bulk of the project) |
| Internal testing | Days to weeks | Verification across environments | Moderate |
| Publication | Hours to days | Storefront listing, Workshop upload | Low |
| Launch support | Weeks to months | Bug reports, first-customer onboarding | High |
| Maintenance | Months to years | Patch releases, customer support | Sustained |
| Engine refresh updates | Weeks per refresh | Rebuild against new engine version | Episodic high |
| Long-term archive or retirement | Years | Decision to continue or sunset | Strategic |
The total cost of a published mod across its full lifecycle typically exceeds the initial authoring cost by a factor of two to three. New mod developers entering commercial publishing should plan around this multiplier rather than around the authoring cost alone.
Pro tip
The single most impactful investment a new commercial mod developer can make in long-term success is establishing a documented customer-support workflow from the first commercial release. The workflow does not need to be elaborate; a single dedicated Discord channel with response-time expectations and a public changelog suffices. Studios that establish the workflow early retain customers; studios that defer the workflow lose customers and reputation simultaneously.
The relationship between modding and the broader games industry
Modding is not a separate world from the broader games industry; the two are interconnected at multiple levels. Many professional game developers got their start in modding communities. Several major commercial games began as community mods (Counter-Strike, Defense of the Ancients, Team Fortress, and many more). Modding tools are often built or maintained by the same engineering teams responsible for the base-game tools. Industry hiring increasingly considers mod portfolios as relevant prior work, particularly for technical-art and live-service-content roles.
The diagram shows the bidirectional flow between the modding community and the broader industry. A modder who pursues an industry career can later return to the modding community as a senior contributor; an industry engineer who joins the modding community can elevate the technical standards of the broader ecosystem. The two roles are not mutually exclusive, and many established commercial mod studios contain at least one individual whose career has spanned both sides.
Frequently asked questions
Do I need permission from Smartly Dressed Games to make Unturned mods?
No explicit permission is required for personal or community mods. Smartly Dressed Games provides official tools and supports the modding community. Commercial mod sales should follow the policies published by Smartly Dressed Games on their official channels.
Can I make money from Unturned mods?
Yes. Several marketplaces support paid Unturned mod sales, and many developers earn substantial recurring revenue from this work. Building a customer base takes time and consistent output. The dominant model is recurring server-operator licensing through commercial storefronts such as Tebex.
Is modding considered cheating?
No. Modding adds new content or modifies single-player or server-side experiences. Cheating, by contrast, involves modifying game code to gain unfair advantages on servers that prohibit such modifications. The two are distinct activities. Reputable mod studios publish only content that is sanctioned by the game's modding policy and that does not undermine the integrity of server-side gameplay.
What if my mod breaks after a game update?
Game updates occasionally break mods. Professional mod developers monitor official update channels and release compatibility patches promptly. Free mods may be abandoned and stop working over time, which is one reason server operators often prefer paid mods with active support.
How do I price a commercial mod?
Pricing depends on the category, the production value, and the competitive landscape. The documented ranges in the revenue model section of this article are useful starting points; cross-reference against the published prices of established mod studios on Tebex to calibrate. The dominant pricing mistake among new commercial mod developers is to underprice; correcting a low price later is harder than starting at a competitive price.
How do I handle customer support as a solo mod developer?
Establish a single Discord channel for support requests, publish a clear response-time expectation, and write a brief FAQ for the most common questions. Most established commercial mod studios are solo or near-solo operations and converge on this lightweight support model. The discipline of responding within the published response window is the principal differentiator between studios that retain customers and studios that lose them.
What documentation should accompany a commercial mod?
At minimum, the documentation should include an installation guide, a configuration reference, a changelog, and known-issue notes. Established commercial mod studios additionally publish a brief video walkthrough, a roadmap of planned features, and a public changelog history. The documentation effort scales with the complexity of the mod; a simple item mod may require only a one-page README, while a full vehicle pack may require a multi-page configuration reference.
Should I open-source my mod?
It depends on the mod and the goals. Free Workshop releases benefit from open-source companion code for plugin work, particularly when the audience includes other mod developers. Commercial releases typically remain closed-source to protect the revenue model. A mixed strategy (open-source tooling, closed-source assets) is common across established commercial studios.
How do I localise a mod for non-English-speaking markets?
Unturned uses configuration files for in-game text, which are straightforwardly translated by separate localisation files. The dominant first-language targets beyond English are Portuguese (for the Brazilian roleplay corridor), Spanish (for the broader Latin American market), Russian (for Eastern Europe and Russia), and German (for Western Europe). Established commercial mod studios maintain a translator network or use professional translation services to produce the localisation files; the revenue uplift from localisation is documented and substantial.
What happens to my mods if I stop developing?
A published mod continues to exist on Steam Workshop and commercial storefronts indefinitely unless explicitly removed. A mod that stops receiving updates will eventually stop working with a future engine refresh; the documented half-life of an abandoned mod is approximately two to three years from the last update. Established commercial mod studios maintain a sunset protocol for retired mods that includes one final update, a public retirement notice, and a recommended-replacement listing.
Can I collaborate with other mod developers?
Yes, and the practice is encouraged. Many established commercial mod studios began as collaborative duos or small teams. Discord channels, the Smartly Dressed Games forum, and the Steam community hub all support modder-to-modder networking. Collaboration agreements should be documented in writing from the first significant project to avoid later ambiguity about revenue splits and intellectual-property ownership.
How do I know if my mod is high enough quality to publish commercially?
The dominant heuristic is to publish a free Workshop variant first and observe community reception. A free release that generates positive ratings, sustained downloads, and at least a handful of unsolicited server-operator licensing inquiries is a strong signal that a commercial variant is viable. Publishing a commercial mod without first validating community reception is a documented common mistake among new commercial mod developers.
Best practices
- Choose a focused first project that can be completed in two to four weeks
- Document your mods thoroughly so end users can install and use them without external support
- Build a portfolio of small completed mods before attempting a large project
- Engage with the Unturned modding community to learn from established developers
- Respect the intellectual property of other creators
- Plan the first year of commercial publishing as portfolio investment rather than revenue generation
- Treat customer support as a first-class operational discipline from the first commercial release
- Localise to at least Portuguese, Spanish, and Russian alongside English for any commercial mod
- Maintain a documented customer-support workflow even at solo-studio scale
- Establish written collaboration agreements with any contributor before significant work begins
- Validate commercial viability through a free Workshop release before publishing a commercial variant
- Audit every published mod against the no-malicious-code, no-stolen-assets, no-undisclosed-behaviour baseline before each release
Appendix A: Extended mod-category scope ladder
The scope ladder below describes the progression from the smallest viable mod scope to the largest. New mod developers should plan their first six to twelve months as a climb up the lower rungs, with later years devoted to the higher rungs as skill and portfolio mature.
| Rung | Scope | Approximate elapsed time | Skills required |
|---|---|---|---|
| 1 | Configuration-only item reskin | 1-2 weeks | Text editing, publishing workflow |
| 2 | Custom-icon item | 2-3 weeks | Image editing |
| 3 | Custom-texture item | 3-4 weeks | Image editing, Unity import |
| 4 | Custom-mesh item | 4-6 weeks | 3D modelling, UV unwrap |
| 5 | Item pack (5-10 items) | 6-10 weeks | All of the above, scope management |
| 6 | Server-side plugin (simple) | 2-4 weeks | C#, OpenMod conventions |
| 7 | Server-side plugin (complex) | 4-12 weeks | C#, deeper OpenMod knowledge |
| 8 | Single vehicle | 4-8 weeks | 3D modelling, physics tuning |
| 9 | Vehicle pack | 8-20 weeks | All of the above, pack-level design |
| 10 | Small map mod | 8-12 weeks | Terrain sculpting, asset placement |
| 11 | Medium map mod | 16-24 weeks | All of the above, navigation mesh |
| 12 | Large map mod | 24-52 weeks | All of the above, lighting design |
| 13 | Total conversion | 1-5 years | All of the above, design coherence |
The scope ladder is a planning aid, not a prescription. Most established commercial mod studios climb rungs 1 through 6 in their first year, rungs 7 through 10 in their second and third years, and consider rungs 11 through 13 only after a stable revenue base supports the multi-year time horizon.
Appendix B: Equipment and tooling recommendations for new mod developers
The equipment and tooling recommendations below complement the more hardware-focused recommendations in the What is Unturned? appendices. The focus here is on the software and process tooling that established commercial mod studios converge on over time.
| Tool category | Recommended tooling | Rationale |
|---|---|---|
| Source-asset version control | Git with LFS for binary assets | Recovery from accidental corruption |
| Project planning | Notion, Linear, or equivalent | Multi-month project visibility |
| Customer support | Dedicated Discord channel | Documented response cadence |
| Changelog publication | Public document or Discord channel | Customer-facing maintenance visibility |
| Internal testing | Local Unturned server instance | Per-build verification |
| Asset organisation | Disciplined folder structure (see What is a Folder?) | Multi-year project maintainability |
| Documentation | Markdown source committed alongside code | Co-evolution with the mod itself |
| Backup | External drive plus cloud snapshot | Multi-point-of-failure resilience |
| Image and texture authoring | Photoshop, Affinity Photo, or GIMP | Texture and icon work |
| 3D modelling | Blender (free) or Maya / 3DS Max (commercial) | Mesh authoring |
Best practice
The dominant pattern across established commercial mod studios is to establish source-asset version control before authoring the first commercial release. The investment is small (a few hours) and the payoff is enormous: recovery from corruption, ability to revert unwanted changes, and a permanent history of the mod's evolution. Git with LFS is the de facto industry standard for game-asset version control.
Appendix C: Historical context for the broader modding industry
The broader modding industry has gone through several distinct eras, each with its own dominant platforms, distribution channels, and economic models. The Unturned modding ecosystem inherits practices and assumptions from each era.
| Era | Approximate years | Dominant platform | Distribution | Economic model |
|---|---|---|---|---|
| Doom era | 1993-1997 | Doom | BBS, FTP | Free, hobbyist |
| Half-Life era | 1998-2003 | Half-Life | Game-developer-hosted | Free, hobbyist |
| Construction-set era | 2002-2010 | Morrowind, Oblivion | Modding-community sites | Free, hobbyist |
| Workshop era | 2012-present | Steam Workshop | Steam | Free, ecosystem-integrated |
| Commercial marketplace era | 2018-present | Tebex and equivalents | Independent storefronts | Paid, commercial |
The current Unturned modding ecosystem combines elements of the Workshop era (free distribution through Steam Workshop) and the commercial marketplace era (paid distribution through Tebex). The combination is one of the structural reasons the ecosystem has attracted a disproportionate number of professional commercial mod studios relative to the player base.
Did you know?
The transition from the construction-set era to the Workshop era was driven primarily by Valve's decision to integrate community-content distribution directly into Steam. Workshop launched in 2012 and within five years had become the dominant distribution channel for free mods across the entire Steam catalogue. The Unturned modding ecosystem launched into the Workshop era and inherited its conventions from the beginning.
Appendix D: Extended scenarios for first-mod selection
The scenarios below describe representative situations that new mod developers commonly encounter when selecting a first mod project. Each scenario is composed from documented patterns across the established commercial mod studios and the broader community.
Scenario 1: The roleplay player who wants a specific custom item
A roleplay player who participates in a community server and wants a specific custom item that does not exist (a particular firearm, a specific clothing piece, a stylised vehicle) is one of the dominant entry profiles. The player typically has a clear creative vision, a specific use case, and an established social context in which to test and refine the result.
The recommended entry path is the configuration-only or single-item custom-art mod that addresses the specific item. The player authors the mod, deploys it on the community server they participate in, and uses the live feedback to refine the result. The first mod typically completes within two to four weeks of part-time work. The community feedback loop is the principal advantage of this scenario; the player has a built-in testing audience that most new mod developers lack.
Scenario 2: The aspiring game designer building a portfolio
An aspiring game designer who wants to enter the games industry and is building a portfolio to support that career path is another recurring entry profile. The designer typically wants the broadest possible portfolio coverage to demonstrate adaptability to potential employers.
The recommended entry path is a series of small mods across multiple categories: a configuration-only item, a custom-art item, a small server-side plugin, and (after several months) a small map mod. The portfolio breadth is the principal benefit of this scenario; the designer demonstrates competence across the full mod-development workflow rather than depth in a single category. Industry hiring for technical-art and live-service-content roles values this breadth.
Scenario 3: The server owner who wants exclusive content
A server owner who runs a community server and wants exclusive custom content unique to their server is a recurring entry profile that often progresses into commercial publishing. The owner typically begins with bespoke content for their own server, recognises that other server operators face similar needs, and gradually transitions into a commercial mod studio operating model.
The recommended entry path is the bespoke custom content for the owner's own server, followed by progressive commercialisation as the portfolio grows. The owner-to-publisher transition is one of the most documented success paths in the commercial mod ecosystem; established studios that began this way include some of the most respected names in the community.
Scenario 4: The student exploring a future career direction
A student exploring a future career direction in game development, technical art, or live-service content production is a recurring entry profile. The student typically has time for sustained learning but limited spending capacity, and is using mod development as a low-cost on-ramp into the broader industry.
The recommended entry path is a sustained twelve-month learning arc across multiple mod categories, with periodic publication of completed work to build a public portfolio. The student treats the work as both skill acquisition and reputation building, with explicit attention to documenting each mod's authoring process for portfolio purposes. The published portfolio becomes the foundation for later industry job applications or commercial publishing transitions.
Appendix E: Compatibility matrix between mod categories and player segments
The compatibility matrix below shows which mod categories are most relevant to which player segments. The matrix is intended as a planning aid for new mod developers selecting an entry category.
| Mod category | Roleplay players | PvP players | Survival players | Singleplayer players | Server operators |
|---|---|---|---|---|---|
| Items (cosmetic) | High relevance | Moderate | Low | Low | High (server identity) |
| Items (functional) | High | High | High | Moderate | High |
| Vehicles | Very high | Moderate | Moderate | Low | Very high |
| Maps | Very high | High | High | Moderate | Very high |
| Server-side plugins | Very high | Moderate | Low | Not applicable | Very high |
| Total conversions | Variable | Variable | High | High | Variable |
| Translation / localisation | High | High | High | High | High |
| Sound / music | Moderate | Low | Low | Moderate | Moderate |
The matrix shows that vehicles, maps, and server-side plugins have the highest relevance to the dominant player segment (roleplay players) and to the principal commercial customer base (server operators). New commercial mod developers should weight their portfolios toward these high-relevance categories.
Appendix F: Troubleshooting flow for first-mod problems
The flowchart below addresses the most common first-mod authoring problems that new mod developers encounter. The flow is a triage entry point; the dedicated troubleshooting chapter in the modding-tools section of this knowledge base provides the deep coverage.
The flowchart is the recommended triage entry point. The dedicated troubleshooting chapter provides deeper coverage for each branch.
Best practice
Maintain a personal troubleshooting notebook from the first mod onward. The notebook accumulates into a substantial personal reference within months and becomes a documented onboarding aid for any future collaborator. Established commercial mod studios maintain shared studio-level troubleshooting notebooks as a standing operational asset.
Appendix G: Benchmark table for first-mod productivity expectations
The benchmark table below summarises documented first-mod productivity figures across the established commercial mod studios and the broader community. The figures are intended as a planning aid; substantial variation around the figures is normal.
| Mod scope | First-mod elapsed time | Hours per week assumed | Skill-acquisition focus |
|---|---|---|---|
| Configuration-only item reskin | 1-2 weeks | 8-12 | Configuration format, publishing workflow |
| Custom-icon item | 2-3 weeks | 8-12 | Image-editor workflow, icon design |
| Custom-texture item | 3-4 weeks | 8-12 | Texture authoring, Unity asset import |
| Custom-mesh item | 4-6 weeks | 8-12 | 3D modelling, UV unwrap |
| Server-side OpenMod plugin (simple) | 2-4 weeks | 8-12 | C# fundamentals, OpenMod conventions |
| Server-side OpenMod plugin (complex) | 4-12 weeks | 8-12 | Deeper OpenMod knowledge, design |
| Single vehicle | 4-8 weeks | 8-12 | Vehicle physics, animation, seats |
| Small map mod | 8-12 weeks | 8-12 | Terrain sculpting, asset placement |
| Total conversion | 1-5 years | Full-time | All of the above plus design coherence |
The first-mod elapsed times are part-time figures. Full-time mod development compresses each figure by approximately 2.5x, though documented diminishing returns set in beyond 30 hours per week.
Did you know?
The documented diminishing returns beyond 30 hours per week of mod development are attributed to the cognitive load of sustained creative and technical work, not to any lack of time. Established commercial mod studios that ship at the highest cadences typically pace their output at 25-32 hours per week per developer and produce more measurable output per calendar week than studios that attempt 50+ hour weeks.
Appendix H: Glossary of modding terminology
The glossary below defines the modding-specific terminology that recurs throughout the 57 Studios Modding Knowledge Base. The glossary complements the foundational terminology glossary in What is Unturned?; together the two glossaries cover the most common terms a new mod developer encounters in the foundational chapters.
| Term | Definition |
|---|---|
| Asset bundle | A packaged collection of Unity assets in .unity3d format, loaded by the game at runtime |
| Authoring | The act of creating mod content (assets, configuration, code) |
| Bundle | Shorthand for asset bundle |
| Changelog | A documented record of changes between mod releases |
| Commercial mod | A mod sold through a third-party marketplace such as Tebex |
| Configuration file | A text file (typically .dat or .json) defining the properties of an in-game entity |
| Customer support | The ongoing operational discipline of responding to customer inquiries about a mod |
| Direct distribution | Mod distribution outside of the established platforms, typically through Discord or GitHub |
| End user | A player who installs and plays mods, distinct from a server operator |
| Engine refresh | A Smartly Dressed Games engine version update, often accompanied by a Unity version bump |
| Free mod | A mod published at no cost, typically through Steam Workshop |
| License fee | The fee paid by a server operator to license a commercial mod for use on a server |
| Maintenance | The ongoing operational discipline of updating a published mod over time |
| Marketplace | A commercial distribution platform such as Tebex |
| Mesh | The 3D geometry of an item, vehicle, or map asset |
| Mod loader | The component of the game responsible for discovering and loading installed mods |
| Modding API | The set of programmatic interfaces exposed by the game for mod use |
| OpenMod | A C# server-side plugin framework for Unturned |
| Plugin | A server-side mod that modifies gameplay behaviour without client-side download |
| Portfolio | The collection of published mods that a developer or studio has produced |
| Publication | The act of releasing a completed mod through a distribution channel |
| RocketMod | An earlier C# server-side plugin framework, gradually superseded by OpenMod |
| Roleplay server | A community server running custom mods to support persistent character-driven play |
| Server operator | The person or entity running a community server |
| Server-side mod | A mod that runs only on the server, with no client-side download required |
| Showcase mod | A free mod published to demonstrate quality and build reputation |
| Steam Workshop | The official mod distribution platform integrated into Steam |
| Storefront | A commercial mod distribution page, typically hosted on Tebex |
| Tebex | The dominant third-party commercial mod marketplace |
| Texture | A 2D image applied to the surface of a 3D mesh |
| Total conversion | A mod that replaces large portions of base-game content |
| Unity Editor | The development environment used to build Unity-based mods |
| Unity version | The specific Unity Editor release that the current Unturned build targets |
| Workshop | Shorthand for Steam Workshop |
The glossary above is the foundational modding-specific reference. A more detailed glossary covering advanced topics is maintained in the reference chapters; new mod developers do not need to consult the advanced glossary until they have completed the foundational chapters.
Appendix I: The 57 Studios mod release cadence reference
The release cadence reference below documents the standing publication schedule that 57 Studios maintains across its mod portfolio. The schedule is shared as a reference template for new commercial mod developers establishing their own release cadences; the specific timing should be calibrated to the developer's own production capacity and customer base.
| Cadence dimension | 57 Studios standard | Rationale |
|---|---|---|
| New-mod release frequency | One new commercial mod per 4-8 weeks | Sustained portfolio growth without quality compromise |
| Patch release frequency | Within 1-2 weeks of a verified bug report | Customer confidence in maintenance quality |
| Engine-refresh response | Within 2-4 weeks of a documented engine refresh | Continued mod compatibility |
| Changelog publication | Public within 24 hours of every release | Customer-facing transparency |
| Customer-support response time | Within 24 business hours | Documented customer expectation |
| Storefront page refresh | Quarterly review of every active listing | Continued discoverability |
| Localisation release cadence | Within 4-6 weeks of the English release | Multi-region addressability |
| Showcase Workshop release | Concurrent with each commercial release | Reputation building |
| Roadmap publication | Quarterly forward-looking roadmap | Customer planning visibility |
The cadence shown is the documented operational rhythm of an established commercial mod studio. New commercial mod developers should not attempt to match this cadence in the first year; the cadence is the steady-state result of multiple years of operational refinement, not the starting point.
The sequence above shows the full release-and-support loop. The loop repeats for every release and every customer-reported issue; the cumulative effect is the studio's operational reputation, which directly feeds new-customer acquisition.
Pro tip
A new commercial mod developer should aim for a documented one-week customer-support response window from the first commercial release. The window does not need to be 24 hours immediately; the discipline of meeting a documented window is what builds reputation. Studios that publish a one-week window and reliably meet it outperform studios that publish a 24-hour window and miss it.
Common mistake
Attempting to match an established studio's release cadence in the first year. The established cadence is the result of years of operational refinement; attempting to replicate it from a standing start produces burnout, missed releases, and reputational damage. The recommended first-year cadence is one commercial release per quarter, with patch releases on demand. Cadence scales up as the operational capacity grows.
Appendix J: Legal and ethical foundations of mod authoring
The legal and ethical foundations of mod authoring are summarised in the table below. New mod developers should familiarise themselves with each foundation before publishing any mod, particularly any commercial mod.
| Foundation | Description | Practical implication |
|---|---|---|
| Copyright in original assets | The mod author holds copyright on assets they create | The author may license the assets on any terms |
| Copyright in base-game assets | Smartly Dressed Games holds copyright on the base-game assets | The author must not redistribute base-game assets |
| Copyright in third-party assets | The original creator holds copyright | The author must obtain a license before use |
| Trademark in studio identity | The studio's name and logo are the studio's trademarks | Use of another studio's identity is restricted |
| Commercial-publishing policy | Smartly Dressed Games' published policy governs commercial mod sales | Compliance is required |
| Customer-facing disclosure | The mod's documented behaviour is the customer's expectation | Hidden behaviour is a documented infraction |
| Localisation attribution | Translators hold rights to their localisation files | Attribution is the documented norm |
| Refund policy | The commercial marketplace's policy governs refunds | The author must comply with the marketplace policy |
The legal and ethical foundations above are not optional. Established commercial mod studios audit every release against each foundation before publication; the audit is a documented operational discipline that prevents the most common reputational and legal risks. New commercial mod developers should adopt the audit practice from the first commercial release.
Critical warning
The single most damaging legal mistake a new commercial mod developer can make is the unlicensed redistribution of third-party assets. Stolen textures, lifted meshes, and re-uploaded base-game content are documented causes of platform bans, storefront termination, and in egregious cases legal escalation. Every asset in a published mod must be either authored by the developer, licensed under terms that permit commercial mod distribution, or used under a documented permission from the original creator.
Appendix K: Document history and revision log
The 57 Studios Modding Knowledge Base is maintained as a living document. The revision log below records the principal updates to this article.
| Revision | Date | Notes |
|---|---|---|
| 1.0 | Initial publication | First foundational orientation on modding as a discipline |
| 1.1 | Category expansion | Added internal-diversity coverage for items, vehicles, maps |
| 1.2 | Revenue detail | Added revenue model and scope ladder appendices |
| 1.3 | Lifecycle detail | Added publishing lifecycle and broader industry sections |
| 1.4 | Current revision | Added appendices, expanded FAQ, additional historical context |
The knowledge base maintainers update this article when significant ecosystem shifts warrant inclusion. Readers who notice an inaccuracy or an outdated reference are encouraged to flag the discrepancy through the knowledge-base contribution channels.
Next steps
Continue to What is a File? to begin building the foundational file system knowledge required for all mod development work. Related articles include What is Unturned? for game background and the dedicated chapters on each mod category for deeper specialisation. Readers planning commercial publishing should consult the commercial-distribution chapters once the foundational orientation is complete.