What was the problem?

Tools were less automated than they could be by not having any integration with Perforce. Workflow-interrupting messageboxes were used to indicate when you should switch to Perforce to check out a needed file.

Additionally, as more contractors were brought on to finish the game, tools would fail since they used hard-coded filepaths.

What was the solution?

p4Ops is a simple library that allows Perforce syncing, checking out, marking a file for add or delete, and checking a file’s status. It uses standard command prompt commands for its operations.

A convertPath method was added as well that converts a filepath string from a Perforce Depot-relative path to a local path and vice versa. This meant that tools could use Perforce paths and they would work across various workspaces.