Legacy Tutorials
The earliest Unturned modding documentation was published through Steam Guides, and for many years these guides were the primary information source for the modding community. The guides were written by SDG and by community contributors at a time when the official modding documentation did not exist in its current form, and they served as the foundation on which the modern modding knowledge base was built. This article catalogues the legacy Steam Guide tutorials, evaluates which content remains relevant to current modding practice, identifies which content has been superseded, and provides migration paths from legacy approaches to the current documentation set.
The legacy tutorials are not obsolete in the sense that they contain incorrect information. Many of the guides - particularly those covering Unity Editor setup, asset authoring workflows, and fundamental modding concepts - contain accurate information that has not been reproduced in the current documentation. The challenge for the modern mod developer is that the legacy guides are interspersed with content that is out of date, references tool versions that are no longer available, or describes workflows that have been replaced by more current approaches. Disentangling the relevant from the superseded is the purpose of this article.
The 57 Studios cohort has reviewed every legacy Steam Guide referenced in the official SDG documentation and has produced the following catalogue, evaluation, and migration guidance. New mod developers should not start with the legacy guides; they should start with the current documentation in this knowledge base and in the official SDG documentation, and they should consult the legacy guides only for the specific topics that this article identifies as still relevant.
Who this article is for
This article is written for Unturned mod developers at all experience levels who encounter references to legacy Steam Guide tutorials in community discussions, older mod documentation, or the official SDG documentation's Legacy Tutorials chapter. The mod developer who has already established a working development environment and is comfortable with the current documentation set will find this article most useful as a reference for evaluating whether a legacy guide is worth consulting.
New mod developers who are just starting out should read the Getting Started articles before consulting this article. The legacy guides are supplemental resources, not primary ones, and a developer who starts with the legacy guides risks learning workflows that are no longer current. The developer should establish a foundation in the current documentation first and then use this article to selectively access the legacy content that remains relevant.
Developers who are maintaining older mods that were originally built using legacy workflows will find the migration guidance in this article directly applicable. A mod that was authored against a 2017-era Steam Guide may need to be updated to work with the current SDK, and the migration paths documented here provide the transition reference.
What you will learn
- The complete catalogue of legacy Steam Guide tutorials referenced in the official SDG documentation
- Which legacy guides contain information that is still relevant to current modding practice
- Which legacy guides have been fully superseded by current documentation
- How legacy Unity setup workflows differ from current workflows
- The migration path from legacy approaches to current documentation for each guide category
- How to evaluate the accuracy of legacy guide content against current SDK behaviour
- The official video tutorial catalogue and which videos remain useful
- Best practices for using legacy resources alongside current documentation
Background
Before the release of the official modding documentation, Steam Guides were the primary distribution channel for Unturned modding tutorials. SDG published guides covering item creation, vehicle authoring, object setup, map features, localization, workshop submission, and Unity version migration. Community contributors supplemented these with their own guides, creating a distributed documentation ecosystem that was rich but fragmented.
The release of the official documentation and, later, the U3 SDK fundamentally changed the information landscape. The official documentation provided a central, authoritative reference that was maintained alongside the game's development. The community knowledge base - including the 57 Studios Modding Knowledge Base - extended the official documentation with cohort-validated workflows, field references, and diagnostic content. The Steam Guides, while still accessible, were no longer the primary information source.
The official SDG documentation's Legacy Tutorials chapter acknowledges this transition. It notes that most of the Steam Guides have been superseded by the current documentation but that "some still contain useful information about Unity setup that we have yet to bring over." The guides that SDG specifically calls out as still containing useful information are the items of focus in this article.
The legacy video tutorials, also catalogued in the official documentation, represent a separate category of legacy content. Many of the videos have become outdated and "do not accurately represent the current modding features available, or may contain incorrect information." The official documentation lists them for completeness rather than as recommended resources, and the developer should approach them with the caution that this article describes.
The flowchart above shows the historical progression of Unturned modding documentation and the evaluation path for legacy content. The transition from the Steam Guides era to the current documentation era was gradual, and content from all three eras coexists in the information ecosystem that modern mod developers navigate.
Legacy Steam Guide catalogue
The official SDG documentation's Legacy Tutorials chapter lists the following Steam Guides as the legacy tutorials that the developer community should be aware of. Each guide is listed with its subject area and the evaluation of what, if anything, remains relevant.
Items
The Items Steam Guide covers the creation of item assets for Unturned - weapons, clothing, consumables, and other inventory items. Most of the sub-sections about Unity setup are still relevant, according to the official documentation. The .dat field reference in the guide is largely superseded by the current official documentation and by the 57 Studios item asset articles, but the Unity Editor workflow descriptions - how to set up a prefab, how to configure the Animator Controller, how to build and export a master bundle - have not been fully reproduced in the current documentation.
The modern mod developer should consult the current documentation for .dat field reference (Melee Asset, Magazine Asset Reference, and related articles) and the legacy Items guide for Unity Editor setup procedures that are not yet covered in the current documentation. The developer should verify that any Unity Editor procedure from the legacy guide works in the current Unity Editor version before relying on it, as Unity's interface and workflow have changed across versions.
| Legacy guide content | Status | Current documentation equivalent |
|---|---|---|
Item .dat field reference | Superseded | Item Asset Anatomy, type-specific articles |
| Unity prefab setup for items | Partially relevant | Master Bundle Export |
| Animator Controller configuration | Still relevant | Not fully reproduced in current documentation |
| Master bundle build and export | Partially relevant | Master Bundle Export |
| Workshop upload procedure | Superseded | Steam Workshop Submission |
Vehicles
The Vehicles Steam Guide covers the creation of vehicle assets. Like the Items guide, the information about Unity setup remains relevant while the .dat field reference has been superseded. Vehicle modding involves more complex Unity prefab hierarchies than item modding, and the legacy guide's coverage of vehicle prefab structure, wheel collider setup, and vehicle physics configuration has not been fully reproduced in the current documentation.
The modern mod developer should approach the Vehicles guide with particular attention to the Unity version differences. Vehicle physics in Unity have evolved across versions, and configurations that worked in the Unity 5 era may produce different behaviour in the current Unity Editor version. The developer should treat the legacy guide's physics configuration values as starting points that require testing and adjustment, not as values that can be copied without verification.
| Legacy guide content | Status | Current documentation equivalent |
|---|---|---|
Vehicle .dat field reference | Superseded | Current official documentation vehicle section |
| Unity prefab hierarchy for vehicles | Still relevant | Not fully reproduced in current documentation |
| Wheel collider configuration | Partially relevant | Requires testing against current Unity version |
| Vehicle physics tuning | Partially relevant | Values may need adjustment for current Unity |
| Vehicle animation setup | Still relevant | Not fully reproduced in current documentation |
Objects
The Objects Steam Guide covers the creation of placeable objects - barricades, structures, and world objects. The Unity setup information remains the most valuable component of this guide, as the current documentation's coverage of object prefab authoring is less detailed than the legacy guide's step-by-step walkthrough.
The modern mod developer who is creating a new object type should consult the legacy Objects guide for the Unity Editor workflow and the current documentation for the .dat field reference. The object asset type has received fewer documentation updates than items or vehicles, which means the legacy guide has retained more of its relevance than guides for asset types that have been more thoroughly documented in the current era.
Miscellaneous Assets
The Miscellaneous Assets Steam Guide covers Unity setup for animals, effects, and resources. These asset types occupy a smaller share of the modding community's attention than items and vehicles, and the current documentation's coverage of them is correspondingly thinner. The legacy guide remains the most detailed Unity setup reference for these asset types.
The modern mod developer who is working with animals, effects, or resources should consult the legacy guide for Unity setup procedures and the current official documentation for .dat field reference. The developer should be aware that some of the asset types covered in the legacy guide have received engine-level changes that affect how they function at runtime, and the .dat fields documented in the legacy guide may not reflect the current field set.
Maps
The Maps Steam Guide explains various map features and the map authoring workflow. Map modding is the most complex modding discipline, and the legacy guide's coverage of map features - terrain painting, foliage placement, spawn point configuration, navigation mesh generation - is substantially more detailed than the current documentation's coverage of the same topics.
The modern mod developer who is creating a custom map should consult the legacy Maps guide alongside the current documentation. The Unity terrain system has evolved across versions, and the legacy guide's terrain authoring procedures may reference tools or interfaces that have changed. The developer should verify each procedure against the current Unity Editor before committing to a workflow.
| Legacy guide content | Status | Current documentation equivalent |
|---|---|---|
| Terrain authoring workflow | Partially relevant | Unity terrain tools have changed across versions |
| Foliage placement and configuration | Still relevant | Not fully reproduced in current documentation |
| Spawn point configuration | Partially relevant | .dat field reference superseded; concept explanations still relevant |
| Navigation mesh generation | Partially relevant | Unity navigation system has changed across versions |
| Map feature explanations | Still relevant | Conceptual coverage not reproduced in current documentation |
Localization
The Localization Steam Guide covers the creation of language-specific text files for mod content. The localization system has remained relatively stable across Unturned versions, and the legacy guide's coverage of the English.dat format, the language file naming convention, and the fallback behaviour is still accurate.
The modern mod developer should consult the legacy Localization guide for the file format reference (which has not changed) and the current documentation for any new localization features that have been added since the guide was written. The 57 Studios knowledge base articles on localization provide the current best practices for multilingual mod development, and the legacy guide serves as a supplementary format reference.
Creating Third-Party Modules
The Third-Party Modules Steam Guide covers a development pattern that is distinct from both mods and plugins. The guide is explicitly noted in the official documentation as "Not to be confused with mods or plugins," and it describes a specific architectural approach that may not be relevant to most modern mod developers.
The modern mod developer should understand that third-party modules are a separate concept from the mods and plugins that dominate current modding practice. The legacy guide is primarily of historical interest; the developer who is building a conventional mod or plugin does not need to consult it. The developer who encounters the term "third-party module" in older documentation or community discussions should recognise it as a reference to a specific legacy pattern rather than as a current modding practice.
Uploading Mods to the Steam Workshop
The Uploading Mods to the Steam Workshop Steam Guide covers the mod publishing workflow. The Steam Workshop upload procedure has changed across the years, and the legacy guide's specific upload steps may not match the current Workshop interface. However, the conceptual coverage of Workshop metadata, preview image requirements, and mod versioning is still relevant.
The modern mod developer should consult the current Steam Workshop Submission article for the upload procedure and the legacy guide for the conceptual background on Workshop item management. The specific button labels, menu locations, and interface elements in the legacy guide should not be relied upon without verification against the current Steam client.
Upgrading from Unity 5 LTS to Unity 2017 LTS
The Unity Upgrade Steam Guide is "only relevant for very old mods, but lists the important changes between those two versions," according to the official documentation. This guide is the most narrowly applicable legacy resource; it is relevant only to developers who are maintaining a mod that was built against Unity 5 LTS and who need to understand what changed between Unity 5 and Unity 2017.
The modern mod developer who is building a new mod with the current Unity Editor version does not need to consult this guide. The developer who is maintaining an older mod that was built against Unity 5 or Unity 2017 should consult the guide for the specific breaking changes between those versions, and should budget additional migration effort for the changes between Unity 2017 and the current version, which the legacy guide does not cover.
Unity version migration
The legacy upgrade guide only covers the Unity 5 to Unity 2017 transition. Migrating a mod from Unity 2017 to the current Unity version requires additional steps that are not documented in the legacy guide. The developer should consult Unity's official migration documentation for each version increment and should expect to spend substantial time resolving API deprecations, shader compatibility issues, and asset import format changes.
Official video tutorial catalogue
The official SDG documentation lists several video tutorials that were produced during the earlier era of Unturned modding. The documentation states that "many of these have gradually become outdated" and "do not accurately represent the current modding features available, or may contain incorrect information." The videos are listed "for completeness" rather than as recommended resources.
The following is the catalogue of official video tutorials as listed in the SDG documentation, with the 57 Studios cohort evaluation of each video's current relevance.
Hosting a Dedicated Server on Windows
This video tutorial covers the process of setting up a dedicated Unturned server on a Windows machine. The dedicated server hosting workflow has changed across Unturned versions, and the specific steps in the video may not match the current server setup procedure. The conceptual content - what a dedicated server is, why a mod developer might host one, the basic client-server architecture - remains accurate.
The modern developer should consult the current server hosting documentation for the setup procedure and should use the legacy video only for the architectural concepts. The video's specific configuration file paths, command-line arguments, and port forwarding instructions should be verified against the current documentation before being followed.
Uploading Skins to the Curated Workshop
This video tutorial covers the curated workshop skin submission process. The curated workshop system has evolved, and the submission procedure documented in the video is unlikely to match the current process. The video is primarily of historical interest.
The modern developer who wants to submit skins should consult the current official documentation for the skin submission process and should not rely on the legacy video's specific steps.
Creating Custom Songs
This video tutorial covers the creation and integration of custom audio content. The audio system in Unturned has received updates since the video was produced, and the audio import and configuration procedures may have changed. The creative concepts - how to author audio content for Unturned, what audio formats are supported, how audio integrates with the game's sound system - remain valuable even if the technical implementation details are out of date.
The modern developer should consult the current audio documentation for the technical workflow and the legacy video for the creative guidance on audio content design for Unturned.
Quick Overview of First Version of Foliage Upgrade
This video tutorial covers an early version of the foliage system upgrade. The foliage system has been substantially revised since this video was produced, and the specific features and interfaces documented in the video are no longer current. The video is primarily of historical interest.
The modern developer working with foliage should consult the current foliage documentation and the Maps Steam Guide for foliage placement guidance.
Devkit 101 and Landscapes Overview
This video tutorial provides a broad overview of the development kit interface and landscape authoring. The devkit interface has changed across Unturned versions, and the specific interface elements shown in the video may not match the current editor. The conceptual content - how the devkit is organised, what the major interface regions are for, the relationship between the devkit and Unity - remains valuable as an orientation resource.
The modern developer should use this video as a conceptual orientation and should not rely on the specific interface elements, menu locations, or button labels shown in the video.
Spawn Tables
This video tutorial covers the spawn table system that controls how items, vehicles, and zombies appear in the game world. The spawn table format has remained relatively stable, and the video's content may still be accurate. However, the spawn table editor interface may have changed, and the developer should verify the specific editing procedures against the current editor.
The modern developer should consult the current spawn table documentation for the definitive reference and the legacy video for the conceptual explanation of how spawn tables interact with the game's spawning system.
Building Models
This video tutorial covers the 3D model authoring workflow for Unturned assets. The 3D modelling fundamentals - topology, UV mapping, texture authoring, export settings - are tool-agnostic and remain accurate regardless of when the video was produced. The specific Blender or other 3D tool versions and interfaces shown in the video may be outdated, but the principles the video teaches are still applicable.
The modern developer should use this video for the 3D modelling principles and should consult current 3D tool documentation for the tool-specific procedures. The 57 Studios cohort recommends this video as one of the more durable legacy resources because 3D modelling fundamentals change much more slowly than game engine interfaces.
The flowchart above describes the evaluation process the developer should apply when encountering any legacy video tutorial. The process separates creative and conceptual content (which ages slowly) from interface and procedural content (which ages quickly), and it ensures that the developer does not apply outdated procedures without verification.
How legacy tutorials differ from current documentation
The differences between the legacy Steam Guide tutorials and the current documentation set fall into several categories. Understanding these categories helps the developer evaluate legacy content and determine when it can be used directly and when it must be verified.
Unity Editor version differences
The legacy guides were written for Unity 5 and Unity 2017. The current SDK uses a substantially newer Unity version. Unity's interface, workflow, and API have changed across these versions, and procedures that were correct for Unity 5 may not work in the current Unity Editor. The developer should expect that any legacy procedure that involves clicking a specific button, opening a specific menu, or accessing a specific panel may need to be adapted for the current editor.
The most common Unity version differences that affect legacy guide accuracy are:
| Legacy procedure | Issue in current Unity | Resolution |
|---|---|---|
| Asset bundle build settings | Build interface has changed | Use current Build Tool described in SDK documentation |
| Prefab creation workflow | Prefab system was overhauled | Use current prefab workflow |
| Material and shader configuration | Standard shader replaced | Use current rendering pipeline materials |
| Animation import settings | Animation import interface changed | Use current animation import settings |
| Navigation mesh baking | Navigation system was updated | Use current navigation tools |
Tool version differences
The legacy guides reference specific versions of third-party tools - Blender, Notepad++, Photoshop, and others. The current versions of these tools may have different interfaces, different file format support, and different export workflows. The developer should use the current version of each tool and should consult that tool's current documentation for the user interface, then apply the conceptual guidance from the legacy guide to the current tool interface.
The 57 Studios cohort has validated that the following tool-specific legacy guide content is affected by version differences:
| Tool | Version referenced in legacy guides | Current version differences |
|---|---|---|
| Blender | 2.7x series | Major interface redesign in 2.8+; different export settings |
| Unity Editor | 5.x, 2017.x | Substantial interface and API changes |
| Notepad++ | Older versions | Minor interface changes; encoding handling unchanged |
| Photoshop | Older versions | Minor interface changes; PSD format unchanged |
File format differences
Some of the file formats used in Unturned modding have evolved since the legacy guides were written. The .dat file format has gained new fields and new field types, and the legacy guides' field reference tables may be incomplete for current Unturned versions. The developer should always consult the current documentation for field reference and should use the legacy guides only for the fields they cover that have not changed.
The English.dat localization format is one of the more stable file formats; the legacy Localization guide's format reference is still accurate. The master bundle format has evolved across Unity versions, and the legacy guide's bundle build procedure may not produce bundles that are compatible with the current engine. The developer should use the current build tool or the current Unity Editor's asset bundle build pipeline, not the legacy guide's build procedure.
Workflow differences
The modding workflow has evolved from a primarily manual process (create files in a text editor, manually place them in the correct folder, manually test in-game) to a more automated process supported by the SDK's build tooling and the Unity Editor integration. The legacy guides' workflow descriptions assume the manual, text-editor-based approach, which is functional but slower than the current workflow.
The modern developer should adopt the current workflow where it exists and should treat the legacy workflow as a fallback for steps that are not yet covered by the current tooling. The developer should not revert to the manual workflow for steps that the current tooling automates, even if the legacy guide describes the manual approach as the standard method.
Migration path from legacy approaches to current
A developer who has a mod that was built using legacy Steam Guide workflows should migrate the mod to the current documentation set's workflows. The migration is incremental - the developer should not attempt to migrate everything at once - and should prioritise the areas where the legacy approach is most likely to cause compatibility issues with the current SDK.
Step 1: Audit the mod against the current field reference
Open every .dat file in the mod and compare the fields present against the current field reference in the official documentation or the 57 Studios knowledge base. Identify fields that are missing from the legacy .dat file but present in the current reference (these may need to be added), fields that are present in the legacy file but not in the current reference (these may be deprecated), and fields whose valid values have changed.
The audit produces a migration checklist: a list of every field that needs to be added, removed, or updated. The developer should work through the checklist systematically, making one category of changes at a time and testing after each category.
Step 2: Update the Unity project to the current version
If the mod's Unity project was built against an older Unity version, the developer should open the project in the current Unity Editor version recommended by the SDK. Unity will automatically upgrade the project assets and may flag API deprecations, shader compilation errors, or asset import warnings. The developer should resolve each warning and error before proceeding.
The Unity upgrade step is the most likely to produce unexpected issues because Unity's automatic upgrade process cannot resolve all version differences. The developer should budget substantial time for this step and should maintain a backup of the pre-upgrade project.
Step 3: Rebuild master bundles with the current build pipeline
The legacy guide's bundle build procedure should be replaced with the current build pipeline. The developer should use the SDK's Build Tool or the current Unity Editor's asset bundle build pipeline to rebuild every master bundle in the mod. The rebuilt bundles should be tested in the current Unturned version to confirm they load correctly.
Step 4: Update the Workshop listing and metadata
If the mod is published on the Steam Workshop, the developer should update the Workshop listing to reflect the migrated content. The listing should note the migration, describe any changes that affect player experience, and provide the current compatibility information. The legacy upload procedure should be replaced with the current Workshop submission workflow.
Step 5: Test comprehensively
After migration, the developer should test every aspect of the mod in the current Unturned version: item spawning, gameplay behaviour, visual appearance, audio, and multiplayer compatibility. The testing should cover both the migrated content and any content that was not changed during migration, because changes to the Unity project or the build pipeline can affect assets that the developer did not intentionally modify.
The flowchart above describes the migration workflow as a linear sequence with a test-and-fix loop at the end. The developer should not skip steps or reorder them; the sequence is designed to catch issues at the earliest possible stage and to prevent cascading failures that are difficult to diagnose.
Disclaimer about legacy content accuracy
The legacy Steam Guide tutorials and video tutorials were accurate at the time they were published, but they have not been maintained to reflect changes in Unturned, Unity, or third-party tools. The developer should treat every statement in a legacy guide as potentially outdated until verified against the current documentation, the current SDK behaviour, or the current tool version.
The official SDG documentation's recommendation for video tutorials applies equally to the Steam Guides: "If you refer to a video tutorial (official or otherwise), we recommend double-checking the information with our written documentation when possible." The same double-checking discipline should be applied to the Steam Guides: use them as references, not as authorities, and verify their content against the current documentation before relying on it.
The 57 Studios cohort has observed that the most common source of confusion among new mod developers who consult legacy guides is the assumption that the guide's specific procedures are still correct. A developer who copies a legacy guide's Unity Editor menu navigation and finds that the menu items have moved may conclude that they have made an error, when in fact the guide is simply out of date. The developer should approach legacy content with the expectation that user interface details will have changed and should use the current documentation to resolve discrepancies.
Legacy content and the U3 SDK
The legacy Steam Guides were written before the U3 SDK release. They describe modding workflows for the pre-SDK era, where mods were asset-only creations that extended the base game without access to the source code. The SDK has fundamentally changed the modding landscape by providing source code access, and the legacy guides do not describe SDK-based development workflows. A developer building an SDK-based mod should use the legacy guides only for asset authoring reference, not for development workflow guidance. The SDK development workflow is documented in the current official documentation and in the SDK repository's own documentation.
Frequently asked questions
Should I read the legacy guides before starting a new mod?
No. Start with the current documentation - the official SDG modding documentation and the 57 Studios Modding Knowledge Base. The legacy guides are supplemental resources that should be consulted only for specific topics that the current documentation does not cover in sufficient detail, primarily Unity Editor setup procedures. A developer who starts with the legacy guides will learn workflows that have been superseded and will need to unlearn them later.
Which legacy guide is the most valuable for a current developer?
The Items Steam Guide is the most valuable legacy resource, because its Unity Editor setup content has not been fully reproduced in the current documentation. The developer who is creating item assets and needs detailed Unity Editor prefab authoring guidance will find content in the Items guide that complements the current .dat field reference articles.
How do I know if a legacy guide's content is still accurate?
Cross-reference the guide against the current official documentation. If the current documentation covers the same topic, the current documentation is the authoritative source. If the current documentation does not cover the topic, test the procedure in the current Unity Editor version and the current Unturned version. If the procedure works, document your findings; if it does not, the procedure is outdated and should not be followed.
Are there any legacy guides that are completely obsolete?
The Upgrading from Unity 5 LTS to Unity 2017 LTS guide is the most narrowly applicable and is only relevant for developers maintaining mods from that specific era. The Third-Party Modules guide describes a pattern that is distinct from current modding practice and is primarily of historical interest. Most other legacy guides contain at least some content that is still relevant, particularly the Unity Editor setup sections.
Can I use legacy video tutorials as my primary learning resource?
No. The official SDG documentation states that many video tutorials "have gradually become outdated" and "do not accurately represent the current modding features available, or may contain incorrect information." The videos are listed for completeness, not as recommended resources. The developer who is learning Unturned modding should use the current written documentation as the primary resource and should supplement with legacy videos only for creative and conceptual content, not for procedural instruction.
How do the legacy guides relate to the U3 SDK?
The legacy guides predate the U3 SDK and describe modding in the pre-SDK era. They are relevant for asset authoring in the SDK era, because the asset authoring workflow (creating .dat files, building master bundles in Unity) has not fundamentally changed. They are not relevant for SDK development workflow (modifying source code, building standalone distributions, configuring custom forks), because those workflows did not exist when the legacy guides were written.
What should I do if I find contradictory information between a legacy guide and the current documentation?
Trust the current documentation. The current documentation is maintained alongside the game's development and reflects the current state of the modding API. The legacy guides may contain information that was accurate at the time of publication but has been superseded by later game updates. In the rare case that the current documentation appears to be incorrect and the legacy guide appears to be correct, test both claims against the current Unturned version and report the discrepancy through the appropriate feedback channel.
Are there community-made legacy resources beyond the official Steam Guides?
Yes. Many community members created their own Steam Guides, forum posts, and video tutorials during the pre-SDK era. These community resources are not catalogued in the official documentation and vary widely in quality and accuracy. The developer who encounters a community legacy resource should evaluate it by the same criteria applied to the official legacy guides: cross-reference against the current documentation, test any procedures against the current tool versions, and treat unverified claims with caution.
How do I cite a legacy guide in my own mod documentation?
If the legacy guide contains information that your mod documentation references, cite the guide by its Steam Guide title and note that the content may be outdated. Provide the current documentation equivalent where one exists. The citation should make clear to the reader that the legacy guide is a supplementary reference, not the primary source. Example citation: "The Unity prefab hierarchy described in the legacy Items Steam Guide (note: some interface details may have changed in current Unity versions)."
Will SDG ever update the legacy guides?
There is no indication in the official documentation that SDG plans to update the legacy Steam Guides. The official documentation states that the guides "have been superseded by our documentation here," which suggests that SDG views the current documentation as the replacement for the legacy guides rather than as a supplement that exists alongside them. The developer should assume that the legacy guides will not receive updates and should plan their information strategy around the current documentation as the primary resource.
Best practices
- Start with the current documentation before consulting any legacy resource.
- Cross-reference every legacy guide procedure against the current Unity Editor version before following it.
- Use legacy videos for creative and conceptual content only, not for procedural instruction.
- Verify legacy
.datfield references against the current official documentation before using them. - Budget migration time when updating a legacy-era mod to the current SDK.
- Maintain the distinction between legacy guide content (which may be outdated) and current documentation content (which is maintained).
- Do not reference legacy guides as authorities in new mod documentation.
- When an legacy guide contains content not yet covered in current documentation, test it against the current tool versions and document your verified findings.
- Treat the U3 SDK as a dividing line: content before the SDK describes pre-SDK workflows; content after the SDK describes current workflows.
- Share verified legacy-to-current migration findings with the development community to reduce the collective burden of rediscovering the same version differences.
Appendix A: Legacy guide quick-reference matrix
| Guide | Primary value | Verification needed | Superseded by |
|---|---|---|---|
| Items | Unity prefab setup for items | Unity Editor interface changes | Item type-specific articles in this knowledge base |
| Vehicles | Vehicle prefab hierarchy, physics setup | Unity physics changes | Current vehicle documentation |
| Objects | Object prefab authoring | Unity prefab workflow changes | Current object documentation |
| Misc. Assets | Unity setup for animals, effects, resources | Unity interface changes | Current documentation for each asset type |
| Maps | Terrain and foliage authoring concepts | Unity terrain tool changes | Current map documentation |
| Localization | English.dat format reference | Minimal; format is stable | Current localization articles |
| Third-Party Modules | Historical reference only | N/A - primarily obsolete | Current plugin and module documentation |
| Workshop Upload | Workshop conceptual background | Steam interface changes | Steam Workshop Submission |
| Unity Upgrade | Unity 5 to 2017 change list | Only relevant for very old mods | Unity official migration documentation |
Appendix B: Video tutorial evaluation matrix
| Video | Conceptual value | Procedural value | Recommendation |
|---|---|---|---|
| Hosting a Dedicated Server on Windows | Medium - client-server architecture | Low - procedure has changed | Use for concepts; verify procedures |
| Uploading Skins to the Curated Workshop | Low - niche topic | Very low - process has changed | Historical interest only |
| Creating Custom Songs | High - audio content design | Low - import procedures may have changed | Use for creative guidance |
| Foliage Upgrade Overview | Low - system has been revised | Very low - interface has changed | Historical interest only |
| Devkit 101 and Landscapes | High - editor orientation | Low - interface has changed | Use for conceptual orientation |
| Spawn Tables | Medium - spawning system concepts | Medium - format is relatively stable | Verify against current editor |
| Building Models | High - 3D modelling fundamentals | Medium - tool-independent principles | Use for modelling principles; verify export settings |
Appendix C: Diagnostic table - common legacy-to-current migration issues
| Symptom | Legacy-era cause | Resolution |
|---|---|---|
| Prefab loads but is invisible | Prefab format changed across Unity versions | Re-create the prefab in the current Unity Editor |
.dat fields produce unexpected behaviour | Field semantics changed in newer Unturned versions | Compare against current field reference; adjust values |
| Asset bundle fails to load | Bundle format changed across Unity versions | Rebuild the bundle with the current build pipeline |
| Pink material on model | Shader referenced in legacy guide is no longer available | Assign a current shader to the material |
| Animator Controller states not firing | Animation event system changed across Unity versions | Re-author animation events in the current Animator Controller |
| Workshop listing shows incorrect metadata | Workshop metadata format changed | Update Workshop listing through the current Steam Workshop interface |
| Server fails to start | Server configuration format changed | Update server configuration to current format |
| Localized text not appearing | Localization file encoding or naming convention changed | Verify UTF-8 encoding and current naming convention |
Appendix D: External references
- Smartly Dressed Games modding documentation - Legacy Tutorials chapter - the official Legacy Tutorials reference in the SDG documentation.
- Unturned on Steam - Guides section - the Steam Guides section for Unturned, where the legacy guides are hosted.
What is the relationship between Steam Guides and the Steam Community Hub?
Steam Guides are a feature of the Steam Community Hub for each game. They are user-generated tutorial posts that are hosted on Steam's servers and accessible through the game's Community Hub page. The legacy modding guides were posted as Steam Guides for the Unturned Community Hub, and they remain accessible there even though the official documentation has moved to a separate documentation site. A developer searching the Unturned Community Hub for modding information may encounter the legacy guides alongside current community-created guides, and the evaluation criteria in this article apply to any Steam Guide encountered in that context.
Can I create my own Steam Guide for current modding practices?
Yes. Steam Guides remain an active feature of the Steam Community Hub, and any Steam user can create a guide for Unturned. A developer who creates a modding guide should clearly date the guide, note the Unity version and Unturned version the guide was written for, and include a disclaimer that the guide may become outdated as the tools evolve. The 57 Studios cohort recommends that community guides reference the current official documentation as the authoritative source and position themselves as supplementary rather than as replacements for the official documentation.
How do I access the legacy Steam Guides?
The legacy Steam Guides are accessible through the Unturned Steam Community Hub, under the Guides tab. The official SDG documentation's Legacy Tutorials chapter lists the guide titles; the developer can search for those titles in the Guides section to locate the specific guides. Some legacy guides may have been archived, hidden, or removed by their authors; if a guide listed in the official documentation is not accessible, the developer should consult the current documentation for the equivalent content and should not assume the guide's content is essential.
What is the difference between a Steam Guide and the official documentation?
Steam Guides are community-authored (even when authored by SDG, they are published through the Steam Guides platform, not through an official documentation system). The official documentation is maintained by SDG on a dedicated documentation site and is versioned alongside the game's development. Steam Guides are snapshots of knowledge at the time they were written; the official documentation is a living reference that is updated with each game version. The official documentation should be the developer's primary reference; Steam Guides should be supplementary.
Are there any legacy resources that cover server hosting in detail?
The Hosting a Dedicated Server on Windows video tutorial, listed in the legacy video catalogue, covers server hosting. The server hosting landscape has changed substantially since that video was produced, particularly with the release of the U3 SDK, which enables SDK-based server hosting that was not possible in the pre-SDK era. The developer should consult the current server hosting documentation for the current procedures and should use the legacy video only for the architectural concepts of client-server multiplayer.
How should I approach a legacy guide that has no current documentation equivalent?
Test every procedure in the legacy guide against the current Unity Editor version and the current Unturned version. Document which procedures work and which do not. If the procedures work, note the current tool versions and any minor interface adaptations that were needed. Share the verified findings with the development community through the appropriate channel (GitHub Discussions, community Discord, or a community-maintained guide). The developer who verifies legacy content against current tools performs a service for every future developer who encounters the same legacy guide.
What is the most common way new developers misuse legacy guides?
The most common misuse pattern is treating a legacy guide as a step-by-step tutorial for current modding. The developer follows the guide's specific menu navigation, button clicks, and file paths without checking whether those interface elements still exist in the current tools. When something does not work (because the interface has changed), the developer assumes they have made an error rather than that the guide is outdated, and they waste time debugging a problem that does not exist. The correction is to approach legacy guides as conceptual references rather than as procedural tutorials and to verify every procedure against the current tools before following it.
Do I need to consult the legacy guides to be a competent Unturned modder?
No. The current documentation, the U3 SDK repository, and the 57 Studios Modding Knowledge Base together provide sufficient information to build complete, current Unturned mods without consulting any legacy resource. The legacy guides are supplementary; they fill gaps in the current documentation's coverage, particularly around Unity Editor setup procedures. A developer who never consults a legacy guide can still build excellent mods. A developer who consults legacy guides without verifying their content against current documentation may build mods that are based on outdated assumptions.
Appendix E: Migration checklist template
The following template is a recommended format for planning and tracking the migration of a legacy-era mod to the current SDK. The developer should complete one row per mod component and update the status column as migration progresses.
| Component | Legacy approach used | Current documentation reference | Migration status | Notes |
|---|---|---|---|---|
| Example: Item .dat files | Fields from legacy Items guide | Item Asset Anatomy | In progress | Added 3 new fields; removed 1 deprecated field |
| Example: Master bundle | Legacy bundle build procedure | Master Bundle Export | Not started | Bundle format may be incompatible |
The checklist ensures that no component is overlooked during migration and that the developer has a clear reference for which current documentation to consult for each component.
Appendix F: Unity version timeline for modding documentation
Understanding the Unity version landscape that the legacy guides were written against helps the developer contextualise the content. The following timeline shows the major Unity versions that are relevant to Unturned modding history and the documentation eras that correspond to each version.
| Unity version | Approximate era | Documentation available | Relevance to current modding |
|---|---|---|---|
| Unity 5 LTS | 2015-2017 | Steam Guides (primary) | Legacy; most procedures outdated |
| Unity 2017 LTS | 2017-2019 | Steam Guides, early official docs | Legacy; some procedures still relevant |
| Unity 2018-2019 | 2019-2021 | Official documentation (maturing) | Some procedures still relevant |
| Unity 2020-2021 | 2021-2024 | Official documentation (current) | Most procedures still relevant |
| Unity 2022+ | 2024-present | Official documentation, U3 SDK | Current; use as primary reference |
The timeline shows the progression from Steam-Guide-only documentation in the Unity 5 era to the current multi-source documentation ecosystem. A legacy guide written in the Unity 5 era (the oldest guides) is substantially more likely to contain outdated procedural content than a legacy guide written in the Unity 2017 era. The developer can use the guide's publication date, if available, to estimate how much verification the guide's procedures are likely to need.
Appendix G: Community-contributed legacy resource evaluation
Beyond the official SDG-authored Steam Guides, the community has produced a substantial volume of legacy content - forum posts, Reddit threads, YouTube tutorials, and community wiki pages. The 57 Studios cohort has evaluated a sample of these resources and offers the following general guidance for developers who encounter them.
Forum posts and discussion threads
Forum posts from the pre-SDK era should be evaluated by the age of the post and the specificity of the content. A post from 2016 describing a specific .dat field value may be accurate if the field has not changed; a post from 2016 describing a Unity Editor procedure is more likely to be outdated. The developer should cross-reference any claim from a legacy forum post against the current documentation before relying on it.
Community YouTube tutorials
Community-produced YouTube tutorials vary widely in quality and accuracy. A tutorial from a well-known community modder who is still active in the development community is more likely to contain accurate information than a tutorial from an unknown creator. The developer should evaluate community tutorials by the same criteria applied to official legacy videos: separate conceptual content (which may still be valuable) from procedural content (which should be verified), and cross-reference all claims against the current documentation.
Community wiki pages
Community-maintained wikis (such as the Unturned Fandom wiki) may contain modding information that is not present in the official documentation. The developer should treat community wiki content with the same caution applied to legacy guides: verify before relying. Community wikis are not maintained by SDG and may contain information that is outdated, inaccurate, or based on community speculation rather than verified testing. The developer should cross-reference any community wiki claim against the current official documentation or against direct testing in the current Unturned version.
- Upcoming Features - the previous article; covers the official modding feature roadmap.
- Getting Started with Unturned Modding - the practical setup guide for new mod developers, which supersedes the legacy setup procedures.
- What is Modding? - the discipline of modding; provides context for the historical progression from legacy guides to current documentation.
- What is Unturned? - the foundational game introduction.
- Official FAQ - the official FAQ documenting the current SDK and licensing landscape.
- Steam Workshop Submission - the current Workshop publishing workflow that supersedes the legacy upload guide.
- Master Bundle Export - the current Unity bundling workflow that supersedes the legacy guide's bundle build procedure.
- Item Asset Anatomy - the current item field reference that supersedes the legacy Items guide's field tables.
- Melee Asset - the current melee weapon reference; an example of the current documentation standard that the legacy guides preceded.
- Smartly Dressed Games modding documentation - the official current documentation.
Document history
| Version | Date | Author | Notes |
|---|---|---|---|
| 1.0 | 2026-07-26 | 57 Studios | Initial publication. Complete catalogue of legacy Steam Guide and video tutorials from the official SDG Legacy Tutorials chapter, with relevance evaluation, migration guidance, diagnostic tables, and cross-references to current documentation equivalents. |