Skip to content
Search

Creating, editing, moving, or deleting a Pin does not by itself modify or dirty a map. Pins are external .locuspin files, not Actors, Components, or map metadata.

Does Locus make my game depend on the plugin?

Section titled “Does Locus make my game depend on the plugin?”

No. Locus is Editor-focused and does not add a runtime module. Normal use does not require gameplay code, maps, or gameplay assets to reference Locus classes. Notes, Pins, and Documents are external workspace data, not UAssets automatically cooked into a game. Shared workspace files can remain alongside the project after removal, but they do not create a runtime game dependency. See Project Impact & Dependencies.

No. Locus operates in Local Mode when no Unreal source-control provider is active. Read Source Control before using collaborative project roots.

Does Locus require an account or internet connection?

Section titled “Does Locus require an account or internet connection?”

No account, analytics service, telemetry service, or cloud backend is required for the core workspaces. Internet access is only involved when you intentionally open an external website. See Privacy and Feedback.

No. They live beneath the local project Saved storage and never interact with the source-control provider. They can still be exposed by backups or other tools that copy that directory, so “Private” describes Locus ownership—not encryption.

  • Shared Notes: <Project>/ProjectNotes/
  • Private Notes: <Project>/Saved/Locus/PrivateNotes/
  • Shared Pins: <Project>/ProjectPins/
  • Private Pins: <Project>/Saved/Locus/PrivatePins/
  • Documents: <Project>/ProjectDocuments/
  • Recovery: dedicated folders beneath <Project>/Saved/

Documents are authoritative .md files designed for external editors. Notes and Pins are structured Locus files; external changes are detected, but manual format editing is not the normal user workflow and malformed data may be rejected.

Locus Documents contains ordinary project-owned Markdown that stays in Locus. Content Browser contains only Markdown under the reserved ProjectDocuments/Content/ namespace and projects it into matching /Game contexts. Both roots use the same physical Documents repository. The Content Browser branch is intentionally sparse, so unrelated Unreal folders do not appear.

No. It can request checkout, mark-for-add, and provider-aware delete. Your team still reviews and submits through its normal workflow.

Organize a new Document while it is Untracked, then choose Mark for Add after its path is final. Locus intentionally blocks rename and move after Mark for Add, and for controlled Documents, because it cannot guarantee a provider-neutral source-control move. Use the Locus Documents workspace rather than direct Content Browser rename. See Documents and Source Control.

The Locus UI becomes unavailable, but disabling the plugin does not intentionally delete its external data. Maps continue to load without Locus-owned runtime objects. Back up and manage the retained external files deliberately.

Does Locus support multiple Unreal Engine versions?

Section titled “Does Locus support multiple Unreal Engine versions?”

The Locus 1.1 release target supports Win64 Unreal Engine 5.4–5.8. Packages are Engine-minor-specific, so use only a package identified for the project’s exact Engine version. Core Locus, C++, Blueprint, and MCP are supported across that range. The interactive and unattended Python Developer API requires Unreal Engine 5.6 or newer.

No. The Locus 1.1 release target is Win64 only. macOS and Linux are not supported release platforms.

Locus does not include an autonomous AI assistant. Its optional MCP Integration lets a compatible local client work with supported Notes, Documents, Pins, and status information while Unreal Editor is open. The connected client performs the AI workflow. See MCP Integration.

No. Locus does not automatically translate a user’s Notes, Pins, Documents, tags, or comments. Documentation interface localization is separate from project content.

Choose Give Feedback in Locus or visit feedback.pullsar.dev. Opening the site is distinct from submitting a form; review Privacy and Feedback for the metadata boundary.