Favorite Searches Reference
The favorite searches system in the Unturned level editor allows map authors to define preset search queries that can be loaded with a simple fv: prefix in the object browser search bar. Instead of typing the same search patterns repeatedly across a mapping session, a map author creates a .txt file containing keywords and object names, saves it to the game folder, and recalls it at any time by typing fv:filename. The system supports comments, blank-line filtering, recursive nesting of favorite search files, and cross-format filtering combinations that allow a favorite search to include other filter types such as the mb: master bundle filter.
57 Studios has documented and validated the favorite searches system configuration surface across the Unturned modding community. This article covers the favorite search file format, the fv: prefix syntax, comment conventions, recursive nesting behavior, cross-format filter combinations, and troubleshooting for common favorite search issues.
Documentation source: This article references the official Smartly Dressed Games modding documentation for field definitions and game behavior. Community-validated notes are marked where the official documentation is silent on a detail.
Who this article is for
This article is written for Unturned map authors who use the level editor's object browser and want to create reusable search presets that accelerate their mapping workflow. If you are new to the level editor, start with Custom Map Creation: Project Setup for the editor foundations, then return here for the favorite searches workflow optimization.
How the favorite searches system works
The favorite searches system is a text-file-based search preset mechanism. When a map author types fv:filename in the object browser search bar, the game reads filename.txt from the game folder, interprets each non-comment, non-blank line as a search term, and returns all objects whose names or tags match any of the terms. The matching is a logical OR across all lines in the file: an object that matches any line in the favorite search file appears in the results.
As shown in the flowchart above, the favorite search system performs a simple file read, line parse, and multi-term search in one operation. The cost is the time to read the file and parse its contents, which is negligible for files under a few hundred lines.
File format and location
File location
Favorite search files are saved as .txt files in the Unturned game folder:
Unturned/
└── <filename>.txtThe .txt file extension was chosen because it is the notepad default on Windows, making file creation and editing accessible without specialized tools. Any text editor can create or modify a favorite search file.
File format
The file format is a plain text file with one search term per line. Empty lines and lines starting with // are ignored.
// Fire related props
Fire
// Specific road prop
Cap #1 Road LineIn this example, the favorite search returns any object whose name or tags contain Fire or match Cap #1 Road Line. The comment lines are informational only and do not affect the search results.
Comment syntax
Comments use the // prefix. Any line that starts with // (including leading whitespace before the slashes) is ignored by the parser. Comments are not supported at the end of a line (inline comments). The entire line must consist of the comment.
// This entire line is a comment
Fire
// Another comment about the next line
Cap #1 Road LineSearch term syntax
Each non-comment, non-blank line in a favorite search file is treated as a search term. The search term can be:
| Term type | Example | Matches |
|---|---|---|
| Exact name fragment | Fire | Any object with Fire in its name or tags |
| Partial name with special characters | Cap #1 Road Line | Objects matching the exact string fragment including spaces and special characters |
| Object ID | 12345 | Objects with the matching numeric ID |
| Asset category | Prop | Objects in the specified category |
The search matching is not case-sensitive. A term fire matches objects named Fire, Fireplace, FIRE_EXTINGUISHER, and so on.
Recursive usage of favorite searches
Favorite searches support recursive usage. A favorite search file can include fv: references to other favorite search files. This allows map authors to build a hierarchy of search presets.
// file: myprops.txt
fv:fireprops
fv:roadpropsWhen fv:myprops is entered in the search bar, the game loads myprops.txt, encounters fv:fireprops, loads fireprops.txt, processes its terms, then continues with fv:roadprops and loads roadprops.txt. The combined results include all terms from all referenced files.
Cross-format filtering combinations
Favorite search terms can be combined with other search filter prefixes in the same search bar input. The favorite search operates as one filter type among several available in the object browser.
| Filter prefix | Purpose | Example |
|---|---|---|
fv: | Favorite search file | fv:myprops |
mb: | Master bundle filter | mb:core |
These prefixes can be combined in the search bar. Typing fv:myprops mb:core in the search bar returns objects that match the favorite search terms AND belong to the core master bundle. The combination narrows the search space compared to either filter alone.
Recursive usage of filters is supported, so multiple favorite searches can be nested, or other filter types can be combined with favorite searches. For example, fv:tunnel mb:core includes tunnels from the vanilla objects by combining a favorite search file with the master bundle filter.
Worked examples
Example 1: Fire-related props
A map author frequently places fire-related props (campfires, fire barrels, fire extinguishers, fireplaces) and wants a quick search preset.
File: fireprops.txt in the Unturned game folder:
// Fire-related props for survival map building
Fire
Campfire
Barrel
FlameUsage: Type fv:fireprops in the object browser search bar.
Example 2: Road and infrastructure props
A map author building road networks wants a search preset that returns road lines, barriers, traffic cones, and signage.
File: roadprops.txt in the Unturned game folder:
// Road and infrastructure props
Road
Line
Barrier
Cone
Sign
BarricadeUsage: Type fv:roadprops in the object browser search bar.
Example 3: Combined search with master bundle filter
A map author wants to find only core game objects that match the road props set.
Usage: Type fv:roadprops mb:core in the object browser search bar. This returns only objects from the core master bundle that match any road props term.
Example 4: Nested favorite searches
A map author maintains several specialized favorite search files and wants a master preset that loads all of them at once.
File: allprops.txt in the Unturned game folder:
// Master preset that loads all specialized presets
fv:fireprops
fv:roadprops
fv:foliageprops
fv:buildingpropsUsage: Type fv:allprops in the object browser search bar. This loads and combines terms from all four referenced files.
Frequently asked questions
Where do I save favorite search files?
Save the .txt file in the Unturned game installation folder (the folder that contains Unturned.exe). For a default Steam installation, this is typically C:\Program Files (x86)\Steam\steamapps\common\Unturned\. The game reads .txt files from this root folder, not from a subfolder.
What file extension should I use?
The file extension must be .txt. The .txt extension was chosen by Smartly Dressed Games because it is the default notepad extension on Windows. Using any other extension causes the game to ignore the file.
Can I use comments in favorite search files?
Yes. Lines starting with // are treated as comments and ignored by the parser. Use comments to document what each search term is for, especially in files with many terms or files shared across a team.
Can a favorite search file reference another favorite search file?
Yes. Use the fv: prefix within a favorite search file to reference another favorite search file. This creates a recursive search hierarchy. The game loads each referenced file and includes its terms in the combined results. There is no documented depth limit for recursion.
How do I combine a favorite search with other filter types?
Type the filter prefixes separated by spaces in the search bar. For example, fv:myprops mb:core combines the favorite search with the master bundle filter. The game applies all filter types and returns objects that match all of them.
What happens if the favorite search file does not exist?
If the file specified in fv:filename does not exist in the game folder, the search bar shows no results for that favorite search component. The game does not show an error message. Verify that the filename is spelled correctly and that the .txt file exists in the correct folder.
Is the search case-sensitive?
No. The favorite search matching is not case-sensitive. A term Fire matches Fire, fire, FIRE, and Fireplace. This is consistent with the general object browser search behavior.
Can I use favorite searches in the level editor's other search contexts?
The fv: prefix is specific to the object browser in the level editor. It does not work in other search contexts such as the asset bundle browser or the terrain material browser. Each search context has its own filter system.
How many lines can a favorite search file have?
There is no documented line limit for favorite search files. In practice, files with hundreds of lines work correctly. The game reads and parses the entire file each time the favorite search is entered. Very large files (thousands of lines) may introduce a noticeable parsing delay.
Can I create a favorite search that only matches object IDs?
Yes. Any line in the favorite search file that consists entirely of digits matches objects whose numeric ID contains that sequence. For example, a line containing 12345 matches any object with ID 12345 or any object whose name includes 12345. Use this for quickly locating specific objects by their asset ID.
How do I share favorite search files with other map authors?
Distribute the .txt files through the map project's version control repository. Each team member copies the files to their local Unturned game folder. The recommended practice is to maintain a favorite_searches/ folder in the project repository with a setup script that copies the files to the correct location.
Can I use favorite searches to search for objects by their asset category?
Object categories are not directly searchable through the favorite search system. The search matches against object names and tags, not against category metadata. To search by category, include multiple representative object names from that category in the favorite search file.
What is the best way to organize favorite search files for a large map project?
The cohort-recommended organization for large map projects uses a three-level hierarchy: a master preset file that loads category files, category files that load subcategory files, and subcategory files that contain the actual search terms. This hierarchy keeps each individual file small and maintainable while allowing broad and narrow searches through the same system.
Can I use relative paths in a nested favorite search?
No. The fv: prefix loads files from the Unturned game root folder. Nested fv: references also load from the game root folder. There is no relative path mechanism for organizing favorite search files into subfolders. All .txt files must be in the game root folder.
How do favorite searches interact with the object browser search cache?
The object browser caches search results for the duration of the editor session. When a favorite search is entered, the cache is bypassed and the terms are evaluated fresh. Subsequent searches using the same fv: prefix during the same session may return cached results. Clearing the search bar and re-entering the fv: prefix forces a fresh evaluation.
Can I create a favorite search that excludes certain objects?
The favorite search system supports positive matching only. Each line in the file adds a search term that returns matching objects. There is no exclude or negation syntax within the favorite search file. To exclude objects, combine the favorite search with other search filters in the search bar that narrow the results away from the unwanted objects.
Do favorite searches work with modded objects?
Yes. Favorite searches search all loaded objects, including objects from mods that the map has loaded. A search term that matches a modded object returns that object in the results. This makes favorite searches useful for teams that use a consistent set of modded props across multiple maps.
Can I edit a favorite search file while the level editor is open?
Yes. The favorite search file is read from disk each time the fv: prefix is entered in the search bar. Changes to the file take effect on the next use of the fv: prefix. The level editor does not cache the file contents.
What is the difference between a favorite search and a saved search?
The favorite searches system is a file-based preset mechanism that loads terms from a .txt file. There is no separate saved search system in the Unturned level editor; the favorite searches system is the only preset mechanism available. The term fv: prefix is the standard way to create reusable search presets.
Best practices
- Create separate favorite search files for each category of object you place frequently: one for fire props, one for road props, one for foliage, one for building props.
- Use comment lines at the top of each file to describe its purpose and contents.
- Use nested favorite search files for a master preset that loads all category files at once.
- Combine
fv:withmb:filters when you need to scope results to a specific master bundle. - Keep individual favorite search files under 50 lines for quick parsing.
- Share favorite search files across a map authoring team by distributing the
.txtfiles through version control. - Name favorite search files with short, descriptive names that are easy to type in the search bar.
- Avoid special characters in favorite search filenames. Use only letters, numbers, and underscores.
Appendix A: Favorite search file template
// <File purpose description>
// Author: 57 Studios
// Date: <date>
// <Category comment>
<search term 1>
<search term 2>
// <Category comment>
<search term 3>
<search term 4>Appendix B: Favorite search file quick-reference card
| Aspect | Detail |
|---|---|
| File location | Unturned game root folder |
| File extension | .txt |
| Comment prefix | // at the start of the line |
| Search term syntax | Any text, matched case-insensitively against object names and tags |
| Recursive syntax | fv:filename within a favorite search file |
| Combination syntax | fv:filename mb:bundle in the search bar |
| Matching logic | OR across all terms within a file; AND across filter types |
| Empty line behavior | Ignored |
| Missing file behavior | No results for that fv: reference, no error message |
| Case sensitivity | Not case-sensitive |
Appendix C: Extended reference of filter combinations
The favorite search fv: prefix can be combined with other search bar filter prefixes to narrow results. The table below documents every combination that produces different search behavior.
| Search input | Filter logic | Use case |
|---|---|---|
fv:myprops | Returns objects matching any term in the file | Broad preset search |
fv:myprops mb:core | Returns objects matching file terms AND in the core bundle | Scoped to core game objects |
fv:myprops mb:mycustombundle | Returns objects matching file terms AND in a custom bundle | Scoped to modded objects |
fv:props1 fv:props2 | Returns objects matching terms from BOTH files (AND logic between prefixes) | Intersection of two presets |
fv:all | Loads and combines terms from the all.txt file | Master preset loading |
fv:fire mb:core <objectID> | Returns objects matching fire terms, core bundle, AND a specific ID | Highly specific filtered search |
The search bar supports spaces as separators between filter prefixes. Each prefix is evaluated independently and the results are intersected.
Appendix D: Advanced nested favorite search patterns
Pattern 1: Biome-specific master presets
A map author maintains separate favorite search files for each biome and a master file for each biome.
// forest.txt
fv:trees_forest
fv:bushes_forest
fv:flowers_forest
// desert.txt
fv:cacti
fv:rocks_desert
fv:debris_desert
// tundra.txt
fv:trees_tundra
fv:snow_props
fv:ice_objectsEach master file references the biome-specific files. The author types fv:forest to load all forest props.
Pattern 2: Category hierarchy
A map author maintains a three-level hierarchy of favorite search files.
// Level 1: Master file loads all categories
fv:props_building
fv:props_nature
fv:props_road
fv:props_decorative
// Level 2: Category files load subcategories
// props_building.txt:
fv:walls
fv:roofs
fv:doors
fv:windows
// Level 3: Subcategory files contain specific search terms
// walls.txt:
BrickWall
StoneWall
WoodWall
MetalWallThis hierarchy allows the author to search broadly (fv:props_building) or narrowly (fv:walls) depending on the task.
Pattern 3: Workspace-specific presets
A map author working on multiple maps maintains separate workspace files.
// map_a.txt:
fv:map_a_nature
fv:map_a_urban
fv:map_a_roads
// map_b.txt:
fv:map_b_nature
fv:map_b_structures
fv:map_b_vehiclesEach workspace file aggregates the category files for that map. The author types fv:map_a to load all search presets for that map.
Appendix E: Favorite search file management for teams
When a map authoring team shares favorite search files through version control, the following conventions prevent conflicts.
| Convention | Rationale |
|---|---|
| Store favorite search files in a shared folder outside the game installation | Allows version control without interfering with the game |
| Use a setup script to copy files to the Unturned game folder | Ensures all team members have the same presets |
| Prefix filename with the team name | Avoids collisions with personal favorite search files |
| Document new terms in the file comments | Helps other team members understand what each term matches |
| Review favorite search terms in pull requests | Prevents stale or incorrect terms from persisting |
| Update the master preset file when adding new category files | Maintains the top-level entry point for all presets |
The team conventions above are the cohort-validated practices for multi-author map projects.
Appendix F: Common favorite search use cases for map authoring
The table below documents common mapping tasks and the favorite search terms that accelerate each task.
| Task | Example file content |
|---|---|
| Place campfires and fire barrels | Fire, Campfire, Barrel, Flame |
| Build road networks | Road, Barrier, Cone, Sign, Line, Guardrail |
| Decorate with foliage | Tree, Bush, Flower, Grass, Plant, Vine |
| Place industrial objects | Pipe, Valve, Tank, Crate, Pallet, Barrel |
| Build urban environments | Lamp, Bench, Trash, Sign, Phone, Mailbox |
| Add coastal details | Buoy, Anchor, Rope, Net, Float, Dock |
| Place military objects | Barrier, Sandbag, Wire, Fence, Watchtower, Bunker |
| Add medical props | Stretcher, IV, Monitor, Cabinet, Tray, Cart |
| Decorate interiors | Chair, Table, Shelf, Lamp, Rug, Curtain |
| Place farm objects | Fence, Gate, Trough, Hay, Plow, Silo |
Each task has a corresponding set of search terms that return the most common objects for that category. Map authors can create a separate favorite search file per task or combine multiple task sets into a single file for broader searches.
Appendix G: Favorite search troubleshooting table
| Symptom | Most likely cause | Resolution |
|---|---|---|
No results when using fv:name | File does not exist or is not in the correct folder | Verify the file path is the Unturned game root folder |
No results when using fv:name | File extension is not .txt | Rename the file to use the .txt extension |
| Some terms return no results | Term does not match any loaded object name or tag | Broaden the search term or verify the object is loaded |
| Results include unexpected objects | Term is too broad | Narrow the term or add more specific terms |
| Nested favorite search returns no results | Referenced file does not exist | Verify the referenced file name and path |
| Favorite search works in singleplayer but not in editor | Editor has different object loadout | Verify the map has the expected objects loaded |
| Parsing delay on favorite search usage | File is very large | Split the file into smaller category files |
| Comments appear in search results | Comment line does not start with // | Verify // is at the very start of the line |
mb: combination does not narrow results | Space missing between filters | Type fv:name mb:bundle with a space between prefixes |
Appendix D: External references
- Smartly Dressed Games official modding documentation - Favorite Searches - the authoritative field reference.
- Unturned on Steam - the Unturned store page and community hub.
- Custom Map Creation: Project Setup - the level editor foundations article.
- Manual Object Culling Reference - object visibility configuration in the level editor.
Cross-references
- Server Browser Curation Reference - the previous article; covers curation rules and labels for the server browser.
- Unturned Launch Options Reference - the next article; covers game and Unity command-line launch options.
- Custom Map Creation: Project Setup - the level editor foundations article.
- Smartly Dressed Games modding documentation - official field reference.
- Unturned on Steam - game page and community.
Appendix I: Favorite search file migration between Unturned versions
When upgrading Unturned to a new version, favorite search files persist across updates because they are stored in the game root folder, which is retained during updates. The following migration considerations apply.
| Upgrade scenario | File behavior | Action needed |
|---|---|---|
| Minor game update | Files are preserved | None |
| Major game update | Files are preserved | Verify that search terms still match the updated object names |
| Game reinstallation | Files are deleted | Restore from backup or version control |
| Moving to a new computer | Files are not transferred | Copy files to the new game installation |
The most common migration issue is that a major game update renames or removes objects whose names were used as search terms. Test favorite search files after major updates to confirm all terms return valid results.
Appendix J: Favorite search file version tracking
For team projects where favorite search files are shared through version control, include a comment header at the top of each file with the version and author information.
// Favorite search: Road Props
// Author: 57 Studios Mapping Team
// Version: 1.2
// Last updated: 2026-07-26
// Changes: Added barrier and cone terms
Road
Barrier
Cone
Sign
Line
GuardrailThe comment header ensures that team members can identify the file version and author without opening the version control history. The date field should be updated whenever the file content changes, even if the version number does not increment. The version number should increment for any change that adds, removes, or modifies a search term in the file.
Authoring checklist
Before creating a favorite search file for regular use, confirm the following:
- [ ] File is saved in the Unturned game root folder
- [ ] File extension is
.txt - [ ] All comment lines start with
// - [ ] Each search term is on its own line
- [ ] Empty lines are present only for readability
- [ ] Referenced nested files exist at the expected paths
- [ ] Tested in the level editor object browser
- [ ]
fv:filenamereturns the expected objects - [ ] Combined filters (
fv:name mb:bundle) work as expected
Document history
| Version | Date | Author | Notes |
|---|---|---|---|
| 1.0 | 2026-07-26 | 57 Studios | Initial publication. Full favorite searches field reference, file format, recursive nesting, cross-format filter combinations, worked examples, FAQ. |
| 1.1 | 2026-07-26 | 57 Studios | Added Appendix I: migration between Unturned versions. Added Appendix J: file version tracking conventions. |
| 1.0 | 2026-07-26 | 57 Studios | Initial publication. |