# Perforce P4

Version control suited to asset workflows that need configured exclusive file editing.

ID: perforce-p4
Language: en
Revision: 1
Translation source revision: 1
Canonical: https://kickoff.jujin.dev/en/catalog/perforce-p4/

## Why: the goal or problem

A racing game team edits 3D vehicle models. Two artists’ changes to one binary model cannot be usefully merged. Coordinating exclusive edits matters more here than parallel text branches.

## How: work toward a solution

Set the model’s file type to binary+l. One artist opens it for editing; another open is refused. Submit the finished changelist, then the next artist syncs and edits.

## What: the concept

Perforce P4, formerly Helix Core, manages versioned files through a server and workspaces. Exclusive opening requires +l configuration; p4 lock alone does not prevent another open. Locks can cause waits, and server operation and licensing need planning.

[Source](https://help.perforce.com/helix-core/server-apps/cmdref/current/Content/P4Guide/resolve.lock.exclusive.html)

---

# Go further

Optional reading · separate from the overview

## Selection & comparison

Compare asset characteristics before choosing a system. The example uses a binary model for which merging competing edits is impractical; configured exclusive access serializes work. Git and Mercurial favor distributed local history, while SVN can also use locks. P4 is not the only locking option: existing asset tools and team workflow decide the fit.

## Applications

The vehicle model is explicitly assigned binary+l. An artist opens it, edits and submits a changelist to the depot; the next artist syncs the submitted version. This models a central P4 workflow, not every available topology. A failed submission does not prove the next artist can proceed.

## Implementation & cautions

Review the typemap for selected asset types. Distinguish +l, which restricts opening, from p4 lock, which restricts submission. Name an owner for abandoned-lock recovery and repository backups. Recheck current licensing, user limits and hosting terms for the team’s actual workload; this article makes no free-tier or price promise.

## Evidence

- [P4: Preventing multiple checkouts](https://help.perforce.com/helix-core/server-apps/cmdref/current/Content/P4Guide/resolve.lock.exclusive.html) — The +l file type prevents concurrent opens; p4 lock only restricts submission. (Checked: 2026-09-27)
- [P4: p4 submit](https://help.perforce.com/helix-core/server-apps/cmdref/current/Content/CmdRef/p4_submit.html) — Changelist submission and failure behavior. (Checked: 2026-09-27)