Project

Secondary encryption keys that can be selected for use on different assets.

Games are required to make these keys available to the .pak platform file at runtime in order to access the data they protect.

Encrypts all .ini files in the .pak.

Gives security to the most common sources of mineable information, with minimal runtime IO cost.

Encrypts all files in the .pak file.

Secure, but will cause some slowdown to runtime IO performance, and high entropy to packaged data which will be bad for patching.

If true, will replicate gameplay tags by index instead of name.

For this to work, tags must be identical on client and server.

The length in bits of the first segment when net serializing tags.

We serialize NetIndexFirstBitSegment + 1 bit to indicate "more", which is slower to replicate.

GameMode to use if not specified in any other way (for example, per-map DefaultGameMode or in the URL).

You can choose any GameMode class in your project.

The default pawn class used by players.

You can choose any pawn class in your project.

HUD class this game uses.

You can choose any HUD class in your project.

The class of PlayerController to spawn for players logging in.

You can choose any PlayerController class in your project.

The class of GameState associated with this GameMode.

You can choose any GameState class in your project.

GameMode to use if not specified in any other way (for example, per-map DefaultGameMode or in the URL).

This setting is only used when running the engine as a dedicated server.

You can choose any GameMode class in your project.

If not set, the GlobalDefaultGameMode value will be used.

If set, this map will be loaded when the Editor starts up.

You can choose any map available in your project.

Map templates that should show up in the new level dialog.

This will completely override the default maps chosen by the default editor.

The map that will be loaded by default when no other map is loaded.

You can choose any map available in your project.

The map that is loaded when transitioning from one map to another.

You can choose any map available in your project.

The map that will be loaded by default when no other map is loaded.

This setting is only used when running the engine as a dedicated server.

You can choose any map available in your project.

The viewport layout to use if the screen should be split and there are two local players.

You can choose from the following options:

• Horizontal
• Vertical

The viewport layout to use if the screen should be split and there are three local players.

You can choose from the following options:

• Favor Top
• Favor Bottom
• Horizontal
• Vertical

The viewport layout to use if the screen should be split and there are four local players.

You can choose from the following options:

• Grid
• Horizontal
• Vertical

If enabled, this will make it so that gamepads start being assigned to the second controller ID in local multiplayer games.

In PIE (Play in Editor) sessions with multiple windows, this has the same effect as enabling the Route 1st Gamepad to 2nd Client setting in Editor Preferences.

The class to use when instantiating the transient GameInstance class.

You can choose any GameInstance class in your project.

Movies to play on startup.

Note that these must be in your game's Game/Content/Movies directory.

If enabled, will generate .pak file chunks.

Assets can be assigned to chunks in the editor or via a delegate (see ShooterGameDelegates.cpp).

Can be used for streaming installs (PS4 Playgo, XboxOne Streaming Install, etc).

Normally, during chunk generation, all dependencies of a package in a chunk will be pulled into that package's chunk.

If this is enabled, only hard dependencies are pulled in. Soft dependencies stay in their original chunk.

If enabled, it will generate data for HTTP Chunk Installer.

This data can be hosted on a web server to be installed at a runtime.

Requires the Generate Chunks option to be enabled.

By default, shader code gets saved inline inside Material Assets. Enabling this option will store only shader code once as individual files.

This will reduce overall package size, but might increase loading time.

If this option is disabled, the shader code will be stored in the library essentially in a random order, squarely the same in which the assets were loaded by the cooker.

Enabling this option will sort the shaders by their hash, which makes the shader library more similar between builds. This can help patching, but can adversely affect loading times.

By default, shader code gets saved into individual platform-agnostic files. Enabling this option will use the platform-specific library format only if one is available.

This will reduce overall package size but might increase loading time.

A list of custom builds that will show up in the Platforms menu to allow customized builds that make sense for your project. Will show up near Package Project in the Platforms menu (in the main Level Editor toolbar).

If true, individual files are only allowed to be in a single chunk and it will assign it to the lowest number requested.

If false, files may end up in multiple chunks if requested by the cooker.

If greater than 0, this sets a maximum size per chunk.

Chunks larger than this size will be split into multiple .pak files such as pakchunk0_s1.

This can be set in platform-specific game .ini files.

A comma-separated list of formats to use for .pak file and IoStore compression.

If more than one format is specified, the list is in order of priority, with fallbacks to other formats in case of errors or unavailability of the format (for example, if the format's plugin is not enabled).

Commonly PackageCompressionFormat=Oodle or PackageCompressionFormat=None.

If enabled, forces the use of the specified Package Compression Format.

This option overrides any platform-specific values set by the HardwareCompressionFormat parameter in DataDrivenPlatformInfo.ini.

A generic setting for allowing a project to control compression settings during .pak file and IoStore compression.

For example: PackageAdditionalCompressionOptions=-compressionblocksize=1MB -asynccompression.

For compressors with multiple methods, select one. For example, for Oodle, you may use one of these:

• Kraken
• Mermaid
• Selkie
• Leviathan

You can read the description of every method here.

For compressors with variable levels, select the encoder level, which makes packages smaller but takes more time to encode.

This does not affect decode speed.

For faster iteration, use lower effort levels (for example, 1).

A generic setting which is used to determine whether it is worth using compression for a block of data when creating IoStore or .pak files.

If the amount of saved bytes is smaller than the specified value, then the block of data remains uncompressed.

The optimal value of this setting depends on the capabilities of the target platform. For example, PackageCompressionMinBytesSaved=1024.

Note that some compressors (for example, Oodle) do their own internal worth it check and only use this value to determine the minimal size of a block which should be compressed.

A generic setting which is used to determine whether it is worth using compression for a block of data when creating IoStore or .pak files.

If the saved percentage of a compressed block data is smaller than the specified value, then the block remains uncompressed.

The optimal value of this setting depends on the capabilities of the target platform. For example, PackageCompressionMinPercentSaved=5.

Note that some compressors (for example, Oodle) do their own internal worth it check and ignore this value.

Specifies whether to include the crash reporter in the packaged project.

This is included by default for Blueprint-based projects, but can optionally be disabled.

Predefined sets of cultures whose internationalization data should be packaged.

You can choose from the following options:

• English
• EFIGS: English, French, Italian, German, Spanish
• EFIGSCJK: English, French, Italian, German, Spanish, Chinese, Japanese, Korean
• CJK: Chinese, Japanese, Korean
• All

Cook only maps (this only affects the Cookall flag).

Don't include content in any editor folders (anything under Engine/Content/Editor*) when cooking.

This can cause issues with missing content in cooked games if content that the game uses is being excluded.

This setting tells the Editor to not include movies by default when staging or packaging.

If this setting (bSkipMovies in the .ini file) is true, all movie files in Engine\Content\Movies and <ProjectRoot>\Content\Movies are skipped, and the movies listed in UFSMovies and Non-UFSMovies are staged or packaged.

If this setting (bSkipMovies in the .ini file) is false, all movie files in Engine\Content\Movies and <ProjectRoot>\Content\Movies are staged or packaged.

If bSkipMovies is true, these specific movies will still be added to the .pak file (if using a .pak file; otherwise, they're copied as individual files).

The name of the movie file should have no extension in the listing: if the filename of your movie is, for example, Level2CinematicScene.mp4, you should add Level2CinematicScene to this array.

If SkipMovies is true, these specific movies will be copied when packaging your project, but are not supposed to be part of the .pak file.

The name of the movie file should have no extension in the listing: if the filename of your movie is, for example, Level2CinematicScene.mp4, you should add Level2CinematicScene to this array.

If set, only these specific .pak files will be compressed.

This should take the form of *pakchunk0*.

This can be set in a platform-specific .ini file.

Directories containing .uasset files that should always be cooked regardless of whether they're referenced by anything in your project.

These paths are stored either as a full package path (for example, /Game/Folder, /Engine/Folder, /PluginName/Folder) or as a relative package path from /Game.

Directories containing .uasset files that should never be cooked, even if they are referenced by your project.

These paths are stored either as a full package path (for example, /Game/Folder, /Engine/Folder, /PluginName/Folder) or as a relative package path from /Game.

Directories containing .uasset files that are for editor testing purposes and should not be included in enumerations of all packages in a root directory because they will cause errors on load.

These paths are stored either as a full package path (for example, /Game/Folder, /Engine/Folder, /PluginName/Folder) or as a relative package path from /Game.

Directories containing files that should always be added to the .pak file (if using a .pak file; otherwise they're copied as individual files).

This is used to stage additional files that you manually load via the UFS (Unreal File System) file IO API.

Directories containing files that should always be copied when packaging your project, but are not supposed to be part of the .pak file.

This is used to stage additional files that you manually load without using the UFS (Unreal Files System) file IO API, for example, third-party libraries that perform their own internal file IO.

Directories containing files that should always be added to the .pak file for a dedicated server (if using a .pak file; otherwise they're copied as individual files).

This is used to stage additional files that you manually load via the UFS (Unreal File System) file IO API.

Directories containing files that should always be copied when packaging your project for a dedicated server, but are not supposed to be part of the .pak file.

This is used to stage additional files that you manually load without using the UFS (Unreal Files System) file IO API, for example, third-party libraries that perform their own internal file IO.

Specifies whether to build the game executable during packaging.

You can choose from the following options:

• Always
• Never
• If Project Has Code, or Running a Locally Built Editor
• If Running a Locally Built Editor

The build configuration for which the project is packaged.

You can choose from the following options:

• Debug
• DebugGame
• Development
• Test
• Shipping

If enabled, a full rebuild will be enforced each time the project is being packaged.

If disabled, only modified files will be built, which can improve iteration time.

Unless you iterate on packaging, we recommend full rebuilds when packaging.

If enabled, a distribution build will be created using the shipping configuration.

If disabled, a development build will be created.

Distribution builds are for publishing to the App Store.

A directory containing additional prerequisite packages that should be staged in the executable directory.

Can be relative to either the Engine folder within your Unreal Engine installation directory or the folder where your .uproject file is located.

Select the hardware class and a graphical level.

You can choose from the following options:

• Class of hardware to target:

  • Desktop: Desktop or console

  • Mobile: Mobile or tablet

• Graphical level to target:

  • Maximum: High-end features default to enabled.

  • Scalable: Some features are disabled by default but can be enabled based on the actual hardware.