• No Sky Props is enabled by default for newly generated configuration files. Existing configuration files retain their stored value.

• I will write this later... I guess Layout Order and Custom Biomes.

Mod manager

1. Install PLL_Library through a PEAK and Thunderstore compatible mod manager.
2. Ensure BepInEx-BepInExPack_PEAK-5.4.75301 is installed.
3. Start PEAK once to generate the configuration file.

Manual

1. Install BepInExPack PEAK.
2. Place PLL_Library.dll directly in PEAK/BepInEx/plugins/.
3. Start PEAK once to generate the configuration file.

Custom content

Place custom .pll files built with PLL Creator directly in:

PEAK/BepInEx/plugins/PLL_Biomes/

Only files with the exact lowercase .pll extension are discovered.

Configuration file:

BepInEx/config/AF/PLL_Library/config.cfg

Client configuration files may differ. The host's resolved gameplay values are the flight authority. PLL / Advertise Layout remains each client's local display preference. An empty Map / Seed creates a fresh random seed on world entry. Any nonempty text produces the same deterministic numeric seed.

Each registered custom biome receives a separate file beneath:

BepInEx/config/AF/PLL_Library/Custom Segments/

Its Favorites, Overwrites, Before, After, and Spawn Chance values begin with the bundle defaults and remain editable by the user. Spawn Chance is an inclusive 0 through 100 percentage used by Generative Map. The host resolves these values for the flight.

• Default uses the configured Map / LayoutOrder and Map / DoOrder values. With ordering off and neither Generative Map nor InfiniteMap active, PLL keeps PEAK's current authored base layout and active variant choices. Registered modifications targeting LayoutId.Default apply to this selection.
• Library Base appears whenever the effective Default selection differs from PLL's compiled LayoutOrder default. This includes a disabled DoOrder value or a registered modification targeting Default. Library Base is not a named layout and does not rewrite configuration. It selects the compiled default order, enables ordering for the selected flight, and ignores modifications targeting Default. The terminal override clears after the flight configuration is captured.
• Named layouts supply their own ordered tokens and always enable ordering for the selected flight.

Each layout sequence contains public ordinary choices only. Exact public native names and exact custom segment IDs select a source. Qualified biome tokens such as peak/beach select from registered owners and declared overwriters. Caldera, Gloom, and Peak are internal structure (for the time being). Those names and their structural aliases are rejected as layout tokens. The solver maximizes valid overwrite substitutions, then Before and After, then Favorites, and finally ordinal stable ID order. Metadata never inserts a biome by itself.

PLLLibrary exposes two startup registration methods. It does not expose raw registry mutation or active flight mutation.

using BepInEx;
using PLL.Library;

namespace Example.PLL;

[BepInPlugin("example.pll.layout", "Example PLL Layout", "1.0.0")]
[BepInDependency(PLLLibrary.PluginGuid, BepInDependency.DependencyFlags.HardDependency)]
public sealed class ExampleLayoutPlugin : BaseUnityPlugin
{
    void Awake()
    {
        var Layout = new LayoutDefinition(
            new LayoutId("example/extended-ascent"),
            "Extended Ascent",
            "1",
            new[]
            {
                "Beach", "Tropics", "Roots", "Alpine",
                "Mesa", "Volcano", "Citadel", "Nadir"
            });
        PLLLibrary.DeployLayout(Layout);
    }
}

This example targets the named Extended Ascent layout registered above.

using BepInEx;
using PLL.Library;

namespace Example.PLL;

[BepInPlugin("example.pll.modification", "Example PLL Modification", "1.0.0")]
[BepInDependency(PLLLibrary.PluginGuid, BepInDependency.DependencyFlags.HardDependency)]
public sealed class ExampleLayoutModificationPlugin : BaseUnityPlugin
{
    void Awake()
    {
        var Modification = new LayoutModification(
            "example/move-mesa",
            "1",
            new LayoutId("example/extended-ascent"),
            new[]
            {
                LayoutEdit.InsertAfter("Roots", 0, new[] { "Mesa" }),
                LayoutEdit.Remove("Mesa", 0)
            });
        PLLLibrary.ModifyLayout(Modification);
    }
}

Both edits resolve against the original Extended Ascent sequence. Remove("Mesa", 0) removes the original Mesa, not the inserted Mesa. The result is Beach > Tropics > Roots > Mesa > Alpine > Volcano > Citadel > Nadir.

A .pll is a Windows AssetBundle built by PLL Creator. It contains validated data and Unity assets, not executable plugin code. Runtime discovery loads the bundle, validates its registered definitions and reachable prefab graph, registers all accepted content in one transaction, and keeps a successful bundle loaded for the process lifetime.

Every custom biome requires:

• one canonical lowercase qualified biome ID and one content revision
• one inactive segment prefab with CustomSegmentRuntime and PllBiomePrefabAnchors on its root
• zero or one direct PllBiomeRoot link to the owning definition
• valid Entry, Exit, and Start ports with compatible connector tokens
• one DayNightProfile owned by the project
• one PllFogAuthoring owner on the exact runtime fog origin
• complete fixture, item, generation, visual, sound, and native resolver ownership for every authored capability

The Creator package contains the complete component tables, enum values, ownership rules, native resolver shapes, validation steps, and .pll build workflow. A separately installed peer plugin is required for executable layout registration, runtime hook handling, or other code.

Install com.aeralis.pll.creator-3.1.0.tgz through Unity Package Manager with Add package from tarball. Use a Unity project with Standalone Windows 64 support installed.

1. Wait for Unity to import and compile the package.
2. Run PLL > Configure and select the PEAK installation root.
3. Run PLL > Create Biome to create an inactive source prefab, definition, ports, anchors, fog and progress owners, and the required DayNightProfile owned by the project.
4. Use the focused PLL > helpers for supported authoring components.
5. Select one or more PllBiomeDefinition or PllBiomeRegistry assets.
6. Run PLL > Validate Selected Biome.
7. Run PLL > Build .pll and choose a destination outside the Unity project.

PLL > Create Biome creates this top-level source topology:

<BiomeName> [CustomSegmentRuntime, PllBiomePrefabAnchors, PllBiomeRoot]
|- FloorRoot
|- CampfireRoot
|- RuntimeMarkers
`- Presentation

Copy Config.Build.user.props.template to Config.Build.user.props. Set PEAKManagedDir in the copied file to the installed PEAK_Data\Managed directory, then run:

dotnet build .\PLL_Library.slnx -c Release

Release solution builds compile and package all four outputs. Debug and design time builds compile without packaging.

Include the following with a report:

• PLL Library, PEAK, and BepInExPack versions
• complete mod list
• BepInEx/LogOutput.log, and PEAK Player.log
• BepInEx/config/AF/PLL_Library/config.cfg
• selected terminal layout and text seed
• custom bundle filename, stable IDs, and revisions when custom content is involved
• whether the failure occurs offline, as host, as client, during late join, or during quicksave continuation