Workshop Tag Taxonomy and Governance

Intermediate40-60 minutesWindowsSteam Workshop

Every Steam Workshop listing exists in a competitive discovery environment. When a player types "military vehicle" into the Unturned™ Workshop search bar, the ranking algorithm evaluates every submitted Workshop entry and surfaces those with the highest relevance scores. Tags are among the most weighted signals in that evaluation. A listing that applies tags correctly, consistently, and deliberately appears where its target audience is already searching. A listing that applies tags arbitrarily — selected in thirty seconds during the upload flow with no policy document, no revision cadence, and no cross-portfolio harmonization — competes at a structural disadvantage against listings that treat tag selection as a documented organizational process.

This article describes the 57 Studios™ Tag Taxonomy and Governance Framework: the complete system by which every Unturned™ mod published under the 57 Studios™ brand receives a tag assignment that has been evaluated against a decision matrix, reviewed for conflicts, verified against the authoritative tag list, and scheduled for periodic re-assessment. The framework is designed to operate at scale — across a portfolio of dozens of active listings — without accumulating inconsistencies that degrade average listing performance over time.

Modders operating a single listing will find the framework useful as a quality gate. Modders operating three or more listings will find it necessary. Organizations operating ten or more listings across multiple contributors will find it indispensable.

Prerequisites

• An active Steam account with at least one published or draft Unturned™ Workshop entry.
• Familiarity with the Steam Workshop submission workflow. If you have not yet submitted a Workshop entry, read Steam Workshop Submission first, then return to this article.
• Access to the 57 Studios™ internal tag inventory spreadsheet or an equivalent tracking document for your organization.
• Write access to the listing's Workshop entry so that tag changes can be applied.

What you'll learn

• How the 57 Studios™ Tag Taxonomy and Governance Framework is structured and why each layer exists.
• How to apply the four-tier tag hierarchy to any Unturned™ mod type.
• How to use the Tag Selection Decision Matrix to move from mod description to approved tag set in a reproducible way.
• How to identify and resolve tag conflicts within a single listing and across a portfolio.
• How to maintain a tag inventory that stays accurate as the Workshop's official tag list changes.
• How to execute the Annual Tag Review Process and document its outcomes.
• How to deprecate tags that have been removed or renamed by Smartly Dressed Games.
• How to harmonize tags across a multi-contributor organization without central bottlenecks.
• The full 57 Studios™ reference tag taxonomy table covering every tag category relevant to Unturned™ Workshop content.
• Cohort-validated tag combinations for the most common Unturned™ mod archetypes.
• Common tag mistakes and the corrective procedure for each.

---

Part 1 — Foundational Concepts

1.1 Why Tag Governance Is an Organizational Discipline

Tag governance is the formal management of how metadata labels are selected, maintained, and retired across a body of content. In enterprise content management systems, tag governance frameworks are standard operating procedure. The Steam Workshop is a content repository, and the discovery problems it creates for publishers are structurally identical to those in larger content management contexts: inconsistent labeling erodes search relevance, ad-hoc tag decisions produce orphaned or conflicting entries, and the absence of a review cadence means that tags applied three years ago may no longer reflect the mod's content or the Workshop's current indexing vocabulary.

At 57 Studios™, tag governance is assigned the same project priority as preview image compliance and description accuracy. The reasoning is straightforward: a mod that cannot be found by its target audience does not generate subscriptions, does not generate reviews, and does not generate the community signal that drives organic Workshop ranking improvements over time. Tag governance is, in effect, a compound-interest system: consistent, policy-compliant tags applied at launch and maintained through periodic review produce cumulative discoverability advantages that ad-hoc approaches cannot replicate.

Governance Principle GP-001: Tag selection is a documented decision, not an in-the-moment choice. Every tag applied to a 57 Studios™ listing must be traceable to a policy rule.

Governance Principle GP-002: The authoritative tag reference is the live Unturned™ Workshop tag list as rendered in the Steam Workshop upload interface at https://partner.steamgames.com/doc/features/workshop. Internal documentation is secondary to the live source.

Governance Principle GP-003: No contributor applies tags to a 57 Studios™ listing without consulting the tag inventory. The inventory is the single source of truth for approved tags within the portfolio.

1.2 Steam Workshop Tag Mechanics

Before defining the governance framework, it is necessary to understand how the Steam Workshop processes tags at a technical level.

Tags on a Workshop entry are stored as a flat array of string values. The Workshop search and filter system uses these values to match listings against user queries. The matching is exact against the tag value; a tag of Vehicle does not match a user filter for Vehicles. Valve's documentation at https://partner.steamgames.com/doc/features/workshop specifies that the available tags for a given game are defined by the game developer — in Unturned™'s case, by Smartly Dressed Games — and that only the tags defined in the game's Workshop configuration appear in the tag picker UI.

This has a critical governance implication: tags that are not on the official list cannot be applied through the standard upload interface. Attempts to apply unofficial tags through API methods produce entries that do not match the filter categories that players use to browse. The 57 Studios™ framework therefore treats the official tag list as a closed vocabulary, not a starting point for creative expansion.

1.3 Tag Limits and Constraints

The Unturned™ Workshop imposes a practical limit on the number of tags that can be applied to a single listing. The interface renders a finite set of checkboxes; selecting all of them is possible but counterproductive. The 57 Studios™ framework imposes a stricter internal limit:

Constraint	Official Workshop Limit	57 Studios™ Policy Limit
Minimum tags	1	3 (Primary + at least 2 Secondary)
Maximum tags	All available	8 (prevents tag dilution)
Mandatory tier	None	Primary Category (exactly 1)
Discretionary tiers	N/A	Secondary, Content Type, Technical

The rationale for the 8-tag ceiling is detailed in Part 5 — Common Tag Mistakes. The rationale for the 3-tag floor is that a listing with only 1 tag provides insufficient signal for the Workshop ranking algorithm to place it accurately in category browse views.

---

Part 2 — The Tag Hierarchy

The 57 Studios™ tag hierarchy assigns every applicable Workshop tag to one of four tiers. The tiers are evaluated in sequence during tag selection. A tag from a lower tier is never selected before the tiers above it are satisfied.

2.1 Tier 1 — Primary Category

Definition: The single tag that describes what kind of Workshop content the listing is. The Primary Category tag must map to the highest-level filter a player would use to browse for this content type. Exactly one Tier 1 tag is applied to every listing. No listing is published without a Tier 1 tag.

Approved Tier 1 values for Unturned™ Workshop:

Tag Value	Applies To
Vehicle	Driveable vehicles (land, sea, air)
Item	Wearable items, tools, consumables, weapons
Map	Full maps, arena maps, playable environments
NPC	Non-player character packs
Character	Cosmetic character skins
Object	Placeable environment objects
Localization	Translation and localization packs

Rule T1-001: If a mod contains multiple primary content types (e.g., a vehicle pack with custom items), select the Tier 1 tag that describes the majority content type by asset count. Document the secondary content type in the Tier 2 selection.

Rule T1-002: The Tier 1 tag must match the mod's physical file structure. A folder using the Vehicle asset type convention must carry the Vehicle tag. Mismatches between folder structure and Tier 1 tag are treated as a data integrity error.

2.2 Tier 2 — Secondary Category

Definition: Tags that describe the thematic or functional subcategory of the mod. Tier 2 tags answer the question "what kind of [Tier 1 content] is this?" A listing may carry 1 to 3 Tier 2 tags.

Tag Value	Tier 1 Parent	Description
Military	Vehicle, Item, Object	Armed forces aesthetic or function
Civilian	Vehicle, Item, Object	Non-combat everyday items
Survival	Item, Map	Core survival mechanics focus
Adventure	Map, Item	Exploration or quest-oriented
Arena	Map	Structured PvP or PvE encounters
Role Play	Map, Character, Item	RP server or scenario content
Curated	Any	Officially curated by SdG (system-assigned; do not self-apply)
Fantasy	Item, Character, Object	Non-realistic or high-fantasy aesthetic
Sci-Fi	Vehicle, Item, Object	Science-fiction aesthetic or technology
Horror	Map, Object, Character	Atmospheric horror content

Rule T2-001: The Curated tag is assigned by Smartly Dressed Games. It must never be self-applied. Applying it to a non-curated listing constitutes a metadata violation and may result in Workshop policy action.

Rule T2-002: No more than 3 Tier 2 tags are applied to a single listing. If a mod legitimately spans more than 3 secondary categories, the selection must be narrowed to the 3 that best describe the mod's primary audience's browsing behavior.

2.3 Tier 3 — Content Type

Definition: Tags that describe the nature of the content delivery — how the content is structured and delivered to the subscriber, rather than what the content is. Tier 3 is optional; 0 to 2 Tier 3 tags are applied.

Tag Value	Description
Pack	A collection of multiple assets under one entry
Overhaul	Replaces or significantly modifies existing base-game content
Bundle	Thematically grouped items sold or distributed together
Patch	Compatibility or bug-fix addendum to another Workshop entry
Beta	Pre-release or actively iterated content

Rule T3-001: Beta is a temporary tag. It must be removed within 30 calendar days of the mod reaching a stable release state. The Annual Tag Review Process (see Part 4) must verify that no listing carries Beta beyond this window.

2.4 Tier 4 — Technical Attributes

Definition: Tags that describe technical properties of the mod that affect how subscribers interact with it — server-side requirements, client-side compatibility flags, or dependency relationships. Tier 4 is optional; 0 to 2 Tier 4 tags are applied.

Tag Value	Description
Vanilla Friendly	Does not alter base-game balance
Multiplayer	Verified functional in multiplayer environments
Workshop Dependency	Requires another Workshop entry to function
Server Side	Designed for server-side-only deployment

Rule T4-001: Workshop Dependency must only be applied when the mod genuinely cannot function without another listed Workshop entry. The dependency entry's Workshop ID must be documented in the listing description.

Rule T4-002: Vanilla Friendly is a trust signal to the player community. It must only be applied after functional testing confirms no base-game balance disruption. Misapplication erodes listing credibility.

---

Part 3 — Tag Selection Decision Matrix

The Tag Selection Decision Matrix is a structured evaluation tool. It converts a mod description into a candidate tag set through a series of documented decision points. Every 57 Studios™ tag assignment must be traceable to a completed Decision Matrix evaluation.

3.1 Matrix Inputs

Before beginning matrix evaluation, the following inputs must be prepared:

1. Mod summary statement: One sentence describing what the mod adds or changes.
2. Asset type list: The file extensions and folder conventions used by the mod (e.g., Vehicle/, .unity3d, .dat).
3. Target player profile: The primary player type this mod serves (e.g., RP server operators, PvP players, singleplayer survival players).
4. Interaction with base game: Whether the mod adds to, replaces, or depends on base-game content.

3.2 Matrix Steps

Step 1 — Resolve Tier 1.

Map the asset type list to the Tier 1 approved value table. If the mapping is unambiguous, record the Tier 1 tag and proceed. If the mapping produces multiple candidates, apply Rule T1-001 (majority asset type wins) and document the tie-breaking reasoning in the tag assignment record.

Step 2 — Identify Tier 2 candidates.

From the Tier 2 table, list every tag whose Tier 1 parent matches the selected Tier 1 tag and whose description aligns with the mod summary statement. This produces a candidate list of 1–6 tags.

Step 3 — Filter to maximum 3.

Score each Tier 2 candidate on a 1–3 scale across two dimensions:

Dimension	Score 3	Score 2	Score 1
Search intent alignment	Tag exactly matches how target players search	Tag partially matches expected search terms	Tag is only loosely related to expected search behavior
Content coverage	Tag describes ≥60% of the mod's content	Tag describes 30–59% of content	Tag describes <30% of content

Sum the scores. Select the 3 candidates with the highest combined score. In a tie, prefer the tag with higher search intent alignment, as intent alignment is the more direct discoverability driver.

Step 4 — Evaluate Tier 3.

Review the Tier 3 table. Apply only if:

• The mod contains 5 or more distinct assets (qualifies for Pack).
• The mod replaces base-game assets (qualifies for Overhaul).
• The mod is in active development with breaking changes expected (qualifies for Beta).

If none of these conditions apply, Tier 3 is left empty.

Step 5 — Evaluate Tier 4.

Verify each Tier 4 candidate against the technical test criteria defined in the tag definitions. Do not infer Tier 4 tags from the mod description alone; functional testing is required.

Step 6 — Compile the final tag set.

Assemble the Tier 1 + Tier 2 + Tier 3 + Tier 4 selections. Verify total count is between 3 and 8. If below 3, re-examine whether Tier 3 or Tier 4 tags were incorrectly excluded. If above 8, apply the over-tagging reduction protocol (see Part 5.1).

---

Part 4 — Tag Conflict Resolution

Tag conflicts occur when two or more tags in a listing's tag set contradict each other, overlap redundantly, or create a false representation of the mod's content. Conflicts undermine the integrity of the tag set and reduce the precision of the Workshop's relevance matching.

Governance Principle GP-004: Every tag set is subject to a conflict check before publication. Conflict checks are mandatory, not advisory.

4.1 Conflict Types

Type A — Logical contradiction. Two tags that cannot simultaneously be true. Example: a listing carrying both Vanilla Friendly and Overhaul. An overhaul by definition alters base-game content; it cannot simultaneously be vanilla-friendly. Resolution: remove Vanilla Friendly.

Type B — Hierarchical redundancy. A Tier 2 tag and a Tier 3 tag that describe the same property. Example: a listing carrying both Pack (Tier 3) and a Tier 2 tag implying collection status, creating a doubled description with no additive information. Resolution: retain the higher-tier tag; remove the lower-tier redundancy.

Type C — Cross-listing inconsistency. A tag applied to one 57 Studios™ listing in a series that is absent from related listings in the same series. Example: a three-part vehicle pack where Part 1 and Part 2 carry Multiplayer but Part 3 does not, despite identical deployment requirements. Resolution: apply the tag uniformly across all entries in the series, or document the exception with a technical justification.

Type D — Scope mismatch. A tag whose defined scope does not match the mod's content coverage. Example: a single-vehicle listing carrying Pack. Resolution: remove the out-of-scope tag.

4.2 Conflict Resolution Protocol

When a conflict is identified, the following steps are executed in order:

1. Document the conflict. Record the conflict type, the conflicting tags, and the listing entry's Workshop ID in the tag inventory.
2. Identify the governing rule. Reference the specific Tier rule or Governance Principle that defines the correct resolution.
3. Remove the non-conforming tag. Do not add new tags to resolve a conflict; remove the tag that violates policy.
4. Update the listing. Apply the corrected tag set through the Workshop management interface.
5. Update the inventory. Record the resolution date and the outcome in the tag inventory log.
6. Verify recurrence. Search the full portfolio for other listings that may carry the same conflicting combination. If found, apply the same resolution.

---

Part 5 — Common Tag Mistakes

5.1 Over-Tagging

Over-tagging is the application of tags beyond the content's actual scope, motivated by a belief that more tags increase discoverability. This belief is incorrect. The Workshop ranking algorithm interprets a high tag count on a narrow-scope listing as a relevance signal mismatch — the listing claims membership in many categories but delivers content specific to few. This reduces the listing's precision score in each tagged category, producing lower rankings across all categories rather than higher rankings in any.

Symptoms of over-tagging:

• Tag count exceeds 8 for a mod with a single clearly defined content type.
• Tags from multiple Tier 2 categories that do not share a common audience.
• Tier 4 tags applied without functional testing verification.
• Tags selected to match popular listings rather than to accurately describe the mod.

Corrective procedure:

1. List all current tags.
2. Score each tag against the Decision Matrix criteria (search intent alignment + content coverage).
3. Remove any tag scoring below a combined 3 out of 6.
4. Verify the remaining set is between 3 and 8 tags.
5. Update the listing and the tag inventory.

5.2 Under-Tagging

Under-tagging is the application of fewer tags than necessary to accurately represent the mod's content and audience. A listing with only a Tier 1 tag provides the Workshop algorithm with insufficient signal to rank it in secondary browse categories where its target audience shops.

Symptoms of under-tagging:

• Tag count of 1 or 2.
• Only Tier 1 tag applied with no Tier 2 selection.
• A mod that serves a specific audience (e.g., RP server operators) without any Tier 2 tag that indicates that audience.

Corrective procedure: Return to Step 2 of the Decision Matrix and regenerate the Tier 2 candidate list. Ensure at least 2 Tier 2 tags are applied.

5.3 Tag-Keyword Stuffing

Tag-keyword stuffing is the selection of tags based on keyword popularity rather than content accuracy. A modder who applies Military to a civilian vehicle because military vehicle searches have higher volume is engaging in tag-keyword stuffing. The practice violates Steam Workshop content guidelines, may trigger review flags, and produces a subscriber experience mismatch — players who subscribe based on a Military tag and receive civilian content leave negative reviews.

Governance Principle GP-005: Tags describe what the mod is. Tags are never selected because they describe what the modder wishes the mod were, or because the tag attracts more traffic than the accurate tag.

Detection method: Review each Tier 2 tag against the mod's asset list. If fewer than 30% of assets relate to the tag, the tag fails the content coverage threshold and must be removed.

5.4 Stale Tags

Stale tags are tags that were accurate at the time of publication but have become inaccurate due to mod updates, Workshop tag list changes, or audience evolution. A mod that launched as Beta and was stabilized eight months ago but still carries the Beta tag is a stale-tag case.

Detection method: The Annual Tag Review Process (see Part 6) is the primary detection mechanism. Between review cycles, stale tags are identified through the Tag Deprecation Policy (see Part 7).

---

Part 6 — The Annual Tag Review Process

The Annual Tag Review Process is a scheduled governance event conducted once per calendar year for every active 57 Studios™ Workshop listing. It is not triggered by mod updates, Workshop changes, or subscriber feedback — it occurs on a fixed calendar schedule regardless of other events. The review date is documented in the tag inventory for each listing.

6.1 Review Trigger

Trigger Type	Review Scope
Annual schedule	Full portfolio
Workshop tag list update by Smartly Dressed Games	All listings carrying the affected tag
Significant mod content update (>30% new assets)	Affected listing only
Sustained drop in Workshop search impressions (>20% over 90 days)	Affected listing, starting with tag audit

6.2 Review Procedure

Step 1 — Retrieve the current official tag list.

Access https://store.steampowered.com/app/304930/Unturned/ and navigate to the Workshop section. Cross-reference with https://partner.steamgames.com/doc/features/workshop. Document any differences between the current list and the tag inventory's recorded vocabulary.

Step 2 — Compare each listing's current tag set to the Decision Matrix output.

Re-run the Decision Matrix for each listing using the mod's current (post-update) content as input. Compare the matrix output to the listing's applied tags. Any discrepancy is a candidate for correction.

Step 3 — Execute conflict checks.

Apply the conflict resolution protocol to each listing. Document all conflicts found and all resolutions executed.

Step 4 — Update stale tags.

Apply the Tag Deprecation Policy to any deprecated tags. Apply the Beta recency check (>30 days since stable release → remove Beta).

Step 5 — Update the tag inventory.

Record the review completion date, the reviewer's name, and a summary of changes for each listing.

Step 6 — Generate the Review Report.

The review report is a structured document containing:

• Total listings reviewed.
• Total tags audited.
• Conflicts identified and resolved.
• Tags updated or removed.
• Listings requiring follow-up (pending functional testing for Tier 4 tags, etc.).
• Next review date.

Governance Principle GP-006: The Annual Tag Review Report is retained in the 57 Studios™ project records for a minimum of three years. It serves as an audit trail for Workshop compliance purposes.

---

Part 7 — Tag Deprecation Policy

Tag deprecation occurs when a tag is removed from the official Unturned™ Workshop vocabulary, renamed, or redefined by Smartly Dressed Games. A deprecated tag on a listing does not cause an immediate error — the tag may remain in the listing's stored data — but it no longer matches any player filter, rendering it a dead label that consumes one of the listing's available tag slots without providing discovery benefit.

7.1 Deprecation Identification

Deprecated tags are identified through three channels:

1. Proactive monitoring: A member of the 57 Studios™ team subscribes to the Unturned™ developer update communications and notes any tag list changes.
2. Annual Review cross-reference: The Step 1 tag list comparison during the Annual Review identifies retired tag values.
3. Listing audit flag: A listing whose tag set contains a value not present in the current official list is flagged automatically during any inventory reconciliation.

7.2 Deprecation Response

Timeline	Action
Day 0 — deprecation confirmed	Flag affected listings in the inventory with status DEPRECATED-TAG-PENDING
Day 1–7	Identify the replacement tag (if Smartly Dressed Games has issued a successor tag) or the best remaining alternative
Day 7–14	Update all affected listings; remove deprecated tag; apply replacement or alternative
Day 14	Update tag inventory; close DEPRECATED-TAG-PENDING flags; document in the deprecation log

Governance Principle GP-007: Deprecated tags are never simply removed without a replacement evaluation. A tag removal that drops the listing below the 3-tag floor must be compensated with a new compliant tag selection.

---

Part 8 — Cross-Organization Tag Harmonization

57 Studios™ publishes Workshop content across multiple contributors and, in some cases, in collaboration with external organizations such as Horizon Life RP. Tag harmonization ensures that portfolio-level browsing behavior — a player following the 57 Studios™ Workshop profile and browsing its entire catalog — presents a coherent, consistent discovery surface. Harmonization is a cross-listing governance concern, distinct from per-listing quality.

8.1 Harmonization Principles

Principle H-001 — Consistent primary categories. All listings of the same type (all vehicle listings, all item listings) use the same Tier 1 tag. No vehicle listing in the 57 Studios™ portfolio uses a Tier 1 tag other than Vehicle.

Principle H-002 — Consistent series tags. Listings that form a named series (e.g., a three-part military vehicle pack) must share at minimum the same Tier 1 and Tier 2 tags. Tier 3 and Tier 4 may vary per listing within the series based on content-specific attributes.

Principle H-003 — Uniform Multiplayer standard. The Multiplayer tag is applied uniformly across a series if any listing in the series has been verified in multiplayer. It is not applied to any listing in the series if the series has not been multiplayer-verified. Split application within a series is prohibited.

Principle H-004 — External collaborator tag alignment. When publishing content in collaboration with an external organization (e.g., content developed for Horizon Life RP), the 57 Studios™ tag governance framework applies to the 57 Studios™ listing of that content. External organizations' own listings are governed by their own policies; harmonization applies only to 57 Studios™-owned entries.

8.2 Harmonization Process

The harmonization check is a sub-step of the Annual Tag Review Process. It is also triggered whenever a new listing is added to the portfolio. The check consists of:

1. Exporting the complete tag matrix from the tag inventory (all listing IDs with their full tag sets).
2. Grouping listings by Tier 1 category.
3. Comparing Tier 2 tag sets within each group for consistency with series membership.
4. Flagging any cross-listing inconsistencies for conflict resolution.

---

Part 9 — Full Tag Taxonomy Reference

The following table is the 57 Studios™ internal reference for all Unturned™ Workshop tags. It is synchronized against the official Workshop tag list on an annual basis during the Annual Tag Review Process. The "Status" column reflects the tag's current operational status.

#	Tag Value	Tier	Tier 1 Parent(s)	Use Case	Status
1	Vehicle	1	—	Driveable land, sea, or air assets	Active
2	Item	1	—	Weapons, clothing, consumables, tools	Active
3	Map	1	—	Full playable environments	Active
4	NPC	1	—	Non-player character packs	Active
5	Character	1	—	Player cosmetic skins	Active
6	Object	1	—	Placeable environment props	Active
7	Localization	1	—	Translation content	Active
8	Military	2	Vehicle, Item, Object	Armed forces aesthetic/function	Active
9	Civilian	2	Vehicle, Item, Object	Non-combat everyday content	Active
10	Survival	2	Item, Map	Core survival mechanic focus	Active
11	Adventure	2	Map, Item	Exploration or quest content	Active
12	Arena	2	Map	Structured PvP or PvE encounters	Active
13	Role Play	2	Map, Character, Item	RP server or scenario content	Active
14	Curated	2	Any	Officially curated by SdG	System-assigned only
15	Fantasy	2	Item, Character, Object	Non-realistic / high-fantasy	Active
16	Sci-Fi	2	Vehicle, Item, Object	Science-fiction aesthetic	Active
17	Horror	2	Map, Object, Character	Atmospheric horror content	Active
18	Modern	2	Vehicle, Item	Contemporary real-world aesthetic	Active
19	Historical	2	Vehicle, Item	Period-accurate historical content	Active
20	Post-Apocalyptic	2	Map, Object	Collapsed-civilization settings	Active
21	Tropical	2	Map	Tropical biome environments	Active
22	Winter	2	Map	Winter biome environments	Active
23	Desert	2	Map	Arid biome environments	Active
24	Urban	2	Map, Object	City and suburban environments	Active
25	Rural	2	Map, Object	Countryside environments	Active
26	Underground	2	Map	Cave or bunker-dominant maps	Active
27	Offshore	2	Map	Open-water or island settings	Active
28	Infection	2	Map, Item	Zombie/infection survival focus	Active
29	Weapons	2	Item	Primary or secondary weapon content	Active
30	Clothing	2	Item, Character	Wearable cosmetic content	Active
31	Vehicles	2	Vehicle	(Legacy alias for Vehicle; see deprecation notes)	Review
32	Pack	3	Any	Multi-asset collection entry	Active
33	Overhaul	3	Any	Replaces base-game content	Active
34	Bundle	3	Any	Thematically grouped collection	Active
35	Patch	3	Any	Compatibility or bug-fix addendum	Active
36	Beta	3	Any	Pre-release or actively iterated	Temporary
37	Vanilla Friendly	4	Any	No base-game balance disruption	Active
38	Multiplayer	4	Any	Verified in multiplayer context	Active
39	Workshop Dependency	4	Any	Requires another Workshop entry	Active
40	Server Side	4	Any	Server-side deployment only	Active
41	Client Side	4	Any	Client-side only; no server install	Active
42	Standalone	4	Any	No dependency on other entries	Active
43	Optimized	4	Vehicle, Map, Object	Performance-validated at low settings	Active
44	High Poly	4	Vehicle, Object, Character	High-detail assets; performance note	Active
45	Low Poly	4	Vehicle, Object, Character	Intentionally low-detail assets	Active

---

Part 10 — Cohort-Validated Tag Combinations

The following combinations are derived from 57 Studios™ portfolio performance data and represent the tag sets associated with above-average Workshop search ranking for their respective mod archetypes. These combinations are starting points, not mandatory selections. The Decision Matrix must still be applied to each listing individually.

Mod Archetype	Tier 1	Tier 2	Tier 3	Tier 4	Notes
Military vehicle pack (land)	Vehicle	Military, Pack	Pack	Multiplayer, Vanilla Friendly	Remove Vanilla Friendly if weapons are modified
RP server item bundle	Item	Role Play, Civilian	Bundle	Server Side	Server Side only if server-deploy intended
Survival map (temperate)	Map	Survival, Rural	—	Multiplayer, Vanilla Friendly	Add Winter or Desert for non-temperate biomes
Infection zombie map	Map	Infection, Survival	—	Multiplayer	Horror optional if atmosphere is a primary feature
Cosmetic character skin	Character	Clothing	—	Vanilla Friendly	Single skins rarely warrant Pack; use only for multi-skin entries
NPC merchant pack	NPC	Survival, Role Play	Pack	Server Side	Confirm multiplayer behavior before adding Multiplayer
Sci-fi vehicle overhaul	Vehicle	Sci-Fi	Overhaul	Multiplayer	Vanilla Friendly is incompatible with Overhaul
Historical weapon item pack	Item	Historical, Weapons	Pack	Multiplayer, Vanilla Friendly	Verify balance before applying Vanilla Friendly
Arena PvP map	Map	Arena	—	Multiplayer	Vanilla Friendly is appropriate if base loot tables are unchanged
Localization translation pack	Localization	—	—	Vanilla Friendly	Localization packs rarely require Tier 2; omit if no match

---

Part 11 — Tag Inventory Management

The tag inventory is the master record of every tag applied to every 57 Studios™ Workshop listing. It is maintained as a structured document (spreadsheet or database table) with the following fields:

Field	Type	Description
listing_id	String	Steam Workshop entry ID
listing_title	String	Human-readable listing title
tier_1_tag	String	Applied Tier 1 tag
tier_2_tags	String[]	Applied Tier 2 tags (1–3)
tier_3_tags	String[]	Applied Tier 3 tags (0–2)
tier_4_tags	String[]	Applied Tier 4 tags (0–2)
total_tag_count	Integer	Sum of all applied tags
last_reviewed_date	Date	ISO 8601 date of last review
reviewer_name	String	Name of reviewer
next_review_date	Date	Scheduled Annual Review date
deprecation_flags	String[]	Any DEPRECATED-TAG-PENDING flags
notes	String	Freeform governance notes

Governance Principle GP-008: The tag inventory is updated within 48 hours of any tag change on any listing. An inventory that lags the live Workshop data is an unreliable governance tool.

---

Frequently Asked Questions

Q: Can I use a tag that is popular on other Workshop listings but is not on the official Unturned™ tag list?

A: No. The 57 Studios™ framework treats the official Unturned™ tag list as a closed vocabulary. Tags not on the official list cannot be applied through the standard interface, and API-applied unofficial tags do not match player filter behavior. The correct action is to identify the closest official tag and document the gap in the tag inventory backlog for monitoring.

Q: What happens if I apply the Curated tag to a listing that has not been officially curated by Smartly Dressed Games?

A: The tag constitutes a misrepresentation of the listing's curation status. It may attract initial subscriber interest that converts to negative reviews when subscribers discover the listing is not officially curated. It also risks a Workshop content policy violation. Remove it immediately and do not reapply.

Q: How do I decide between Pack and Bundle for a multi-asset listing?

A: Pack is used for any collection of 5 or more assets of the same type under one Workshop entry. Bundle is used for thematically grouped assets that are conceptually sold or distributed together, regardless of count. A two-vehicle pack with strong thematic cohesion (e.g., a matched set of police vehicles) may use Bundle. A twenty-vehicle pack with varied themes uses Pack. When in doubt, Pack is the safer selection.

Q: My mod has been stable for two months but I forgot to remove the Beta tag. Is there a penalty?

A: There is no Workshop-imposed penalty for a stale Beta tag, but there is a discovery cost. Players filtering for non-beta stable content may exclude Beta-tagged listings. The corrective action is straightforward: remove the tag through the Workshop management interface and update the tag inventory with the removal date and the reason.

Q: Can a map listing have both Arena and Survival as Tier 2 tags?

A: Yes. A map that features a structured arena combat zone and also includes survival mechanics outside the arena — for example, a map where players must survive to reach the arena — can legitimately carry both. Apply the Decision Matrix to confirm both tags meet the content coverage threshold (≥30% of the map's design investment each). If the arena section is a minor feature, Survival is the correct sole Tier 2 tag.

Q: How do I handle a listing where the mod's content changed significantly after an update?

A: A significant content update (>30% new or changed assets) triggers an out-of-cycle tag review for the affected listing only. Re-run the Decision Matrix with the updated content as input. If the output tag set differs from the applied tag set, update the listing and document the change in the tag inventory.

Q: We publish content in collaboration with Horizon Life RP. Which governance framework applies?

A: The 57 Studios™ Tag Taxonomy and Governance Framework applies to the 57 Studios™-owned Workshop listing for that content. Horizon Life RP applies its own governance to any separately owned listings. Tag harmonization between the two organizations' listings is encouraged but governed by the external collaborator alignment principle (Principle H-004) rather than by a mandatory compliance requirement.

Q: Can I apply Vanilla Friendly and Multiplayer to the same listing?

A: Yes. These Tier 4 tags are not in conflict. Vanilla Friendly describes balance impact (no disruption to base-game balance); Multiplayer describes verified deployment context. A vehicle mod that adds a new vehicle without altering weapon values or drop rates, and has been tested on a multiplayer server, is accurately described by both tags.

Q: How often does the official Unturned™ tag list change?

A: Smartly Dressed Games does not publish a fixed cadence for tag list updates. Changes typically accompany significant game updates. The Annual Tag Review Process is designed to catch any changes that occurred since the previous review. Portfolio managers monitoring the Unturned™ development update communications can identify changes proactively and trigger a targeted deprecation review without waiting for the annual cycle.

Q: Is there a minimum tag count enforced by the Steam Workshop?

A: The Steam Workshop does not enforce a minimum tag count at the platform level. The 57 Studios™ policy minimum of 3 tags is an internal governance standard based on discovery performance analysis, not a Valve requirement. However, listings with zero tags are excluded from category filter results entirely; the practical minimum for any discovery-oriented listing is 1.

Q: What is the difference between Server Side and Workshop Dependency at Tier 4?

A: Server Side describes how the mod is deployed — it installs on the server rather than on individual clients. Workshop Dependency describes a dependency relationship — the mod cannot function without another Workshop entry being present. These are independent attributes. A server-side mod with a dependency carries both tags. A server-side mod with no dependencies carries only Server Side.

Q: Can our team apply tags differently depending on who submitted the listing?

A: No. Tag governance is a portfolio-level function, not a per-contributor function. All contributors apply tags using the same Decision Matrix and the same tag inventory. Cross-listing inconsistencies produced by contributor variance are a Type C conflict and are resolved through the harmonization process.

---

Part 12 — Tag Governance Metrics and Reporting

Sound tag governance produces measurable outcomes. The following metrics are tracked at the portfolio level as part of the Annual Tag Review Report and during any triggered interim review. Tracking these metrics over time creates a longitudinal record of governance health that informs resourcing decisions (how much reviewer time is allocated to tag maintenance) and prioritization (which listings are at greatest risk of tag decay).

12.1 Portfolio Health Metrics

Metric	Definition	Target Threshold
Tag compliance rate	Percentage of listings with a tag set that passes a full Decision Matrix evaluation without correction	≥95%
Conflict rate	Percentage of listings with at least one identified tag conflict at review time	≤5%
Stale tag rate	Percentage of listings carrying at least one tag that has been deprecated or that violates the Beta recency rule	≤2%
Under-tagging rate	Percentage of listings with fewer than 3 tags	0% (zero tolerance)
Over-tagging rate	Percentage of listings exceeding 8 tags	≤3%
Inventory lag	Maximum number of days between a live tag change and the corresponding inventory update	≤48 hours

Governance Principle GP-009: If the tag compliance rate falls below 90% at any review cycle, the Annual Tag Review Process is supplemented with a quarterly spot-check program until the rate recovers to ≥95% for two consecutive annual reviews.

12.2 Review Cycle Reporting

Each Annual Tag Review Report includes a year-over-year comparison table for every metric above. This comparison is the primary mechanism for detecting governance drift — a gradual degradation in tag quality that is not visible in any single listing but emerges as a portfolio-level trend across multiple review cycles.

Metric	Prior Year	Current Year	Delta	Action Required
Tag compliance rate	—	—	—	—
Conflict rate	—	—	—	—
Stale tag rate	—	—	—	—
Under-tagging rate	—	—	—	—
Over-tagging rate	—	—	—	—
Inventory lag (max days)	—	—	—	—

The Delta column is the arithmetic difference between current and prior year. For rates where lower is better (conflict rate, stale rate, over/under-tagging rate), a positive delta indicates degradation. For rates where higher is better (compliance rate), a negative delta indicates degradation. Any degrading delta beyond the measurement noise threshold (±2 percentage points) triggers a root cause analysis before the next review cycle.

12.3 Governance Ownership

Tag governance at 57 Studios™ is owned by the publishing team lead. The following responsibility assignments apply:

Responsibility	Owner	Frequency
Tag inventory updates	Contributing modder (within 48 hours of any change)	Per-event
Decision Matrix completion	Contributing modder	Per-listing at publication and annual review
Conflict check execution	Publishing team lead	Per-listing at publication; portfolio-wide at annual review
Annual Review Report generation	Publishing team lead	Annual
Tag deprecation response	Publishing team lead	Within 14 days of confirmed deprecation
Harmonization audit	Publishing team lead	Annual (sub-step of Annual Review)
External reference verification	Any team member	Annual (sub-step of Annual Review)

---

Appendix A — Tag Decision Matrix Worksheet Template

The following is the standard worksheet format used by 57 Studios™ contributors when completing a Decision Matrix evaluation. One worksheet is completed per listing before initial publication and at each Annual Review cycle.

TAG DECISION MATRIX WORKSHEET
==============================
Date:
Reviewer:
Listing Workshop ID (if existing):
Listing Title:

INPUTS
------
Mod summary statement:
Asset type list:
  - 
  - 
Target player profile:
Interaction with base game:

TIER 1 RESOLUTION
-----------------
Asset type → Tag mapping:
Tie-break applied (Y/N):
Tie-break reasoning (if Y):
Selected Tier 1 Tag:

TIER 2 CANDIDATE LIST
----------------------
Candidate 1: [tag] | Intent: [1-3] | Coverage: [1-3] | Total: [sum]
Candidate 2: [tag] | Intent: [1-3] | Coverage: [1-3] | Total: [sum]
Candidate 3: [tag] | Intent: [1-3] | Coverage: [1-3] | Total: [sum]
Candidate 4: [tag] | Intent: [1-3] | Coverage: [1-3] | Total: [sum]
Top 3 selected:

TIER 3 EVALUATION
-----------------
Pack (5+ assets): Y / N
Overhaul (replaces base content): Y / N
Beta (active breaking iteration): Y / N
Selected Tier 3 tags (if any):

TIER 4 EVALUATION
-----------------
Vanilla Friendly (testing confirmed): Y / N
Multiplayer (testing confirmed): Y / N
Workshop Dependency (confirmed dependency): Y / N
Server Side (server-only deployment): Y / N
Client Side (client-only): Y / N
Standalone (no dependencies confirmed): Y / N
Optimized (low-settings test passed): Y / N
High Poly (high-detail intentional): Y / N
Low Poly (low-detail intentional): Y / N
Selected Tier 4 tags (if any):

CONFLICT CHECK
--------------
Logical contradictions (Type A): None / [list]
Hierarchical redundancy (Type B): None / [list]
Cross-listing inconsistency (Type C): None / [list]
Scope mismatch (Type D): None / [list]
Resolution applied (if any):

FINAL TAG SET
-------------
Tier 1: [tag]
Tier 2: [tag], [tag], [tag]
Tier 3: [tag]
Tier 4: [tag], [tag]
Total count: [n]
Compliant with 3–8 policy range: Y / N

INVENTORY UPDATE
----------------
Inventory updated: Y / N
Next review date:

---

Appendix B — Tag Governance Glossary

Term	Definition
Annual Tag Review Process	The scheduled governance event conducted once per calendar year across all active 57 Studios™ Workshop listings to audit, correct, and document tag sets.
Closed vocabulary	A tag set whose members are defined by an external authority (Smartly Dressed Games via the Workshop configuration) and cannot be extended by the listing owner.
Content coverage threshold	The 30% rule: a tag must describe at least 30% of the mod's content to meet the minimum relevance standard.
Dead label	A deprecated tag that remains stored on a listing but no longer matches any active player filter.
Decision Matrix	The six-step structured evaluation tool that converts a mod description into a compliant tag set.
Deprecation	The retirement of a tag from the official Workshop vocabulary, either by removal or renaming.
Governance Principle	A top-level rule in the 57 Studios™ Tag Taxonomy and Governance Framework, identified by the prefix GP-.
Harmonization	The process of aligning tag sets across multiple listings in the 57 Studios™ portfolio to produce a consistent discovery surface.
Over-tagging	The application of tags beyond the mod's content scope, producing relevance signal dilution.
Search intent alignment	The degree to which a tag matches the actual search terms and filter behaviors of the mod's target player audience.
Tag inventory	The master record of every tag applied to every 57 Studios™ Workshop listing, maintained as a structured document.
Tag conflict	A condition in which two or more tags in a listing's tag set contradict, overlap redundantly, or misrepresent the mod's content.
Tag-keyword stuffing	The selection of tags based on popularity rather than content accuracy, in violation of Governance Principle GP-005.
Tier	A level in the 57 Studios™ tag hierarchy (Tier 1 through Tier 4), each describing a different dimension of the mod's content and attributes.
Under-tagging	The application of fewer tags than necessary to accurately represent the mod's content and audience, resulting in insufficient discovery signal.

---

Appendix C — External References

The 57 Studios™ Tag Taxonomy and Governance Framework references the following external sources as authoritative inputs. Internal documentation is secondary to these live sources. All external references were verified as of the date of this article's publication.

Source	URL	Used For
Steam Workshop Developer Documentation	https://partner.steamgames.com/doc/features/workshop	Authoritative tag mechanics, Workshop publishing pipeline specifications
Unturned™ on Steam	https://store.steampowered.com/app/304930/Unturned/	Live tag list verification, Workshop browse behavior reference

Note on link maintenance: Both URLs are subject to change at Valve's or Smartly Dressed Games' discretion. The Annual Tag Review Process includes a link verification step. If either URL becomes invalid, the tag inventory must be flagged as requiring source re-verification before the next Decision Matrix evaluation is conducted.