On this page
- Quik, here is what we are trying to build
- What changed, and why you are receiving this
- The decision: one world, with manageable work areas
- What we need from you first
- Who supplies what
- How we keep the amount of work sane
- What success looks like for the first sample
- Technical execution plan
- What “one save” means
- First integration pass
- Daily work
- Online target and proof plan
- Measurements Legend should receive
- Technical references
- Spatial references and overlay review / 15 October
Quik: building one connected Lost Souls city
15 October 2026 · a working brief for Quik and Legend. The city architecture is a production direction; engine integration, final scale and online capacity still require proof.
Quik, here is what we are trying to build
Lost Souls needs a believable place that works across the story, concept art and playable world. Crown Key is our first detailed reference district. Legend is developing The Grove and the western coast next. Those areas need to connect physically: a player should be able to travel between them, recognize the same shoreline and bridges, and see the appropriate neighboring skyline across the water.
The long-term goal is hundreds of people sharing one persistent online city. That is a target to engineer and test, not a player count that these documents promise. We also need a practical solo/small-team authoring workflow today. Building the whole city does not mean keeping every building and interior loaded at full detail on your PC.
The island's creator direction is a visually cloaked place for AI and defense development and an experiment in comfortable, unseen control. Miami in 2043 visibly feels locked down; island life conceals more of its control. Use that contrast to guide architecture, public space and atmosphere. Exact cloak behavior, AI terminology and future-part answers remain in the Black Vault as decisions to develop; they do not supply physical dimensions.
What changed, and why you are receiving this
We found that the design images, layout files and Unreal measurements do not yet form one accepted scale. The original Crown Key layout is about 620 by 625 metres; a revised source is about 1,281 by 1,274 metres. That is about 4.19 times the original land area. We have not established what the current Unreal map actually measures. A label or an older screenshot cannot settle it.
Legend also found that some building/interior handoffs left too much for you or your AI to infer. Going forward, you should receive reviewed dimensions, floor/core plans, reference roles and a clear list of which rooms are needed. You should not have to guess building size from an attractive image or enlarge an island to compensate for an unclear brief. When a dimension is missing, record the question and owner before treating it as settled.
The latest inspected UE history also removed building mesh assets. That does not tell us everything remaining in the map, external actors or other branches. We need your current-project evidence before calling anything missing, finished or ready to replace.
The decision: one world, with manageable work areas
Use one Unreal project and one selected authoritative World Partition world. Crown Key, The Grove and future districts occupy the same coordinate frame. You can load one work region in the editor and stream content during play. Separate staging maps are useful for building and testing reusable assets; the delivered city should connect its districts as one place.
Think of it as a shared city plan with manageable work zones. You can work on a lobby or a Grove street without opening the entire city at full detail. A player approaching the bridge still needs a continuous road, matching water level and believable distant view.
“One save” has two meanings here. For development, it means one authoritative world and its coherent map, actor and asset files. For online play, it means server-owned persistent state such as identities and selected saved changes. An editor Save All supplies the first kind of saving, not the online backend.
What we need from you first
- Open the exact project and map you currently use. Send Legend the branch/commit, engine version, map path, a fresh overview and a short list of what is actually present, streamed out, removed or uncertain.
- Measure Crown Key's width/depth, key bridge endpoints and water level. Report actor AND component scale, plus imported mesh dimensions where relevant. Compare those with the source layouts in the scale register.
- Identify the best candidate for the shared world and what conversion or integration it needs. Do this on a protected copy/branch with a recovery point. Bring the trade-offs to Legend before committing the production world to a new scale.
- Agree on a small connected test area: Crown Key, its west-coast connection and one test building/interior. Do not wait for every district or every room to be designed.
- Build and record that sample. Walk, drive and boat through it; enter a furnished room; compare named cameras with the approved references; then report fit, streaming and performance issues.
Your first deliverable is a current-world report and proposed integration sample, not a complete city rebuild. Include measurements, screenshots, the exact commit/map, open questions and your recommended next move. Legend then chooses the visual/scale direction with the design and layout authors.
Who supplies what
| Person / role | Supplies | Decision or evidence |
|---|---|---|
| Legend / creator | Controlling images, district identity, intended uses and selected story requirements | Accepts visual intent, the chosen physical scale and scope |
| Design / layout author | Candidate metric layout, dimensioned plans/sections, room and opening schedules | Explains physical fit and identifies provisional dimensions |
| Quik / engine developer | Current-project measurements, integration approach, import/runtime evidence and technical recommendations | Demonstrates what works in the actual project and flags blockers |
| Assisting AI | Reads the current brief, referenced packs, approved dimensions and exact project state | Records gaps and proposals; does not invent approval or silently resize the world |
How we keep the amount of work sane
Build reusable foundations before multiplying appearances. Relentless Development supplies the cutting-edge collection; Vice Villas supplies garden/village homes and commerce; Tidemark Estates supplies coastal hospitality. These are production design collections, with corporate stories still open. A district can mix them.
Author one measured shell and one useful room kit, test them, then create selected material, roof, planting and facade options. A change to the footprint, core or openings needs a geometry variant. A color change does not need a new building foundation. Select enterable buildings deliberately; we do not need a unique full interior in every skyline tower.
The Crown Key building plan lists 31 assets and their work. For The Grove, begin with a courtyard home, a village shop/courtyard and a waterfront pavilion. Use the current protocols to decide which drawings, views and tests each needs.
What success looks like for the first sample
A person can recognize the approved Crown Key silhouette, cross the agreed west-coast connection, travel along one believable street and enter a room that fits the character, camera, furniture and building shell. Roads, terrain, water and neighboring views agree. The sample reopens from a coherent checkout, runs in a packaged build and has recorded measurements and performance evidence. Missing launcher or online functions stay visible as open work.
The full island size, every interior and final online capacity are later acceptance decisions. The next useful result is a small part of the city that proves the method and can be repeated.
Technical execution plan
The following detail is for you and any assisting AI after the project context above. Read it against your actual engine version and branch. It is not a script to run without inspecting the current map.
What “one save” means
| Layer | What is shared | What is separate |
|---|---|---|
| Authoring | One selected persistent .umap, common world settings, water datum, origin, streaming and lighting | External actor files, reusable asset packages and source-controlled work branches |
| District work | The same coordinates and cross-boundary roads, bridges, coast and views | Editor-loaded cells and named work areas; optional staging maps for assets |
| Runtime | A connected playable city with streamed geometry | Distant representations, interior streaming and era states as designed and tested |
| Online persistence | Server-owned durable identities and state | Client caches and temporary simulation; an editor Save All is not an online persistence backend |
World Partition manages spatial streaming. One File Per Actor reduces shared-map editing conflicts. Neither supplies multiplayer authority, durable state or a guaranteed player count. Data Layers represent selected content/era states; they are not a substitute for networking or a separate district-save architecture.
First integration pass
- Record the actual starting world. Pin the UE branch commit, engine build, project and map path. Export loaded actors, transforms, component bounds, mesh paths, source layout revision and known unloaded regions. Current source evidence includes
/Game/Maps/Island, Crown Key work and a western landscape study; this brief does not declare an uninspected map the final world. - Reconcile scale before copying. Compare the original v01 source, v02 source and current actor/component scale. Approve a single world frame and one coastline/layout baseline. Keep source files unchanged; issue a migration record if a measured transform is needed. Never rescale interiors to conceal a geography mismatch.
- Create a protected integration branch and backup. Select or create the authoritative Open World map after inspecting current content. Test conversion on a copy if required. Preserve the old maps as evidence. Do not run bulk delete/respawn scripts on the shared world without a scoped actor manifest and recovery point.
- Integrate Crown Key plus its western neighbor first. Align both ends of each bridge, road widths/grades, water, collision and shore. Maintain the same frame when bringing in district geometry. Check all three Crown Key connections. Do not approve either district in isolation.
- Build the distance view. Establish simplified west-coast skyline/terrain and Crown Key silhouettes with HLOD or suitable distant meshes. Compare the approved aerial and player-height views at fixed cameras. “Visible across the water” is a view requirement; its exact extent follows measured distance, elevation and art direction.
- Build one representative route. Walk, drive and boat between the two areas; enter a test lobby/room; return across the bridge. Test streaming in a packaged build with the intended movement speeds and cameras. Check collision, water, navigation, doors, lifts and spawn continuity.
- Grow from that proven slice. Reusable shells/rooms can be authored in staging maps or Level Instances, then placed in the shared world. Confirm the chosen Level Instance mode's streaming behavior in the installed UE version. Keep world-origin offsets and instance scale explicit.
Daily work
- Pull the correct branch, hydrate LFS and record the base commit before opening the project. Coordinate ownership of the world package, landscape, shared materials and overlapping actor regions.
- Load only the region plus enough neighbors to inspect its connections. Keep external actors in source control; use the existing LFS locking policy for shared binary packages. OFPA does not make conflicting edits mergeable.
- Place a registered shell with unit scale and a stable placement ID. Cosmetic variation changes material/dressing records; a footprint/core/opening change needs a geometry variant or reviewed shell revision.
- Save the map and changed actor/asset files together. Review the changed-file list and commit a coherent dependency set. A
.umapwithout its external actors is not a complete handoff. - Reopen from a clean checkout or a second machine at a milestone. Attach the exact commit, map, benchmark settings and screenshots to the acceptance record.
Online target and proof plan
The creator's target is hundreds of simultaneous users sharing one persistent city. Neither the current reference art nor this brief certifies capacity. Map area, believable resident population, visible NPCs, simulated NPCs and connected players are different budgets.
Build a dedicated-server vertical slice before multiplying content. Select and document the project's replication approach for its exact UE version; evaluate relevance, dormancy, update rates and server-side authority. Do not assume Replication Graph and Iris are interchangeable or automatically combined.
Use staged test loads such as 32, 64, 128 and 256 connected clients as experiments, not promised launch counts. Include a spread-out city test and a deliberately crowded Crown Key event. Record server frame time/tick rate, replication cost, bandwidth per client, active replicated actors, AI/navigation cost, client frame time, memory, packet loss and join/reconnect behavior on named hardware. Set pass budgets with Quik before accepting each test.
Persistence needs stable IDs, ownership/access rules, a server save schema, restart/reconnect tests, migration/versioning and recovery. Test duplicated items/actions and conflicting writes. Do not solve a failed density test by silently turning the requested shared city into unrelated district sessions. If one server cannot meet the target, bring an explicit architecture trade-off back to Legend.
Measurements Legend should receive
Quik supplies measured engine evidence; the design/layout author supplies candidate dimensions and annotated plans; Legend chooses visual intent and accepts the tested scale. Legend should not have to calculate every building. Before a scale decision, compare two or three measured blockouts using the same cameras, character, vehicle, rooms and route timings. Report what must change in each option and preserve the selected visual blueprint.
Technical references
Epic documentation, checked 15 October 2026: World Partition, One File Per Actor, Level Instancing, HLOD, Replication Graph. These describe engine features; the migration and test sequence above is this project's implementation plan.
Spatial references and overlay review / 15 October
Legend adopted the spatial imagery workflow R01. The authored shared layout feeds a simple model and saved cameras. Finished aerials, bridge approaches, street views and interior sightlines are compared against neutral views from those cameras. Record input revisions, actual editing controls, tolerances, differences and scoped approvals. A qualitative fitted overlay cannot establish metric scale.
Construction remains paused by Legend. The freestyled District 3 geography is archived and replaced from the approved master/shared frame; its coastline, roads and bridge placement are not the new foundation. Creator clearance/switchback requirements carry forward. The workflow does not approve candidate world dimensions or resume the build.
