How the game editor Construct 3 uses the File System Access API to let users save their games

# Introduction

(This article is also available in form of a video.)

Construct 3 is a game editor developed by the brothers Thomas and Ashley Gullen. For the present third iteration of their game editor, the two fully » on the browser being the new operating system» after building for Windows and NW.js before. You can get an impression of some games developed with the editor by exploring its showcase or working through the guided tour. Thanks to the superpowers of the web, you can also just click through to any of the «Get inspired» examples and start editing immediately.

# The File System Access API in Construct 3

Construct provides the option of saving to local files with the File System Access API, as well as cloud save (Google Drive, OneDrive, Dropbox), and downloading of a copy of the project file. Stats the Construct developers have collected show that 65% of saves are done with the File System Access API, which demonstrates it’s what most customers want to use.

For saving, the following snippet shows the original production code for obtaining a FileSystemFileHandle from the showSaveFilePicker() method, which then serves to save the actual data. Construct makes use of the id options parameter. The id field can be specified to suggest the directory in which the file picker opens. By specifying an id, the browser can remember different directories for different IDs, which serves to start the dialog consistently in the same directory depending on the ID. For example, level files could open in Documents/levels/, whereas texture files could open in Images/textures/. The types parameter is an array of supported file types with a localized user-visual description and an accept object that tells the operating system to initially only accept .c3p files with the MIME type application/x-construct3-project.

let fileHandle = null;
try {
  fileHandle = await window({
id: "save-project-file",
types: ,
},
},
],
});
} catch (err) {
// Assume user cancelled, or permission otherwise denied.
return;
}

The Construct team have found working with files on the user’s file system to be very intuitive. It works similarly to traditional desktop apps, and integrates conveniently with other software. For example, backup software that can make backups of users’ files, or for easily sending work to other places, or editing files with external tools. They also use the File System Access API for various other use cases, such as selecting a backup folder or importing assets like animations.

# Working with large files and folders

Some of Construct’s customers work with very large projects, in the hundreds of megabytes. Saving such a large amount of work to a single file is painfully slow, let alone uploading it to a cloud service. The File System Access API lets power users work with a local folder with all their assets in separate files. This allows for very fast saves, as only the changed files need to be updated.

# Continue where you left off

Both file and directory handles can be serialized to IndexedDB, allowing Construct to provide a recent projects list that is persisted across sessions, so users can access the same file or folder again, which is a great convenience to the user. In fact, about 30% of all projects opened in Construct are opened this way. The following screenshot shows two recent projects, tetris.c3p and columns.c3p and, in the DevTools window, the corresponding FileSystemFileHandle objects serialized in an IndexedDB table.

# Drag and drop integration

The File System Access API also integrates with the Drag and Drop API, so the user can drag and drop .c3p files onto the application. Construct can then via the getAsFileSystemHandle() method on the DataTransferItem object obtain a FileSystemFileHandle, which means files opened this way can be edited and saved immediately, without having to go through a separate file save dialog.

# Retired NW.js build

Previously, the team had an NW.js build of Construct that needed maintaining and updating separately to access local files. After Chromium added support for the File System Access API in version 84, the Construct developers implemented the API in 2020, and as a by-product were able to retire the NW.js build and use the browser exclusively on all platforms. This simplifies development and avoids the need to bundle the browser engine with the app.

# Conclusions

Construct makes heavy use of the three picker methods showOpenFilePicker(), showSaveFilePicker(), and showOpenDirectoryPicker() respectively to the benefit of their users who have learned to depend on this way of working with Construct. As an additional benefit, Construct also uses the File Handling API, which allows Construct 3 to register itself as a (default) file handler of .c3p files. This means that the user can doubleclick or right-click and open with Construct 3 their game files right from the file explorer of their operating system. Fully betting on the web, Construct uses loads of other modern browser APIs—like WebGL, Web Audio, Web Workers, WebAssembly, WebRTC for multiplayer games, Local Font Access, WebCodecs for their new animation product, and even more. Their goal has always been to make full use of the web platform and show how great products can be built on top of it, so be sure to try their guided tour and create your own games.