Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 38 ยท Editor and Projects

Unreal Project Folder Structure, Config Files and Settings

Understand every folder in an Unreal Engine project, what goes into version control, how Config .ini files and Project Settings work, and how to add plugins safely.

An Unreal project is a folder with a few well-defined parts. Knowing which parts are yours, which are generated, and where settings live lets you back up correctly, use version control without pain and diagnose "it works on my machine" problems. This lesson goes through the folder layout, the .ini configuration files, Project Settings and plugins.

The folders

TEXT
MyGame/
  MyGame.uproject
  Config/
  Content/
  Source/              (C++ projects)
  Plugins/             (optional, project-local plugins)
  Saved/               (generated)
  Intermediate/        (generated)
  Binaries/            (generated)
  DerivedDataCache/    (generated, optional)
  .vs/ or .idea/       (IDE files, generated)
  • .uproject: JSON that lists the engine version, modules and plugins. Opening it starts the editor.
  • Config/: your settings as .ini text files. Keep.
  • Content/: all assets (.uasset) and levels (.umap). They are binary files. Keep, ideally in version control with Git LFS or Perforce.
  • Source/: your C++ modules (.h, .cpp, .Build.cs, .Target.cs). Keep.
  • Plugins/: plugins that live inside the project. Keep.
  • Saved/: logs, screenshots, autosaves, crash dumps, cached config. Delete freely.
  • Intermediate/: generated project files and build data. Delete when odd build errors appear; it is rebuilt.
  • Binaries/: compiled editor and game modules. Rebuilt on demand.
  • DerivedDataCache/: compiled shaders and baked data. Rebuilds slowly; a shared cache speeds up teams.
Python Stand-in: a .gitignore for Unreal

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The .sln solution file is generated from the .uproject (right-click the .uproject > Generate Visual Studio project files), so it is not committed.

Config files and layers

Settings are stored in .ini files, merged in layers where later layers override earlier ones:

  1. Engine/Config/Base*.ini (engine defaults)
  2. Engine/Config/<Platform>/...
  3. Config/Default*.ini (your project defaults: DefaultEngine.ini, DefaultGame.ini, DefaultInput.ini, DefaultEditor.ini)
  4. Config/<Platform>/<Platform>*.ini
  5. Saved/Config/<Platform>/*.ini (a user's local overrides)

You change project settings in the editor (Edit > Project Settings), and the editor writes them into the right Default*.ini file. That is the file to commit. A typical entry looks like:

INI
[/Script/EngineSettings.GameMapsSettings]
EditorStartupMap=/Game/Maps/L_Main.L_Main
GameDefaultMap=/Game/Maps/L_Main.L_Main

[/Script/Engine.RendererSettings]
r.DefaultFeature.AutoExposure=False

Sections are bracketed class paths; keys are property or console variable names. Console variables (r. for rendering, t. for time, sg. for scalability) can also be set in [SystemSettings] of an ini.

Python Stand-in: reading an ini file with layers

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Project Settings worth knowing

Open Edit > Project Settings. Some key pages:

  • Project > Description: name, version, company, icon.
  • Project > Maps & Modes: the Editor Startup Map, Game Default Map and the default Game Mode.
  • Engine > Input: input actions and axes (or Enhanced Input).
  • Engine > Physics, Collision: collision channels and presets.
  • Engine > Rendering: Lumen, Nanite, ray tracing, anti-aliasing.
  • Platforms: Windows, Android and others, with packaging options.

Use the search box at the top; there are hundreds of options.

Plugins

Edit > Plugins lists plugins by category. Enable a plugin, then restart the editor. Plugins are stored in the engine's Plugins folder (engine-wide) or in your project's Plugins folder (project-only). Marketplace/Fab downloads install into the engine unless you copy them. Enabled plugins appear in the .uproject. Turn off unused plugins to shorten startup and package size.

Source control

Unreal works well with Perforce (the industry norm, handles big binaries and file locking), Git with Git LFS (many indie teams) and Plastic SCM / Unity Version Control. Because .uasset and .umap files are binary and cannot be merged, teams lock files or use One File Per Actor (OFPA) so two people can edit different actors in the same level. The toolbar's Source Control menu connects a provider.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which folder can you delete safely to force regeneration?

    Intermediate holds generated build data that is rebuilt on demand.
  2. 2. Where does the editor write project-wide settings you change in Project Settings?

    Project Settings are stored in the Default ini files in the Config folder.
  3. 3. Which layer wins when the same setting appears in several ini files?

    Later layers override earlier ones, so project and user files override engine defaults.
  4. 4. Why use file locking or One File Per Actor?

    Binary .uasset and .umap files cannot be merged like text, so teams avoid simultaneous edits.

Summary

  • Keep .uproject, Config, Content, Source and Plugins; do not commit Saved, Intermediate, Binaries.
  • Settings live in layered .ini files; later layers override earlier ones.
  • Project Settings and Plugins are the main configuration points; plugins need a restart.
  • Use Perforce or Git LFS with file locking for binary assets.

Next: Levels, World Partition and Sublevels