• I am just lazy...

• I am just lazy...

Mod manager

1. Install PLL_Library for every player who will join the lobby.
2. Ensure BepInEx-BepInExPack_PEAK-5.4.75301, AeralisFoundation-Unified_Ray_Tracing-1.0.0 and AeralisFoundation-PLL_Fog_Resources-1.0.0 are installed.
3. Start PEAK once to generate the configuration file. Every member needs compatible PLL protocols and matching content.

Manual

1. Install BepInExPack PEAK.
2. Place unifiedraytracing at the root of the AeralisFoundation-Unified_Ray_Tracing mod directory. Gale mounts it at PEAK/BepInEx/plugins/AeralisFoundation-Unified_Ray_Tracing/unifiedraytracing.
3. Place PLL_Library.dll directly in PEAK/BepInEx/plugins/ and the resource package's NativeFog.bundle at PEAK/BepInEx/plugins/AeralisFoundation-PLL_Fog_Resources/NativeFog.bundle. Do not place the resource inside the DLL or biome bundle.
4. Start PEAK once to generate the configuration file. Every online lobby member needs compatible PLL protocols and matching content.

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

Per-biome spatial controls

Native controls are grouped under [Boundaries] and [Fog] with biome named keys:

[Boundaries]
Beach Wall Boxes = 0,10,0,2,20,100,0,0,0;20,10,0,2,20,100,0,0,0
[Fog]
Beach Fog Cutout = 40,220,0.5

Each registered custom biome receives a separate file beneath:

BepInEx/config/AF/PLL_Library/Custom Segments/

Each file records the loaded bundle's Version / Content Revision. 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.

• I am too lazy...

PLLLibrary exposes two startup registration methods.

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.

• I am too lazy...

• I am too lazy...

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

Include the following with a report:

• PLL Library, PEAK, and BepInExPack versions
• complete mod list
• current 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