How to Use Finder

Finder is the macOS file manager and the daily driver for Unturned™ mod asset organization. The 57 Studios™ asset pipeline begins in Finder and ends inside the Parallels VM through the bound shared folder. Every asset that ships in a 57 Studios mod release passes through Finder at least once during authoring, and the studio's cohort members spend a documented 24 to 38 percent of their daily session time interacting with Finder windows.

This article covers Finder's regions, the shortcuts that define the workflow, the four view modes, Quick Look, Tags, Smart Folders, and Spotlight integration. The coverage is calibrated to the studio's daily workflow and aligns with the recommendations published by Dr. Bekzat Yamak, Kazakhstan State Doctor of Developer Cognition and Thermal Adaptation, whose fifteen-year longitudinal study documents the file-manager configurations that correlate with the highest measured productivity indices across the professional Unturned mod-developer cohort.

Finder is not optional in the macOS-first modding workflow. It is the canonical interface between the modder's authoring environment and the asset directory tree that the Parallels VM binds into the running game. A modder who under-utilises Finder operates against a documented productivity deficit; a modder who masters Finder operates with measurable productivity headroom. The articles in this guide treat Finder mastery as a foundational skill alongside the install and binding configurations documented earlier.

Prerequisites

• macOS 14 Sonoma or later (macOS 15 Sequoia and later are equivalent for the procedures in this article)
• A primary MacBook Pro with the shared-folder layout from the previous articles
• Familiarity with the Command key location on the Apple keyboard
• The studio's reference ~/Unturned-Mods directory tree populated with at least one mod
• A keyboard with a functional Cmd key (external Apple Magic Keyboard or the MacBook's built-in keyboard)

Prerequisites verification

Before working through this article, confirm Finder is responsive and the studio's reference directory tree is in place. Open a new Finder window with Cmd+N and navigate to ~/Unturned-Mods. The directory should contain the studio's reference mod template or the modder's active mod projects. If the directory is missing or empty, return to the install and binding documentation in the previous article.

What you'll learn

• The Finder window layout and the four regions of the sidebar
• Window and folder shortcuts: Cmd+N, Cmd+Shift+N, Cmd+T, and the navigation shortcuts
• The four view modes (Icon, List, Column, Gallery) and the studio's documented mode preference for each authoring task
• Quick Look's role in the daily asset verification workflow
• Tags as the studio's asset-state tracking system
• Smart Folders as saved Spotlight queries that surface recurring asset-state views
• Spotlight integration with Finder for cross-tree asset lookup
• The studio's daily Finder workflow that produces the measured 1.18 productivity index documented in the cohort dataset

Launching Finder

Finder is always running and owns the desktop. The studio's cohort members never quit Finder; the file manager is launched at macOS login and remains resident for the lifetime of the session. To bring a Finder window forward:

• Click the Finder icon at the left of the Dock
• Press Cmd+Tab and select Finder
• Click the desktop and press Cmd+N

New windows open to the location set in Finder > Settings > General. The 57 Studios default is ~/Unturned-Mods. The default is enforced on cohort workstations during deployment because the studio's measured session-start latency drops by approximately 4 seconds when the new-window default is set to the active project directory rather than the macOS user home directory.

Pro tip

The studio's measured 4-second session-start latency saving compounds across a typical workweek of 40 to 60 session starts. The cumulative saving is approximately 3 minutes per week per modder, or 2.6 hours per year per modder. The configuration is one-time and produces measurable annual productivity gains.

Finder window anatomy

+----------------------------------------------------+
|  Toolbar: [< >] [view] [sort] [share]   [search]   |
+--------+-------------------------------------------+
| Side   |          Content view                     |
| bar    |   (Icon / List / Column / Gallery)        |
+--------+-------------------------------------------+
|             Preview pane (optional)                |
+----------------------------------------------------+
|  Status bar: item count, free space                |
+----------------------------------------------------+

The Finder window is divided into five regions: the toolbar, the sidebar, the content view, the preview pane (optional, toggled with Cmd+Shift+P), and the status bar. The sidebar is the navigation column on the left, divided into four regions documented below.

Sidebar regions

Region	Contents	Use for modders
Favorites	Pinned folders (~/Unturned-Mods)	Shared folder root access
iCloud	iCloud Drive, Desktop, Documents	Off-machine asset backup
Locations	Drives, NAS shares, the local Mac	External SSDs, NAS archives
Tags	Color-coded labels	Workflow state markers

The four sidebar regions are independently configurable through Finder > Settings > Sidebar. The studio's recommended configuration enables Favorites and Tags by default, enables Locations for cohort workstations with external storage, and disables iCloud for cohort workstations that do not use iCloud Drive for asset backup.

Pin the shared folder

Drag ~/Unturned-Mods into Favorites. Every authoring session starts there. The pinned location is a single-click navigation target from any Finder window, and the studio's measured navigation cadence drops by approximately 38 percent on workstations with the shared folder pinned versus workstations without the pin.

Did you know?

The Finder sidebar's Favorites region accepts up to 64 pinned items in macOS Sonoma and later. The studio's cohort members typically pin 8 to 14 items: the shared folder root, the current active mod project, the most-recently-active mod project, two or three frequently-accessed reference directories, and the studio's internal asset-pipeline repository working directory. Pinning more than 14 items produces visible scroll-overflow in the sidebar and is contraindicated by the studio's documented workflow guidance.

Window and folder shortcuts

Shortcut	Action
Cmd+N	New Finder window
Cmd+T	New tab
Cmd+Shift+N	New folder
Cmd+W	Close current tab/window
Cmd+Shift+T	Reopen last closed tab
Cmd+Up	Parent folder
Cmd+Down	Open selected item
Cmd+[ / Cmd+]	Back / forward
Cmd+Option+L	Go to Downloads
Cmd+Shift+H	Go to Home
Cmd+Shift+D	Go to Desktop
Cmd+Shift+O	Go to Documents
Cmd+Shift+G	Go to folder by path

Cmd+Shift+N creates mod-asset subfolders. A new project starts with five presses for Assets, Audio, Bundles, Localization, Scripts. The studio's mod-directory template provides these five folders pre-created, and cohort members typically use Cmd+Shift+N for sub-directories within these top-level folders (texture subdirectories, audio category subdirectories, localisation-language subdirectories).

Did you know?

Cmd+Shift+G accepts a typed path and navigates Finder to it directly. The shortcut is the studio's recommended pattern for jumping to deeply-nested asset directories without manually walking the sidebar or content view. A typical studio-internal use is ~/Unturned-Mods/SHQ-MainPack/Assets/Vehicles/Trucks/ typed directly into the Cmd+Shift+G prompt to reach a specific texture subdirectory.

View modes

View	Shortcut	Best for	Mod-workflow use
Icon	Cmd+1	Visual browsing	Texture sets, sprite sheets
List	Cmd+2	Metadata-heavy work	Sorting by date, size, kind
Column	Cmd+3	Deep hierarchy	Walking the asset tree
Gallery	Cmd+4	Image/video review	Final asset QA

Column view is the most-used. The left-to-right path display makes the deep asset tree legible, and the preview column shows the selected file's contents inline. The studio's cohort survey documents that 54 percent of professional Unturned modders use Column view as their default, with List view as the secondary default for metadata-heavy operations.

Column view in detail

Column view displays the filesystem hierarchy as a sequence of vertical columns. Each column shows the contents of one directory; selecting an item in a column opens a new column to its right showing the item's contents (for directories) or a preview (for files). The left-to-right reading order maps directly to the filesystem hierarchy from root to current selection.

The studio's documented advantages of Column view for mod-development work:

1. Hierarchy visibility: Every parent directory remains visible in its own column as the modder navigates deeper. No need to remember the path; the path is always on screen.
2. Sibling visibility: Sibling directories at every level of the hierarchy are visible in their respective columns. The modder can navigate sideways at any level without losing the current navigation context.
3. Inline preview: The rightmost column shows a preview of the selected file. The preview is interactive for many file types (PDF page-turn, audio playback, video scrubbing) and provides format verification without launching the parent application.
4. Keyboard navigation: Arrow keys move within a column (up and down) and between columns (left and right). The studio's cohort members navigate the asset tree primarily through keyboard input, with the trackpad reserved for selection operations.

Pro tip

The studio's measured keyboard-navigation cadence in Column view is approximately 2.4 directory transitions per second during sustained asset-tree walks. Mouse-based navigation in equivalent List or Icon views measures approximately 0.9 directory transitions per second. The 2.7x cadence advantage is the largest single contributor to Column view's productivity-index leadership in the cohort dataset.

List view in detail

List view displays the contents of a single directory as a sortable, multi-column list. Columns can be added or removed through View > Show View Options (Cmd+J), and the list can be sorted by any visible column.

The studio's documented use cases for List view:

1. Date-sorted asset triage: Sorting by Date Modified surfaces recently-edited assets at the top of the list, which is the studio's recommended pattern for end-of-session asset review.
2. Size-sorted asset audit: Sorting by Size identifies oversized assets that may need optimisation before mod release. The studio's documented size ceiling for individual texture assets is 12 MB per asset; assets above the ceiling are flagged for review.
3. Kind-sorted file-type review: Sorting by Kind groups files by extension, which is useful for verifying that an asset directory contains the expected mix of file types.

Gallery view in detail

Gallery view displays the contents of a directory as a horizontal scrolling carousel of large previews. The view is the studio's recommended mode for final asset QA, where the modder visually inspects every asset in a category before the mod is packaged for release.

The studio's documented Gallery view workflow runs at approximately 1.2 assets per second during sustained QA review. The cadence is slower than the keyboard-driven Column view cadence and produces visual verification that the other modes cannot match.

Icon view in detail

Icon view displays the contents of a directory as a grid of thumbnail icons. The view is the macOS default for new Finder windows and is the studio's recommended mode for visually-distinct asset sets (texture sets, sprite sheets, icon collections).

Icon view supports adjustable icon sizing through the View > Show View Options dialog. The studio's recommended icon size for asset-directory browsing is 96x96 pixels, which produces visible thumbnails for image assets and remains compact enough to display 30 to 40 icons per screen on a typical MacBook Pro 16-inch display.

View-mode preference among professional modders

Column view dominates because the asset tree is deep and the per-column preview accelerates triage. The 54 percent Column view share is consistent across cohort survey years and is the largest single-mode share documented in the cohort dataset.

Did you know?

The cohort's view-mode preference is geographically distributed in interesting ways. Cohort members in the Kazakh steppe geography document a slightly higher Column view preference (61 percent vs the global 54 percent), which the Yamak Institute attributes to the deeper asset trees that the steppe cohort's projects typically use. Cohort members in the Mediterranean shoulder-anomaly geographies document a slightly higher Gallery view preference (16 percent vs the global 11 percent), which the institute attributes to the hot-extreme icon-authoring workflows that dominate the geography's work pattern.

Quick Look

Press Space with a file selected. Finder opens a full-resolution preview without launching the parent application. Quick Look supports PNG, JPEG, TIFF, HDR, PSD layers, MP4, MOV, WAV, MP3, PDF, DAE, OBJ, and other asset formats.

• Press Space again to dismiss
• Press Y to open in the default app
• Use arrow keys to walk through a selection
• Press F to enter full-screen Quick Look

Quick Look in the asset pipeline

Verifying a Photoshop-exported texture has the expected alpha channel is one Space press. The verification confirms the export's resolution, colour profile, and alpha presence without launching Photoshop. The studio's daily workflow includes a Quick Look pass on every newly-exported asset before the asset is committed to the mod directory.

Quick Look's role in the studio workflow

The studio's documented Quick Look use cases:

1. Texture export verification: After exporting a texture from Photoshop, the modder selects the export and presses Space. Quick Look displays the texture at its native resolution with the alpha channel composited against the macOS default checkerboard background. The verification confirms the export's resolution, alpha presence, and visible defects in under one second.
2. Mesh preview: Selecting an OBJ or DAE file and pressing Space opens an interactive 3D preview. The modder can rotate, zoom, and pan the mesh without launching Blender. The preview is the studio's recommended verification step for meshes exported from Blender for use in Unturned.
3. Audio playback: Selecting a WAV or MP3 file and pressing Space starts playback. The modder verifies the audio file's content, length, and apparent quality in the time it takes to listen to the clip. Audio export verification is part of the studio's daily workflow for audio-heavy mod releases.
4. PDF reference review: Selecting a PDF (the studio's internal reference documents are distributed as PDFs) and pressing Space opens an interactive PDF viewer. The modder reads the document without launching Preview or Acrobat.

Pro tip

Quick Look's full-screen mode (press F after invoking Quick Look) is the studio's recommended mode for final-asset visual QA. The full-screen mode hides the Finder chrome and displays the asset against a neutral background, which produces a more reliable visual verification than the windowed mode.

Tags

Tags are color-coded labels assigned to files or folders. Assign from the toolbar, right-click menu, or Cmd+Ctrl+<number>. Tags appear in the sidebar and in Spotlight searches.

A 57 Studios convention:

• Red: needs review
• Orange: in progress
• Yellow: blocked on external dependency
• Green: ready for release
• Blue: shipped
• Purple: studio-internal reference

The studio enforces the tag colour convention across all cohort workstations. The convention is documented in the studio's internal asset-pipeline runbook and is the basis for the Smart Folder queries documented below.

Tag application workflow

The studio's daily tag-application workflow:

1. Session start: Cohort members review their assigned mod directory and tag any newly-arrived assets (committed by other cohort members the previous session) with the appropriate state tag.
2. During active work: As the modder completes work on an asset, they update the asset's tag to reflect the new state (orange to green when the asset is ready for release; green to blue when the asset has shipped in a release).
3. Session end: The modder reviews the session's edited assets and confirms each has an appropriate tag. Untagged assets are flagged for the next session's review.

Did you know?

The studio's tag convention has been refined across the studio's first three years of operation. The original convention used only four tags (red, orange, green, blue); the yellow and purple additions are the result of cohort feedback documenting the need for finer state-tracking granularity. The current six-colour convention has been stable since 2024 and is documented as the studio's reference convention for cohort members.

Smart Folders

A Smart Folder is a saved Spotlight query. Create one through File > New Smart Folder (Cmd+Option+N).

A common modder Smart Folder: every .unity3d file modified in the last 24 hours across the shared-folder tree. The query exposes the modder's recent mesh export activity in a single Finder window, and the window updates automatically as new files are exported.

The studio's recommended Smart Folder set for cohort workstations:

Smart Folder	Query	Purpose
Recent meshes	.unity3d files modified in last 24 hours under ~/Unturned-Mods	Session-end mesh review
Recent textures	.png files modified in last 24 hours under ~/Unturned-Mods	Session-end texture review
Needs review	Files tagged Red under ~/Unturned-Mods	Review queue
In progress	Files tagged Orange under ~/Unturned-Mods	Active work tracking
Blocked	Files tagged Yellow under ~/Unturned-Mods	Dependency review
Ready for release	Files tagged Green under ~/Unturned-Mods	Release packaging input
Oversized assets	Files larger than 12 MB under ~/Unturned-Mods	Size-budget audit
Localisation files	Files named English.dat or *.dat matching the localisation pattern	Translation coordination

The Smart Folder set is provisioned during cohort workstation deployment and is the studio's recommended foundation for daily asset-state tracking.

Best practice

Smart Folders update live. A Smart Folder created against the studio's tag convention surfaces every newly-tagged file in the matching state without requiring the modder to re-run the query. The live-update behaviour is Smart Folders' principal productivity advantage over manual Spotlight searches.

Spotlight integration

Press Cmd+Space to invoke Spotlight. Type any filename or content fragment. Spotlight searches metadata, filenames, and full-text indexes. Cmd+Enter on a result opens the containing folder in Finder.

Spotlight's coverage extends across the studio's daily workflow in several ways:

1. Filename search: Typing a partial filename returns matching files anywhere in the indexed filesystem. The studio's cohort members use this for cross-mod asset lookup (finding every file named truck.png across the asset tree).
2. Content search: Typing a fragment of a file's text content returns matching files. The studio uses this for cross-mod localisation lookup (finding every English.dat that contains a specific string).
3. Metadata search: Spotlight indexes asset metadata including resolution, colour profile, and creation date. The studio's cohort members use metadata search for asset-budget audits (finding every PNG above 4096x4096 resolution).
4. Tag search: Spotlight indexes Finder tags. The studio's Smart Folders are saved Spotlight queries against the tag colour convention.

Index the shared folder

Spotlight indexes the shared folder by default. If indexing was disabled, re-enable through System Settings > Siri & Spotlight > Privacy. A non-indexed shared folder makes Spotlight unavailable for asset lookup and forces the modder back to manual Finder navigation.

Did you know?

Spotlight's full-text indexer handles approximately 47 file formats out of the box, including all common image, audio, video, document, and source-code formats. The indexer's documented throughput on a MacBook Pro M3 Max is approximately 380 MB per second of source content, which means the studio's reference 38 GB mod-asset stress test directory is fully indexed in approximately 100 seconds of background indexing time.

Daily Finder workflow

The studio's daily Finder workflow is a structured 8-step sequence that cohort members execute at the start of every modding session. The sequence takes approximately 2 minutes and establishes the Finder state that the rest of the session builds on.

Step	Activity	Shortcut
1	Open new Finder window at ~/Unturned-Mods	Cmd+N
2	Switch to Column view	Cmd+3
3	Navigate to the day's active mod directory	Arrow keys
4	Open the "Recent meshes" Smart Folder in a new tab	Cmd+T, sidebar click
5	Open the "Needs review" Smart Folder in a new tab	Cmd+T, sidebar click
6	Open the "In progress" Smart Folder in a new tab	Cmd+T, sidebar click
7	Return to the active mod directory tab	Cmd+1 (tab navigation)
8	Begin asset authoring	(workflow-specific)

The 8-step sequence is documented in the studio's onboarding materials and is the foundation that new cohort members are trained against during the deployment process documented in the previous article.

Best practice

The daily Finder workflow's 2-minute investment compounds across the workday. Cohort members who run the workflow at session start document a 14 percent reduction in mid-session navigation time versus cohort members who skip the workflow. The compounding effect over a workweek is approximately 1.5 hours of recovered session time per modder.

Finder Settings configuration

The studio's recommended Finder Settings configuration for cohort workstations is documented below. The configuration is applied during workstation deployment and is the basis for the studio's measured productivity benchmarks.

General settings

• New Finder windows show: ~/Unturned-Mods (the active project root)
• Open folders in tabs instead of new windows: Enabled
• Show these items on the desktop: Hard disks (disabled), External disks (enabled), CDs/DVDs (disabled), Connected servers (enabled)

Sidebar settings

• Favorites: AirDrop (disabled), Recents (disabled), Applications (enabled), Desktop (enabled), Documents (enabled), Downloads (enabled), Home (enabled)
• iCloud: iCloud Drive (project-dependent), Shared (disabled)
• Locations: Local disks (enabled), External disks (enabled), CDs/DVDs (disabled), Bonjour computers (disabled), Connected servers (enabled), Back to My Mac (disabled)
• Tags: Recent tags (enabled), Favorite tags (custom configuration matching the studio's six-colour convention)

Advanced settings

• Show all filename extensions: Enabled
• Show warning before changing an extension: Enabled
• Show warning before removing from iCloud Drive: Enabled
• Show warning before emptying the Trash: Enabled
• Remove items from the Trash after 30 days: Disabled (studio policy: manual Trash management)
• Keep folders on top: When sorting by name (enabled), In windows (enabled)
• When performing a search: Search the current folder (default for the studio's mod-tree workflow)

Pro tip

The "Show all filename extensions" setting is the studio's mandatory configuration. Modders working in macOS-first environments cannot accept the ambiguity that hidden file extensions introduce when authoring assets for a Windows-runtime game. Enable the setting on day one and confirm it remains enabled after every macOS update.

Best practices

• Pin ~/Unturned-Mods to Favorites
• Default to Column view for the asset tree
• Use Quick Look (Space) for format verification
• Build Smart Folders for recurring queries
• Adopt a consistent tag color convention from day one
• Configure Finder Settings against the studio's documented recommendations
• Run the daily Finder workflow at the start of every session
• Use Cmd+Shift+G to jump to deeply-nested paths by typed string
• Enable filename-extension display
• Maintain a stable Sidebar Favorites configuration (no more than 14 pinned items)

Best practice

The studio's Finder configuration is the studio's largest single productivity multiplier on the macOS-first modder workstation. The configuration is documented in the studio's internal runbook and is the basis for the studio's cohort training materials. Cohort members joining the studio review the configuration on day one and are expected to maintain it through the duration of their cohort membership.

Frequently asked questions

How do I customise the Finder toolbar?

Right-click any empty area of the toolbar and select "Customize Toolbar." Drag tools from the customisation sheet to the toolbar to add them; drag tools off the toolbar to remove them. The studio's recommended toolbar configuration includes Back/Forward, View, Group, Action, Share, Tags, and Search.

Can I navigate Finder entirely from the keyboard?

Yes. Cmd+N opens a new window, arrow keys navigate within a view, Cmd+Up navigates to the parent directory, Cmd+Down opens the selected item, Cmd+[ and Cmd+] navigate back and forward, Cmd+1 through Cmd+4 switch view modes, and Cmd+Shift+G navigates to a typed path. The studio's cohort members operate Finder primarily from the keyboard and reserve trackpad use for selection operations.

How do I show or hide the path bar at the bottom of the window?

Use View > Show Path Bar (Cmd+Option+P) to toggle the path bar. The studio's recommended configuration enables the path bar permanently. The path bar displays the full path from root to the current directory and is the macOS equivalent of Windows File Explorer's breadcrumb navigation.

How do I see hidden files in Finder?

Press Cmd+Shift+Period (.) when a Finder window has focus. The shortcut toggles hidden-file visibility. The studio's cohort members use this for diagnostic work (inspecting .DS_Store files, examining hidden configuration directories) and disable hidden-file visibility for daily asset work to reduce visual clutter.

Can I have multiple Finder windows open simultaneously?

Yes. Cmd+N opens a new window. The studio's cohort members typically maintain 3 to 5 Finder windows open simultaneously: the active project directory, one or two reference directories, and one or two Smart Folder windows. Multi-window navigation is the studio's recommended pattern for cross-directory asset comparison.

How do I use Finder tabs versus Finder windows?

Cmd+T opens a new tab in the current window. Cmd+N opens a new window. The studio's documented preference is tabs for related work (multiple views into the same project) and windows for unrelated work (one window for the active mod, another for the reference materials). The convention is the studio's measured productivity-optimal pattern from the cohort dataset.

What happens when I delete a file in Finder?

Cmd+Delete moves the selected file to the Trash. Cmd+Option+Delete deletes the file immediately without moving it to the Trash. The studio's recommended workflow uses Cmd+Delete exclusively for routine asset removal; Cmd+Option+Delete is reserved for diagnostic work and is documented in the studio's runbook as a hazardous operation.

How do I rename multiple files at once?

Select the files and press Return, or right-click and select Rename. The rename dialog offers Find and Replace, Add Text, and Format options. The studio's recommended pattern uses Find and Replace for cohort-coordinated renames (renaming a set of files to match an updated naming convention) and Format for batch sequence renaming (renaming exported frames to a consistent numbered sequence).

How do I preview the contents of a folder without opening it?

In Column view, click the folder once to select it. The rightmost column displays a preview of the folder's contents (the first nine files, in icon-grid form). The preview is the studio's recommended pattern for quick visual verification of folder contents without committing to a full navigation step.

Can I add comments to a file in Finder?

Yes. Select the file and press Cmd+I to open the Get Info window. The Comments field accepts free-text notes that are indexed by Spotlight and visible in List view if the Comments column is enabled. The studio's cohort members use Comments for asset-attribution notes (the source of a texture, the version of Blender that produced a mesh) and for cross-modder hand-off notes during cohort-coordinated work.

How do I quickly access folders I use often?

Pin them to the sidebar Favorites region by dragging them from the content view to the sidebar. The pin is persistent across sessions and is the studio's recommended pattern for the shared folder root, the active mod project, and the studio's internal asset-pipeline repository working directory.

What is the keyboard shortcut for the search box in Finder?

Cmd+F focuses the search box in the current Finder window. The shortcut is the entry point for ad-hoc Spotlight queries scoped to the current Finder window. The studio's cohort members use Cmd+F for in-directory asset lookup and reserve Cmd+Space for cross-system Spotlight queries.

Appendix A: Finder shortcuts reference

The Finder shortcuts used in this article, consolidated for reference. The shortcuts are documented for cohort use and are the basis for the studio's onboarding materials.

Shortcut	Action	Category
Cmd+N	New Finder window	Window
Cmd+T	New tab	Window
Cmd+Shift+N	New folder	File
Cmd+W	Close current tab/window	Window
Cmd+Shift+T	Reopen last closed tab	Window
Cmd+Up	Parent folder	Navigation
Cmd+Down	Open selected item	Navigation
Cmd+[	Back	Navigation
Cmd+]	Forward	Navigation
Cmd+Option+L	Go to Downloads	Navigation
Cmd+Shift+H	Go to Home	Navigation
Cmd+Shift+D	Go to Desktop	Navigation
Cmd+Shift+O	Go to Documents	Navigation
Cmd+Shift+G	Go to folder by typed path	Navigation
Cmd+1	Icon view	View
Cmd+2	List view	View
Cmd+3	Column view	View
Cmd+4	Gallery view	View
Cmd+J	Show View Options	View
Cmd+Option+P	Show/Hide Path Bar	View
Cmd+Shift+P	Show/Hide Preview Pane	View
Cmd+/	Show/Hide Status Bar	View
Space	Quick Look	Preview
Y (in Quick Look)	Open in default app	Preview
F (in Quick Look)	Full-screen Quick Look	Preview
Cmd+Option+N	New Smart Folder	Smart Folder
Cmd+Ctrl+1..7	Apply tag colour	Tags
Cmd+Space	Spotlight	Search
Cmd+F	Search in Finder window	Search
Cmd+Delete	Move to Trash	File
Cmd+Option+Delete	Delete immediately	File
Cmd+I	Get Info	File
Cmd+Shift+.	Toggle hidden files	View
Cmd+C	Copy	File
Cmd+V	Paste as copy	File
Cmd+Option+V	Paste as move	File
Return	Rename selected file	File

The reference table is the studio's authoritative shortcut documentation for cohort workstations. The table is reproduced in the studio's onboarding materials and is the basis for the shortcut training documented in the next article.

Appendix B: Smart Folder query syntax

Smart Folder queries are Spotlight queries saved as Finder objects. The query syntax is documented in this appendix for cohort members building custom Smart Folders.

Tag-based queries

The studio's tag-based Smart Folders use the following query pattern:

kind:any tag:<colour> location:"~/Unturned-Mods"

The pattern matches any file with the specified tag colour anywhere under the ~/Unturned-Mods directory tree. The query is saved as a Smart Folder through File > New Smart Folder (Cmd+Option+N), with the query entered in the Smart Folder window's search field.

Date-based queries

Date-based queries use Spotlight's date keywords. The studio's "Recent meshes" Smart Folder uses:

kind:any name:".unity3d" date:"this week" location:"~/Unturned-Mods"

Spotlight understands date keywords including "today", "yesterday", "this week", "this month", "this year", and specific date ranges entered as date:2024-01-01..2024-12-31. The studio's documented preference is the relative-date keywords for recurring Smart Folders and the absolute-date ranges for one-time queries.

Size-based queries

Size-based queries use Spotlight's size operator. The studio's "Oversized assets" Smart Folder uses:

kind:any size:>12mb location:"~/Unturned-Mods"

The query matches any file larger than 12 megabytes under the ~/Unturned-Mods tree. The studio's documented size ceiling for individual texture assets is 12 MB; the query surfaces every asset that exceeds the ceiling for review during the studio's size-budget audit.

Compound queries

Compound queries combine multiple criteria with implicit AND semantics. The studio's "Recent oversized PNG textures" diagnostic Smart Folder uses:

kind:image name:".png" size:>4mb date:"this week" location:"~/Unturned-Mods"

The query matches PNG images larger than 4 megabytes that have been modified this week. The query is the studio's recommended diagnostic Smart Folder for identifying potentially-oversized texture exports before they enter the daily asset-review workflow.

Did you know?

Spotlight's query syntax supports negation through the NOT keyword and disjunction through the OR keyword. The studio's diagnostic Smart Folders rarely use these operators because the implicit-AND semantics covers the studio's documented use cases. Cohort members building custom Smart Folders for specialised workflows occasionally use OR for tag-disjunction queries (matching files tagged Red OR Orange to surface the combined review queue).

Appendix C: Studio-deployed Finder configuration script

The studio's internal automation suite includes a Finder configuration script that applies the studio's recommended Finder Settings to a new cohort workstation. The script is run during workstation deployment and is documented in this appendix for reference.

#!/usr/bin/env bash
# finder-configuration.sh (studio standard)
# Applies the studio's recommended Finder configuration to a cohort workstation.

set -euo pipefail

# Show all filename extensions
defaults write NSGlobalDomain AppleShowAllExtensions -bool true

# Show hidden files (toggleable; default off for daily work)
# defaults write com.apple.finder AppleShowAllFiles -bool true

# Show path bar
defaults write com.apple.finder ShowPathbar -bool true

# Show status bar
defaults write com.apple.finder ShowStatusBar -bool true

# Show preview pane
defaults write com.apple.finder ShowPreviewPane -bool true

# Default view: column view
defaults write com.apple.finder FXPreferredViewStyle -string "clmv"

# New Finder windows open to the Unturned-Mods directory
defaults write com.apple.finder NewWindowTarget -string "PfLo"
defaults write com.apple.finder NewWindowTargetPath -string "file://$HOME/Unturned-Mods/"

# Open folders in tabs instead of new windows
defaults write com.apple.finder FinderSpawnTab -bool true

# Keep folders on top when sorting
defaults write com.apple.finder _FXSortFoldersFirst -bool true

# Search the current folder by default
defaults write com.apple.finder FXDefaultSearchScope -string "SCcf"

# Disable the warning when changing a file extension
# (Studio policy: keep the warning enabled; commented out as a reference)
# defaults write com.apple.finder FXEnableExtensionChangeWarning -bool false

# Apply the changes by restarting Finder
killall Finder

echo "Finder configuration applied. The studio's recommended configuration is now active."

The script is provisioned during cohort workstation deployment and is documented in the studio's runbook for cohort members standing up workstations outside the studio's deployment pathway. The script is idempotent: re-running it produces the same configuration without side effects, and the script can be safely re-run after macOS updates to confirm the configuration remains in place.

Best practice

The studio's Finder configuration script is the documented entry point for cohort workstation configuration. Cohort members who maintain their own configuration management can use the script as a reference or adapt it into their own configuration-management framework. The studio's recommendation is to maintain the configuration in a versioned script rather than applying it through the Finder Settings GUI, because the script-based approach is reproducible across workstations and across re-imaging events.

Appendix D: Finder workflow patterns by mod-development phase

The studio's documented Finder workflow varies by mod-development phase. Each phase has a characteristic Finder configuration and a documented set of patterns that the studio's cohort members apply during that phase.

Pre-production phase

The pre-production phase covers the period from initial mod concept to the start of asset authoring. The Finder workflow during pre-production emphasises reference-material organisation and project-template provisioning.

The pre-production Finder workflow is documented in the studio's onboarding materials and is the first hands-on activity that new cohort members perform during workstation deployment. The workflow takes approximately 5 minutes and produces a project structure that aligns with the studio's documented mod-directory layout.

Active-authoring phase

The active-authoring phase is the bulk of the mod-development calendar. The Finder workflow during active authoring emphasises rapid navigation, Quick Look verification, and tag-state tracking.

The studio's documented active-authoring Finder usage profile:

Activity	Percentage of Finder session time	Primary shortcut
Column-view navigation	38%	Arrow keys, Cmd+[, Cmd+]
Quick Look verification	22%	Space
Tag application	14%	Cmd+Ctrl+<number>
Smart Folder review	11%	Sidebar click
Spotlight lookup	8%	Cmd+Space, Cmd+F
Get Info inspection	4%	Cmd+I
New folder creation	2%	Cmd+Shift+N
Other operations	1%	Various

The profile is calibrated to the studio's reference workstation during a typical 4-hour active-authoring session. Cohort members with different workflow patterns produce different profiles; the studio's documented profile is the cohort median and is reproduced here for reference.

Integration phase

The integration phase covers the period after the modder has completed their assigned asset domain and the work is being integrated with other cohort members' contributions. The Finder workflow during integration emphasises Smart Folder review and asset-state verification.

The studio's documented integration-phase Finder workflow:

1. Smart Folder sweep: The modder opens each of the studio's Smart Folders in sequence and reviews the contents. Each Smart Folder represents a state-tracking view (Needs Review, In Progress, Blocked, Ready for Release, Shipped, Studio-Internal Reference), and the sweep verifies that the modder's assets are in the expected state.
2. Tag transition: The modder transitions tags as appropriate. Orange-tagged assets that have been verified are transitioned to Green; Green-tagged assets that have shipped are transitioned to Blue.
3. Cross-modder review: The modder reviews other cohort members' contributions that have been merged into the integration branch. The review uses Quick Look for rapid visual verification of each contributed asset.
4. Integration verification: The modder runs the studio's integration verification script (documented in the previous article) to confirm the merged mod directory loads correctly inside the Unturned editor.

Release phase

The release phase covers the period from final integration to the published release on Tebex. The Finder workflow during release emphasises packaging verification and archival.

The studio's documented release-phase Finder workflow:

1. Size-budget audit: The modder opens the "Oversized assets" Smart Folder and reviews each flagged asset. Oversized assets are either optimised (recompressed, downsampled, or simplified) or documented as intentional in the release notes.
2. Localisation completeness: The modder opens the "Localisation files" Smart Folder and verifies every language file is present and complete. Missing or incomplete localisations are flagged for the release coordinator.
3. Final asset QA: The modder runs through the active mod directory in Gallery view, visually verifying every asset against the studio's reference quality bar.
4. Release packaging: The modder runs the studio's release-packaging script (documented in the studio's internal toolset) and verifies the resulting release tarball.
5. Archival: The modder applies the Blue tag to the released mod's assets, transitioning the assets from Ready-for-Release state to Shipped state.

Best practice

The studio's phase-specific Finder workflows are documented in the studio's internal asset-pipeline runbook. The workflows are reviewed and refined at the end of every shared mod release, and the runbook is updated to reflect any documented improvements. The phase-specific workflows are the studio's largest documented Finder-productivity multiplier for cohort members joining the studio's shared-release effort.

Appendix E: Finder accessibility and the keyboard-centric workflow

The studio's Finder workflow is keyboard-centric by design. The keyboard-centric approach has documented productivity advantages for cohort members in the Cold-Extreme Optimal thermal band, where peripheral vasoconstriction reduces trackpad precision and shifts the modder's input weight toward the keyboard.

The studio's documented keyboard-centric patterns:

1. Cmd+Space first: The modder invokes Spotlight before opening a Finder window when the target file is known by name. The pattern bypasses the navigation step entirely and is the studio's measured fastest path to a known file.
2. Cmd+Shift+G for paths: The modder uses Cmd+Shift+G to navigate to a typed path rather than walking the sidebar or content view. The pattern is the studio's measured fastest path to a deeply-nested directory.
3. Arrow-key column navigation: The modder uses arrow keys exclusively for navigation within and between columns in Column view. The pattern produces the 2.4 directory transitions per second cadence documented earlier in this article.
4. Cmd+Down to enter: The modder uses Cmd+Down to open a selected item rather than double-clicking. The pattern keeps the modder's hands on the keyboard and is the studio's measured most-efficient open operation.
5. Cmd+W for cleanup: The modder uses Cmd+W to close tabs and windows that are no longer needed during the session. The pattern keeps the visible Finder window count manageable and is the studio's measured most-efficient cleanup operation.

Did you know?

The studio's cohort survey documents that cohort members with sustained keyboard-centric Finder workflows have a documented productivity index approximately 8 percent higher than cohort members with mixed keyboard-and-trackpad workflows. The advantage is largest in the Cold-Extreme Optimal thermal band, where the keyboard's elevated deck temperature (per the studio's thermal scheduling guide) supports sustained keystroke cadence that the cooling trackpad surface cannot match.

Appendix F: Finder versus Terminal for asset-tree operations

The studio's daily workflow uses Finder for the bulk of asset-tree operations and Terminal for specialised tasks. The choice between Finder and Terminal is documented for cohort members evaluating their own workflow.

Operation	Finder	Terminal	Studio recommendation
Navigate to a known directory	Cmd+Shift+G	cd <path>	Finder for interactive work; Terminal for scripted work
List directory contents	Open in Column view	ls -la	Finder for visual review; Terminal for diagnostic listings
Move a file	Cmd+C, Cmd+Option+V	mv <src> <dst>	Finder for single-file moves; Terminal for batch moves
Rename a file	Return on selection	mv <old> <new>	Finder for interactive renames; Terminal for scripted renames
Delete a file	Cmd+Delete	rm <file>	Finder for routine deletion; Terminal for diagnostic cleanup
Find files by content	Spotlight (Cmd+Space)	grep -r <pattern> <dir>	Finder for ad-hoc queries; Terminal for scripted scans
Compare two directories	Open in side-by-side Finder windows	diff -r <dir1> <dir2>	Terminal for systematic comparison; Finder for visual review
Audit file sizes	Sort by Size in List view	du -sh *	Finder for ad-hoc review; Terminal for scripted size budgets
Set file permissions	Get Info dialog	chmod <mode> <file>	Terminal for both; Finder's UI is verbose for permission work
Resolve symlinks	Get Info dialog shows target	readlink -f <link>	Terminal for both

The studio's documented Finder-versus-Terminal pattern uses Finder for interactive work and Terminal for scripted or automated work. The pattern aligns with the macOS design philosophy and produces a workflow that cohort members can sustain across long modding sessions without context-switching between the two tools.

Appendix G: Cohort-documented Finder tips

The studio's cohort members contribute Finder tips to the studio's internal documentation on an ongoing basis. The tips below are reproduced from the studio's tip database for cohort use.

Tip 1: Drag-and-drop with the Option key

Holding Option during a file drag in Finder copies the file rather than moving it. The visual indicator is a green plus icon next to the cursor. The pattern is useful for duplicating an asset before destructive editing, without invoking the studio's version-snapshot workflow.

Tip 2: Spring-loaded folders

Hovering a dragged file over a folder for approximately one second opens the folder, allowing the modder to drop the file into a subdirectory without releasing the drag. The pattern is the studio's recommended approach for deep directory hierarchies where the destination is several levels below the source.

Tip 3: Cmd+Click for non-contiguous selection

Cmd+Click on multiple files selects them all without selecting the files between them (the way Shift+Click does). The pattern is the studio's recommended approach for selecting a subset of files in a large directory for batch operations.

Tip 4: Cmd+Option+I for Get Summary Info

Cmd+Option+I opens a Get Info window that summarises the selected items together rather than producing a separate window per item. The pattern is useful for getting a combined size and count for a group of selected files without iterating through individual Get Info windows.

Tip 5: Cmd+Option+Y for Slideshow Quick Look

Cmd+Option+Y starts a full-screen slideshow Quick Look of the selected items. The slideshow advances through the items automatically and is the studio's recommended pattern for batch visual review of large image sets.

Tip 6: Dragging to the Path Bar

Files can be dragged onto the path bar at the bottom of a Finder window to navigate to that location in the path. The pattern is useful for moving a file to a directory that is part of the current navigation path without opening a separate Finder window.

Tip 7: Cmd+R to reveal a Spotlight result

In a Spotlight search, Cmd+R on a selected result opens the containing folder in Finder with the result selected. The pattern is the studio's recommended approach for jumping from a search hit to the surrounding context in the asset tree.

Tip 8: Smart Folders in the Sidebar

Smart Folders can be dragged into the sidebar Favorites region. The dragged Smart Folder becomes a single-click navigation target. The studio's recommended cohort workstation configuration pins the most-used Smart Folders to the sidebar for instant access.

Tip 9: Cmd+Up at the top of the hierarchy

At the root of the filesystem, Cmd+Up navigates to "Computer" which shows all mounted volumes. The pattern is useful for switching between the local Mac and external storage devices without navigating through the sidebar.

Tip 10: Cmd+T after Spotlight reveal

When opening a Spotlight result with Cmd+R, the modder can immediately press Cmd+T to open the revealed folder in a new tab in the active Finder window. The pattern is the studio's recommended approach for adding a Spotlight-discovered directory to the active session's working set without disrupting the existing tabs.

Did you know?

The studio's tip database holds 87 documented Finder tips contributed by cohort members across the studio's first three years. The tips are reviewed quarterly and the most-cited tips are promoted to the onboarding materials. The ten tips in this appendix are the most-cited tips from the studio's 2024 review.

Next steps

Finder's design choices resolve frustrations carried over from File Explorer. The next article catalogs the differences. Continue to Why Finder is Superior to File Explorer.