Getting Started with Unturned Modding

Beginner10-15 minutesWindowsKeyboardMouse

This article is the bridge between the orientation chapters and the technical chapters of the 57 Studios Modding Knowledge Base. The preceding articles, What is Unturned?, What is Modding?, the file-system foundations, and the input-device guides, establish the concepts and computer literacy that mod development assumes. This article takes those concepts and translates them into concrete, actionable steps: the exact tools to install, the versions to use, the configuration to verify, and the first projects to attempt.

The article that follows describes the standard development environment that 57 Studios maintains across its active workstations and that the broader Unturned modding community has converged on over years of documented practice. New mod developers who assemble the toolchain exactly as described here bypass the most common setup problems that delay first publications. The time investment to read this article fully and install each tool in order is approximately two hours; skimping on any step in the chain compounds into days of avoidable troubleshooting later.

A note on scope. This article is prescriptive, it tells you what to install, in what order, with what exact versions, and what to do after installation. The articles that follow in the getting-started section and the modding-tool installation chapters provide the detailed per-tool configuration. This article is the high-level map; the subsequent articles are the step-by-step directions.

Prerequisites

• Completion of What is Unturned? and What is Modding?
• A Windows 10 or Windows 11 computer
• A working Steam account
• Approximately two hours of uninterrupted setup time
• Administrator access to install software on the workstation
• A minimum of 100 GB of free disk space for the game, the Unity Editor, and project files
• A willingness to follow instructions in the exact order given, without skipping steps

What you'll learn

• The five-hop modding pipeline from authoring to player experience
• The exact version of Unity Editor required for the current Unturned build
• The Unity packages shipped with the game and what each one provides
• The additional tools every mod developer needs
• The categories of mods and the tools each category requires
• Where to find official documentation and community resources
• A prerequisites checklist with exact version numbers
• The recommended first project for a new mod developer
• Answers to the most common beginner questions

The Unturned modding pipeline at a high level

Before installing any tools, it is useful to understand the end-to-end pipeline that connects a mod developer's source files to the content that players see in-game. The pipeline has five distinct hops, and each hop requires a specific tool or set of tools.

As shown in the flowchart above, the pipeline moves left to right. The mod developer authors source files (hop 1), imports them into the Unity Editor and assembles prefabs and materials (hop 2), builds the master bundle using the Unity asset bundling tools (hop 3), packages the built bundle alongside the configuration files into a mod folder (hop 4), and loads the completed mod in Unturned for testing or distribution (hop 5). Each hop is covered in depth by a dedicated chapter of the knowledge base; the references appear in the cross-references section at the end of this article.

Hop 1: Author source assets

The first hop is the authoring of the raw files that will become the mod. The files fall into three categories: three-dimensional models (authored in Blender or another 3D modeling tool), two-dimensional textures (authored in Photoshop, GIMP, Paint.NET, or another image editor), and configuration data (authored in a text editor as .dat files). The output of this hop is a set of source files on the developer's workstation, typically an FBX file for the model, a PNG or TGA file for the texture, and one or more .dat files for the configuration.

Hop 2: Import into Unity Editor

The second hop is the import of the source files into the Unity Editor. The developer creates a Unity project, imports the FBX mesh and the PNG texture, assembles a material, assigns the material to the mesh, constructs a prefab hierarchy (adding any required engine components such as the UseableMelee or UseableGun script), and saves the prefab. The Unity Editor applies its own processing to the imported files, meshes are converted to Unity's internal format, textures are compressed, and materials are baked. The output of this hop is a Unity project containing a correctly structured prefab.

Hop 3: Build master bundle

The third hop is the building of the master bundle. The developer uses the Unity asset bundling tools (provided by the Project.unitypackage file shipped with the game) to assign the prefab to an asset bundle and to build that bundle into a .unity3d file. The bundle is a packaged format that the Unturned game engine can load at runtime. The output of this hop is a .unity3d file containing the prefab and all its referenced assets (meshes, textures, materials).

Hop 4: Package mod folder

The fourth hop is the packaging of the mod folder. The developer copies the .unity3d bundle into a Bundles/ directory and writes the .dat configuration file and the English.dat localization file into an item folder. The folder structure and naming conventions are covered in detail in the item-authoring chapters. The output of this hop is a mod folder that, when placed in the correct location relative to the game installation, the game can read at load time.

Hop 5: Load in Unturned

The fifth hop is the loading of the mod in Unturned. The developer launches the game, opens the single-player mode, uses the console command @give <itemID> to spawn the item, and verifies that the mod appears correctly in-game. If any hop in the pipeline produced an error, the symptom will surface in this hop. The testing loop runs from hop 5 back to the earliest hop that needs correction, and the developer repeats the pipeline from that point forward.

The sequence above shows the temporal flow across the five hops. The mod developer spends most of the iteration time in hops 1 and 2 (authoring and assembly), with brief passes through hops 3 through 5 to verify each iteration. A well-optimized development loop minimizes the time spent in hops 3 through 5 by catching errors early.

What you can mod in Unturned

The Unturned modding system supports a wide range of content categories. Each category requires a different combination of tools and skills, and the entry difficulty varies substantially across categories.

Mod category	Description	Primary tools	Entry difficulty
Items (weapons)	Guns, melee weapons, throwables, and their supporting assets (magazines, attachments)	Unity Editor, Blender, text editor, image editor	Medium
Items (clothing)	Hats, glasses, masks, shirts, pants, vests, backpacks	Unity Editor, Blender, text editor, image editor	Low to medium
Items (cosmetics)	Reskins and retextures of existing vanilla items	Image editor, text editor	Low
Vehicles	Custom cars, trucks, helicopters, boats with physics	Unity Editor, Blender, text editor	High
Maps	Full terrain landscapes with object placement, spawn tables, and lighting	Unturned Map Editor, Unity Editor	High
NPCs and AI	Custom non-player characters with dialogue, quests, and behavior	Unity Editor, text editor, C# scripting	High
Server plugins	Server-side modifications to gameplay, economy, roleplay systems	C# IDE, OpenMod or RocketMod framework	Medium (programming)
Total conversions	Complete reimaginings of the game spanning all of the above	All of the above	Very high

The recommended first mod for every new developer is a cosmetic reskin, taking an existing vanilla item, changing its texture, and publishing the result. The reskin exercises the full pipeline (hops 1 through 5) without requiring 3D modeling skill or Unity prefab construction skill. Once the reskin is published, the developer can incrementally add skills: first a custom .dat configuration, then a custom Unity prefab, then a custom 3D mesh from Blender. The incremental approach produces a published mod at each stage rather than a single enormous project that may never reach completion.

Required tools: installing the foundation

The three foundational tools for Unturned mod development are the game itself, the Unity Editor, and the Unity packages that ship with the game. Each must be installed in a specific version; version mismatches are the single most common source of failed mod loads.

Installing Unturned

Unturned must be downloaded and installed from Steam before any mod development work can begin. The installation provides the game executable (needed to test mods), the official modding documentation (shipped with the game files), the Unity packages (in the Extras/Sources directory), and the vanilla asset files (which serve as reference examples for mod .dat files).

To install Unturned:

1. Open Steam on your Windows workstation. If Steam is not installed, download it from the Steam website and create a free account.
2. Search for Unturned in the Steam store.
3. Click the Install button. Unturned is free to play, and no purchase is required.
4. Wait for the installation to complete. The base game download is several gigabytes.
5. Launch Unturned once to confirm that it runs on your hardware. This initial launch also generates the local configuration files that the modding tools expect to find.
6. Close the game after confirming it runs.

The game files are installed to the Steam library directory, typically at C:\Program Files (x86)\Steam\steamapps\common\Unturned\. The Extras\Sources subdirectory contains the Unity packages that you will import in the next section. The Bundles\Items subdirectory contains the vanilla item configuration files that serve as reference examples.

Installing Unturned adds the Dedicated Server

Adding Unturned to your Steam Library also adds the Unturned Dedicated Server application to your Steam tools library. The Dedicated Server is not required for item, vehicle, or map mod development, but it is required for hosting multiplayer servers and for testing server-side plugins. The server installation is covered in the server-hosting chapters of the knowledge base.

Installing Unity Editor

The Unity Editor is the tool that assembles your source assets into the .unity3d bundles that the game loads. The exact Unity Editor version that Unturned targets changes with major game updates; installing the wrong version is the single most common cause of bundles that fail to load.

At the time of this writing, the Unturned game targets Unity Editor version 2022.3.62f3. This is a Unity 2022.3 Long Term Support release. The version number is published in the official Smartly Dressed Games modding documentation and is subject to change with Unturned engine refreshes. Always confirm the current target version in the official documentation before installing.

To install the Unity Editor:

1. Download Unity Hub from the Unity website. Unity Hub is the launcher that manages multiple Unity Editor installations on a single workstation.
2. Install Unity Hub and sign in with a Unity account. A free personal license is sufficient for mod development.
3. In Unity Hub, navigate to the Installs tab.
4. Click the Install Editor button.
5. Select version 2022.3.62f3 from the list of available versions. If the exact version is not listed, click the Archive link to browse older LTS releases.
6. On the modules selection screen, ensure the following build support modules are selected:
   • Linux Build Support (Mono), required for mod compatibility with Linux servers and players
   • Mac Build Support (Mono), required for mod compatibility with macOS players
7. Complete the installation. The Unity Editor download is several gigabytes, and the installation may take fifteen to thirty minutes depending on the workstation's storage speed.
8. After installation, verify that the version number displayed in Unity Hub's Installs tab reads 2022.3.62f3.

The exact version matters

Although most 2022.3 LTS versions are documented as compatible, and some older LTS versions can be used with additional configuration, versions other than the documented target may not function as intended by the Unturned engine. The safe practice is to install the exact version listed in the official documentation. A mismatch of even a single minor patch digit has produced documented bundle-loading failures.

Critical warning

Do not install the latest Unity Editor release, the version that Unity Hub offers by default is often several releases ahead of what Unturned targets. Asset bundles built against a newer Unity version will fail to load in Unturned, and the failure is silent (no error message to explain why the bundle was rejected). Always select the specific version from the archive list, never the default suggestion.

Importing the Unity packages

Unturned ships two Unity packages in the game installation directory. These packages provide the tools and examples required to export mod content from Unity.

Both packages are located in the Extras/Sources directory under the Unturned installation folder (typically C:\Program Files (x86)\Steam\steamapps\common\Unturned\Extras\Sources\).

To import the packages:

1. Create a new Unity project using the installed 2022.3.62f3 editor version. Use the 3D template. Name the project something descriptive (e.g., MyUnturnedMods). Choose a location on a fast drive with adequate free space.
2. Wait for the new project to open in the Unity Editor. The initial project creation and import may take several minutes.
3. In the Unity Editor toolbar, select Assets, then Import Package, then Custom Package.
4. In the file browser window that opens, navigate to the Unturned Extras/Sources directory.
5. Select the Project.unitypackage file and click Open.
6. In the import dialog that appears, all items are selected by default. Leave all items selected and click Import.
7. After the Project.unitypackage import completes, repeat the process for ExampleAssets.unitypackage. Importing ExampleAssets is optional but strongly recommended for new mod developers because it provides working reference prefabs for every vanilla asset type.
8. Wait for both imports to complete.

Project.unitypackage: the bare-bones essentials

The Project.unitypackage file contains the minimum required to export custom content from Unity to Unturned:

Included item	Purpose
Default Project Settings	Configures the Unity project for the correct rendering pipeline, compression settings, and platform targets
Asset Bundling Tools	Provides the scripts and menu items that build master bundles from prefabs
Mod Hooks (optional)	Provides optional integration points for advanced mod workflows

This package is required for every mod development project. Without it, the Unity Editor cannot produce bundles that the Unturned game engine can read.

ExampleAssets.unitypackage: the reference library

The ExampleAssets.unitypackage file contains vanilla content examples and reference prefabs that accelerate mod development:

Included item	Purpose
CoreMasterBundle directory	Contains an example of each type of vanilla asset, including fully configured prefabs with correct component hierarchies
Game/Sources/Animations directory	Contains all vanilla item animations, which can be reused or referenced in custom animation controllers
Resources/Characters/Preview.prefab	A character model prefab that is helpful for previewing clothing items during development

The CoreMasterBundle examples are the single most useful reference for a new mod developer because they show the exact prefab hierarchy and component configuration that each asset type expects. Study these examples before building your first custom prefab.

Custom content location

Do not place your custom content into the CoreMasterBundle directory. Create a separate directory in your Unity project to house your custom prefabs, meshes, and materials. The CoreMasterBundle directory is a reference library, not a working directory. Placing custom content inside it makes it difficult to distinguish your work from the reference examples and can cause build configuration errors when the reference examples are updated.

Other tools: the extended toolchain

Beyond Unturned, Unity, and the Unity packages, mod developers need a text editor, an image editor, and optionally a 3D modeling tool. Each category is covered below with specific recommendations drawn from the documented practices of the cohort and the broader Unturned modding community.

Text editors

A text editor is required to write and edit the .dat configuration files, the English.dat localization files, and any other plain-text files that the mod project uses. The text editor must be capable of editing plain text without adding formatting, styles, or embedded metadata.

Editor	Cost	Recommended for	Notes
Notepad	Free (included with Windows)	Absolute beginners	No additional features; entirely safe for plain text; no risk of accidental formatting
Notepad++	Free	Intermediate modders	Syntax highlighting, search-and-replace across multiple files, tabbed editing
Visual Studio Code	Free	Advanced modders and plugin developers	Full code-editing capabilities, Git integration, extension ecosystem

The cohort recommendation is to start with Notepad for your first mod. Notepad cannot accidentally add formatting, hidden characters, or embedded metadata to your .dat files. Once you have completed one mod with Notepad and understand the plain-text nature of .dat files, upgrade to Notepad++ or Visual Studio Code for the productivity gains of multi-file search and syntax highlighting.

Do not use a word processor

Do not use Microsoft Word, LibreOffice Writer, WordPad, Google Docs, or any other word processing program to write .dat files. Word processors are designed to add formatting, styles, and metadata to documents. They are not designed to produce plain text. Files saved from a word processor may contain invisible formatting characters that the Unturned parser cannot read, producing load errors that are difficult to diagnose because the file looks correct when opened. Always use a plain-text editor.

Image editing software

An image editor is required to create custom textures for modded items, clothing, objects, and effects. The image editor must support transparency (alpha channel) in exported PNG and TGA files, which are the two texture formats that Unturned consumes.

Software	Cost	Platform	Recommended for
Paint.NET	Free	Windows	Beginners; straightforward interface for texture painting
GIMP	Free	Windows, macOS, Linux	Intermediate; more powerful than Paint.NET, with layers and advanced brushes
Krita	Free	Windows, macOS, Linux	Digital painting; best brush engine among free options
Photoshop	Paid (subscription)	Windows, macOS	Professional texture artists; the industry standard

The cohort recommendation is to start with Paint.NET for your first item mod. The straightforward interface reduces the learning curve for texture authoring. Upgrade to GIMP or Krita when your texture work outgrows Paint.NET's feature set. Photoshop is the tool used by the established commercial mod studios but is not required for new mod developers.

Blender: 3D modeling

Blender is the only 3D modeling tool covered by this knowledge base, and it is the tool used by Smartly Dressed Games for Unturned development. Blender is free, open-source, and runs on Windows, macOS, and Linux.

Blender is required for mod developers who want to create custom 3D meshes for items, vehicles, objects, or map assets. It is not required for developers whose mods reuse existing vanilla meshes with new textures and configuration data.

The Blender-to-Unturned workflow involves modeling the mesh in Blender, applying scale (a documented requirement: non-unit scale produces incorrect in-game size), exporting to FBX format, and importing the FBX into the Unity Editor. The full workflow is covered in the Blender installation and item-authoring chapters of the knowledge base.

Mod category	Blender required?	Notes
Cosmetic reskin	No	Reuses vanilla mesh; only texture changes
Configuration-only item mod	No	Reuses vanilla mesh; only .dat changes
Item with custom mesh	Yes	Full 3D authoring pipeline
Vehicle mod	Yes, generally	Unless reusing a vanilla vehicle mesh
Map mod	No	The Unturned Map Editor handles terrain
Server-side plugin	No	No 3D content at all
Clothing with custom shape	Yes	Unless reusing a vanilla clothing mesh

The best approach for a new mod developer is to complete at least one cosmetic reskin before attempting a custom-mesh item. The reskin exercises the full pipeline and confirms that the toolchain is correctly installed. Adding Blender to the toolchain after the foundation is solid prevents compounding setup problems.

Where to find official documentation

The official Smartly Dressed Games modding documentation is the authoritative reference for every field, data type, and asset type in the Unturned modding system. The documentation is maintained alongside the game and is updated when new engine features or field additions ship.

The official documentation is accessed at: https://docs.smartlydressedgames.com/en/stable/

The table below summarises the principal sections of the official documentation that new mod developers should read first:

Documentation section	Contents	When to read
Getting Started	Tool installation, project setup, pipeline overview	Before installing any tools
Item Assets	Field reference for every item type	When authoring item .dat files
Vehicle Assets	Field reference for vehicle configuration	When authoring vehicle mods
Asset Bundling	Master bundle creation and export	When building Unity prefabs into bundles
Server Hosting	Dedicated server setup and configuration	When testing or hosting multiplayer servers

The official documentation is the first place to check when a field's behavior is unclear or when an error message in the game console references a configuration problem. The 57 Studios knowledge base supplements the official documentation with cohort-validated practices, worked examples, diagnostic tables, and appendices; it is not a replacement for the official documentation.

Where to find the wiki's organized resources

The 57 Studios Modding Knowledge Base is organized as a series of topic sections, each containing a sequence of articles that build on one another. The table below summarises the principal sections that new mod developers should read in order.

Section	Contents	When to read
Getting Started	Computer literacy foundations, file-system concepts, input-device guides	First
Steam and Unturned installation	Installing Steam, installing Unturned, verifying the game runs	Second
Unity setup	Installing Unity Hub, installing the correct editor version, importing the Unity packages	Third
Item authoring	Project folder structure, GUIDs, .dat files, .unity3d bundles, English.dat, Steam Workshop submission	Fourth
Publishing	Steam Workshop upload, Tebex commercial storefront, mod versioning	Fifth
Server hosting	Dedicated server setup, OpenMod framework, RocketMod framework, server administration	When ready to host

The recommended reading order is to complete the Getting Started section in full, then proceed to the Steam and Unturned installation section, then the Unity setup section, and so on. Each section assumes the knowledge of the previous sections.

Prerequisites checklist: exact tool versions

The checklist below summarises every tool, version, and configuration required for a functional Unturned mod development environment. The versions are current at the time of this writing; always verify the Unity Editor version against the official Smartly Dressed Games documentation before installing.

#	Tool	Exact version or requirement	Verified?
1	Windows operating system	Windows 10 (version 21H2 or later) or Windows 11
2	Steam client	Latest stable release (auto-updating)
3	Unturned game	Latest release (auto-updating through Steam)
4	Unity Hub	Latest stable release from the Unity website
5	Unity Editor	Version 2022.3.62f3 (2022.3 LTS)
6	Unity build support modules	Linux Build Support (Mono), Mac Build Support (Mono)
7	Unity package: Project.unitypackage	Imported from Unturned/Extras/Sources/
8	Unity package: ExampleAssets.unitypackage	Imported from Unturned/Extras/Sources/ (optional, recommended)
9	Text editor	Notepad (included with Windows), Notepad++, or Visual Studio Code
10	Image editor	Paint.NET, GIMP, Krita, or Photoshop
11	3D modeling tool	Blender (latest stable release, optional for custom-mesh items)
12	Free disk space	Minimum 100 GB for game, Unity Editor, and project files
13	Administrator access	Required to install Unity Editor and Unity Hub
14	Internet connection	Required for Steam, Unity package downloads, and documentation access

Verify each item in the checklist before attempting your first mod. A missed installation or a version mismatch may not produce an immediate error, the pipeline may work through hops 1 through 4 and fail silently at hop 5, with a mod that appears to load but renders incorrectly or not at all. The time required to verify the fourteen items above is approximately ten minutes; the time required to diagnose a silent failure caused by a version mismatch is typically measured in hours.

Additional notes on the prerequisites

The Unity Editor version 2022.3.62f3 is the published target at the time of this writing. Engine refreshes by Smartly Dressed Games change the target version. When a game update changes the Unity Editor version, all existing mod bundles must be rebuilt against the new editor version, this is a Known Event in the modding calendar, and established mod studios maintain readiness for it.

The Linux and Mac Build Support modules are required even if you only intend to test on Windows. The build modules add the platform support libraries that the Unity bundling tools require to produce cross-platform bundles. Omitting these modules produces bundles that function on Windows but fail to load on Linux and macOS servers and clients.

The text editor, image editor, and 3D modeling tool are listed as separate items in the checklist because they perform distinct and non-overlapping functions. A single tool cannot replace all three. Mod developers who intend to pursue the server-side-plugin path (which requires no image editor or 3D tool) should still install a text editor for .dat file authoring.

First steps: what to do after reading this article

This article describes what to install. The articles that follow describe how to use each installed tool. The recommended sequence of next steps is:

1. Read the next article in the getting-started section: Official FAQ. The FAQ covers the most common questions new mod developers ask after their first tool installation.

2. Proceed to the Steam and Unturned installation section if you have not yet installed the game. The section covers the exact installation sequence, the directory structure to expect, and the verification steps to confirm the game runs.

3. Proceed to the Unity setup section if you have not yet installed the Unity Editor. The section covers Unity Hub installation, selecting the correct editor version, adding build support modules, and creating your first Unity project.

4. Import the Unity packages as described in the Unity setup section. The packages are essential; without them, the Unity Editor cannot produce bundles that the game can load.

5. Complete a cosmetic reskin as your first mod. Select a vanilla item with a simple texture (a shirt, a pair of pants, or a backpack), repaint the texture in your image editor, write the .dat configuration and English.dat localization, build the master bundle, and load the mod in Unturned. The entire project should take between two and eight hours of active work.

6. Publish the reskin to Steam Workshop as a free mod. The publication exercises the full pipeline (authoring, building, packaging, publishing, and verifying), and seeing your content appear in the Workshop is the psychological milestone that separates mod developers who continue from those who abandon the work.

The sequence above is the documented path that the cohort has validated as the fastest route from tool installation to first published mod. A developer who follows this sequence exactly will have a published mod within one week of part-time work.

Frequently asked questions

Do I need to buy anything to start modding Unturned?

No. Unturned is free to play on Steam. The Unity Editor is free under a personal license. Blender, GIMP, Krita, Paint.NET, Notepad++, and Visual Studio Code are all free. A developer can build and publish a complete item mod without spending any money on software.

Can I develop Unturned mods on macOS or Linux?

The modding toolchain is most fully supported on Windows. The Unity Editor runs on macOS and Linux, and a text editor and image editor are available on all three platforms. However, the Unturned Map Editor is Windows-only, and some asset-bundling workflows are more reliable on Windows. The 57 Studios knowledge base assumes Windows throughout. A companion macOS Modding Guide covers the considerations for macOS developers; it is the recommended reference for that subset of the readership.

What is the minimum disk space required?

The game installation is approximately 8 to 12 gigabytes. The Unity Editor installation with one build target module is approximately 10 to 15 gigabytes. A small mod project with a single item occupies a few hundred megabytes. A large mod project with multiple items, vehicles, maps, and source assets can occupy tens or hundreds of gigabytes. The recommended minimum free space before starting is 100 gigabytes.

How long does it take to ship a first mod?

A cosmetic reskin, the recommended first project, can be completed in two to eight hours of active work spread across one to two weeks. A full custom-mesh item mod takes two to four weeks of part-time work. A vehicle mod takes four to twelve weeks. A map mod takes months to years. The cosmetic reskin is the recommended starting point because it completes the full pipeline in the shortest time.

Do I need 3D modeling skill to be a mod developer?

It depends on the category. Cosmetic reskins and configuration-only item mods do not require 3D modeling. Custom-mesh items, vehicle mods, and map objects do. Server-side plugins do not require any 3D skill at all. A developer without 3D skill can pursue cosmetic mods, configuration-only mods, and server-side plugins without obstacle.

What if I install the wrong Unity Editor version?

Asset bundles built against a Unity Editor version that does not match the Unturned target will fail to load silently at runtime. The mod may appear in the inventory but render incorrectly, or it may not appear at all. The fix is to install the correct version (currently 2022.3.62f3) through Unity Hub and rebuild every bundle against the correct version.

How do I know if my tools are correctly installed?

The verification sequence is: launch Unturned in single-player and confirm the game runs; launch the Unity Editor and confirm the version number in the title bar or About dialog; open your text editor and create a test .dat file; open your image editor and export a test PNG with transparency; launch Blender and confirm it opens without errors. Each tool in the chain has a standalone verification step that does not depend on any other tool being correctly installed.

Do I need Unity Hub, or can I install Unity directly?

Unity Hub is the recommended launcher because it manages multiple Unity Editor versions on a single workstation, a capability that becomes essential when Unturned engine refreshes change the target version and you need the old version for previously published mods and the new version for new work. Direct installation of a single Unity Editor version is possible but is not the documented practice.

Can I skip the ExampleAssets.unitypackage import?

Yes, technically. The Project.unitypackage is required; the ExampleAssets.unitypackage is optional. However, the examples in the ExampleAssets package are the reference prefabs that the cohort uses to verify correct hierarchy and component configuration for every asset type. Skipping the import means you must figure out the correct prefab structure from other sources. The import takes approximately five minutes and is recommended.

What is the fastest way to fix a mod that is not loading?

The diagnostic sequence is: verify the .unity3d file is in the correct Bundles/ folder; verify the .dat file is in the correct item folder and the folder name matches the configuration; verify the Unity Editor version matches the Unturned target; verify the GUID in the .dat file is unique and valid; verify the item ID is not colliding with another loaded item. Work through these five checks in order. Ninety percent of mod-loading failures are resolved by one of them.

Can I mod Unturned without installing Unity?

Some mod categories do not require Unity. Configuration-only item tweaks (changing the damage or capacity of an existing item) can be done entirely with a text editor. Server-side plugins are developed in a C# IDE and do not touch the Unity Editor. Cosmetic reskins that reuse existing meshes do require Unity to build the bundle, but the developer can reuse a single Unity project across many cosmetic mods. The only path that avoids Unity entirely is server-side plugin development plus configuration-only item tweaks.

How do I stay updated when the target Unity version changes?

Monitor the official Smartly Dressed Games modding documentation and the Unturned Steam community hub patch notes. When a game update changes the target Unity version, the documentation will list the new version. Download the new version through Unity Hub, rebuild your project against it, and rebuild your bundles. Established mod studios perform this cycle once or twice per year, and the process typically takes a few hours for a medium-sized portfolio.

Best practices

• Install the tools in the exact order described: Unturned first, then Unity, then the Unity packages, then the additional tools
• Install the exact Unity Editor version listed in the official documentation, not the latest available release
• Include Linux Build Support and Mac Build Support when installing Unity Editor, even if you only test on Windows
• Import both Unity packages (Project.unitypackage and ExampleAssets.unitypackage) into every new Unity project
• Use Notepad for your first .dat file authoring before upgrading to a more powerful text editor
• Complete a cosmetic reskin as your first project before attempting any custom-mesh work
• Test every tool in isolation before attempting an end-to-end mod build
• Keep a text file with the installed version of every tool, updated each time a tool is updated
• Read the official Smartly Dressed Games modding documentation alongside the 57 Studios knowledge base
• Rebuild all bundles against the new Unity Editor version after any game update that changes the target version

Advanced considerations

This section covers additional considerations that may not apply to every new mod developer but are essential context for those who plan to pursue modding as a long-term discipline.

Working across multiple workstations

Mod developers who work on more than one computer should adopt a strategy for synchronizing project files between workstations. The dominant pattern across the established commercial mod studios is to version-control the source files (.dat files, texture source files, Blender files) through Git with LFS (Large File Storage) for binary assets, and to rebuild the Unity project and master bundles on each workstation rather than synchronizing the compiled bundles. Source files are small and version-control-friendly; compiled bundles are large, platform-sensitive, and should be treated as build artefacts that can be regenerated.

Maintaining multiple Unity Editor versions

Unturned engine refreshes change the target Unity Editor version. When a refresh occurs, existing published mods must be rebuilt against the new version, but active development on new mods may need to continue uninterrupted. Unity Hub supports installing multiple Unity Editor versions side by side. The cohort practice is to keep the previous target version installed (for rebuilding existing mods) alongside the new target version (for new mods). When a multi-version refactoring cycle is complete and all published mods have been rebuilt against the new version, the old editor version can be removed.

Disk space planning for a growing mod portfolio

A single small item mod occupies a few hundred megabytes of project files and a few megabytes of published files. A portfolio of twenty item mods, ten vehicle mods, and a map mod can occupy several hundred gigabytes when source files, Unity projects, compiled bundles, and published Workshop items are all counted. The documented practice for commercial mod studios is to maintain a primary workstation with a 1 TB or larger NVMe SSD, an external backup drive of 4 TB or larger, and cloud storage for snapshot backups. New mod developers should monitor their disk usage and plan for a storage upgrade when the free space falls below 100 GB.

Recovering from a botched Unity Editor installation

If the Unity Editor installation produces errors, does not launch, or builds bundles that fail to load in Unturned, the documented recovery sequence is: uninstall the Unity Editor version through Unity Hub (Hub, Installs tab, right-click the version, Uninstall), restart the workstation, download the version again through Unity Hub, and reinstall with the Linux and Mac Build Support modules selected. Do not attempt to repair a botched Unity Editor installation by installing additional components or running repair tools, a clean uninstall and reinstall is faster and more reliable.

Working with pre-existing mod projects

If you inherit a mod project from another developer, acquire a Workshop mod's source files, or are asked to update a previously published mod, the first step is always to open the project in the correct Unity Editor version. The correct version is determined by checking the Unity project's ProjectSettings/ProjectVersion.txt file, which records the editor version the project was last saved with. Open the project in that version, verify it loads without errors, and only then consider upgrading to a newer version. Opening a project in a newer editor version than it was authored in will prompt a project upgrade, which is a one-way operation, the project can no longer be opened in the older version. Make a backup of the project folder before opening it in an upgraded editor.

Appendix A: Expanded modding pipeline detail for each hop

The five-hop pipeline diagram in the main article provides the high-level overview. The expanded detail below adds the sub-steps, the tools, and the common failure points for each hop.

Hop 1 detail: authoring source assets

Step	Tool	Output	Common failure point
Model the 3D mesh	Blender or other 3D tool	.blend source file	Non-unit scale (apply scale before export)
UV unwrap the mesh	Blender	UV layout in the .blend file	Overlapping UV islands producing texture bleeding
Paint the texture	Image editor	.png or .tga file	Texture not power-of-two (use 512, 1024, 2048)
Export the mesh to FBX	Blender (export menu)	.fbx file	FBX export settings incompatible with Unity
Write the .dat file	Text editor	.dat configuration file	Misspelled field names, wrong type enum
Write the English.dat file	Text editor	Localization file	Missing Name or Description field

Hop 2 detail: importing into Unity

Step	Tool	Output	Common failure point
Create or open Unity project	Unity Editor	Project folder with Assets directory	Wrong Unity Editor version
Import FBX into Assets	Unity Editor (drag-and-drop)	Unity mesh asset	FBX scale set to 0.01 instead of 1.0
Import PNG/TGA into Assets	Unity Editor (drag-and-drop)	Unity texture asset	Texture compression settings incompatible with game
Create material	Unity Editor (Create menu)	Unity material asset	Shader not compatible with Unturned rendering pipeline
Construct prefab hierarchy	Unity Editor (Hierarchy panel)	Prefab with correct components	Missing required engine component (UseableMelee, etc.)
Assign prefab to asset bundle	Unity Editor (Asset Labels panel)	Bundle assignment on prefab	Bundle name does not match expected convention

Hop 3 detail: building the master bundle

Step	Tool	Output	Common failure point
Configure bundle build settings	Unity Editor (Build menu)	Build configuration	Incorrect build target platform
Build asset bundle	Unity Editor (Build AssetBundles)	.unity3d file	Bundling scripts not imported (Project.unitypackage missing)
Verify bundle contents	Unity Editor (Asset Bundle Browser)	Inspected bundle contents	Missing assets or broken references

Hop 4 detail: packaging the mod folder

Step	Tool	Output	Common failure point
Create mod folder structure	File Explorer or text editor	Folder hierarchy at correct path	Folder path does not match mod ID or naming convention
Copy .unity3d to Bundles	File Explorer	Bundle in correct location	Bundle filename does not match Item field or convention
Copy .dat files to item subfolder	File Explorer or text editor	Configuration in correct location	.dat file in wrong folder relative to bundle
Verify all required files present	Manual or scripted check	Confirmation	Missing English.dat, missing bundle, missing configuration

Hop 5 detail: loading and testing in Unturned

Step	Tool	Output	Common failure point
Launch Unturned	Steam launcher	Game window open to main menu	Game update pending; restart to apply
Enter single-player mode	In-game menu	Player spawned in world	Mod folder not recognized (wrong path)
Spawn test item with @give	In-game console (~ key)	Item appears in inventory	Wrong item ID or mod not loaded
Inspect item visually	In-game camera	Visual confirmation	Incorrect scale, position, or material
Test item functionality	In-game controls	Behavior confirmation	Missing engine component, wrong Enum value

Appendix B: Common tool installation errors and fixes

The table below catalogues the most common tool installation errors that new mod developers encounter and the documented fixes.

Symptom	Tool affected	Most likely cause	Fix
Unturned does not launch	Steam / Unturned	Missing redistributables or anti-virus blocking	Install Visual C++ redistributables; add Unturned folder to anti-virus exceptions
Unity Hub cannot find the specified editor version	Unity Hub	Version not available in the default channel	Click Archive link in the install dialog; browse the LTS archive
Unity Editor crashes on startup	Unity Editor	Corrupted installation or incompatible GPU driver	Uninstall and reinstall the editor; update GPU drivers
Asset bundle build fails	Unity Editor	Project.unitypackage not imported	Import the package from Extras/Sources/
Imported FBX has wrong scale	Unity Editor	Blender export scale settings	Re-export from Blender with "Apply Scalings: FBX All"
.dat file produces parser error	Unturned game	Word processor used instead of plain-text editor	Reauthor the file in Notepad; retype the content (do not copy-paste from a word processor)
English.dat text does not appear in-game	Unturned game	File encoding is not UTF-8	Save the file with UTF-8 encoding (Notepad: Save As, Encoding dropdown)
Texture appears pink in Unity	Unity Editor	Shader not compatible with project render pipeline	Use a shader compatible with the Built-in Render Pipeline
Unity Hub license activation fails	Unity Hub	Firewall blocking Unity authentication	Temporarily disable firewall or add Unity Hub to exceptions

Appendix C: Modding category tool matrix

The matrix below shows which tools are required for each modding category. The matrix is a companion to the "What you can mod" table in the main article and adds the tool participation column.

Mod category	Text editor	Image editor	Unity Editor	Blender	C# IDE	Map Editor
Cosmetic reskin	Yes	Yes	Yes	No	No	No
Configuration-only tweak	Yes	No	No	No	No	No
Item with custom mesh	Yes	Yes	Yes	Yes	No	No
Clothing item	Yes	Yes	Yes	Yes (if custom shape)	No	No
Vehicle mod	Yes	Yes	Yes	Yes	No	No
Map mod	Yes	Optional	Yes (for object prefabs)	Optional	No	Yes
Server-side plugin	Optional	No	No	No	Yes	No
Total conversion	Yes	Yes	Yes	Yes	Yes	Yes

Appendix D: Glossary of modding tool terms

Term	Definition
Asset bundle	A packaged .unity3d file containing one or more Unity assets (meshes, textures, materials, prefabs) that the Unturned game engine loads at runtime
Build target	The platform (Windows, Linux, macOS) for which an asset bundle is compiled
LTS	Long Term Support, a Unity Editor release designation indicating extended stability maintenance
Master bundle	The .unity3d file that contains an item's prefab and all its dependent assets
Mod folder	The directory structure under Workshop/Content/304930/<modID>/ that holds the bundle and the configuration files
Prefab	A Unity asset that packages a GameObject hierarchy with all its components, ready to be instantiated in-game
Project.unitypackage	The Unity package shipped with Unturned that contains the required bundling tools and project settings
Unity Hub	The launcher application that manages multiple Unity Editor installations on a workstation

Cross-references

• What is Unturned?, the first orientation article; introduces the game, the developer, the engine, and the player base.
• What is Modding?, the second orientation article; establishes the discipline of modding and the categories of mod work.
• What is a File?, the file-system foundations that every mod developer relies on.
• How to Install Unity Hub, the detailed Unity Hub installation walkthrough.
• How to Install the Unity Editor, the detailed Unity Editor version selection and installation walkthrough.
• How to Install Unturned, the detailed Unturned installation walkthrough.
• Smartly Dressed Games modding documentation, the official field reference and tool documentation.
• Unturned on Steam, the game page and community hub.
• Official FAQ, the next article; answers the most common beginner questions.

Document history

Version	Date	Author	Notes
1.0	2026-07-26	57 Studios	Initial publication. Complete tooling walkthrough with exact versions, five-hop pipeline diagram, prerequisites checklist, and first-project guidance.