LoreOwl

Import a project

Bring an existing Godot, Unity or Unreal project into LoreOwl from a folder, a zip, Git or Perforce.

Import

  1. On the Projects page, select Import project.
  2. Under Import from, choose a source:
    • Folder: a project on this computer.
    • Zip: a project in a zip file.
    • GitHub: a repository on GitHub or any Git host. Enter the Repository URL. For a private repository, also enter a Personal access token.
    • Perforce: a workspace that you synced with P4V or p4.
  3. Start the import.

The import continues if you close the window. You cannot stop an import that has started.

What comes across

  • Your current files arrive as one commit. The history of the old system does not come across.
  • LoreOwl saves recent commit or changelist messages on that first commit, so you can see where the project came from.
  • From Git, LoreOwl clones the default branch only. Git must be installed on this computer.

Why an import stops

LoreOwl checks the source before it copies anything. It stops the import and tells you why when:

  • Files use Git LFS but were not downloaded. The files are pointer stubs, not your art. Run git lfs fetch --all and then git lfs checkout in the source, and import again.
  • A submodule would import empty. Initialize the submodules in the source first.
  • No project is found. LoreOwl looks for project.godot, an Assets and ProjectSettings pair, or a .uproject file, at the top of the source or up to two folders down.
  • More than one project is found. Import them one at a time with the Folder option.
  • The project is too large for your plan. See Plans and billing.

Engines

How LoreOwl finds Godot, Unity and Unreal Engine, and what it does with each.

Version control

Commit, push, branch and lock files with Lore, from the Version control section of a project.

On this page

ImportWhat comes acrossWhy an import stops