Logistics Network Addressing Standard (LNAS) v1.0

1.0 Introduction

This document establishes the official standards for addressing and filtering packages within our world's Create mod logistics network. This is a major revision that introduces Network Zones to handle complex routing (like bridges and portals) and integrates the Nether as a unique zone.

The primary goal is to create a unified system that is:

Robust: Handles complex geographical layouts, including bridged continents and dimensional travel, without logical flaws.
Intuitive: Uses a mnemonic, letter-based mapping for continent locations.
Massively Scalable: Supports a vast number of continents and areas with an expanded indexing system.
Reliable: Provides clear, copy-paste-ready filter logic for all scenarios.

Adherence to this standard is crucial for the seamless, automated, and error-free operation of our entire logistics infrastructure.

2.0 Core Standard: Rules & Guidelines

This section defines the mandatory structure for all package addresses.

2.1 Address Format

The address format remains consistent.

CC-AAA DestinationName

Component	Code	Separator	Description
Continent	`CC`	`-`	A 2-character code for the continent/landmass/zone.
Area	`AAA`	(space)	A 3-character mnemonic code for a specific base.
Destination	`DestinationName`		A descriptive name for the contents or target.

Example: C0-AST Main Storage (18 characters)

2.2 Continent & Zone Codes (`CC`)

Continents are identified using a Mnemonic Directional System. The first character is a letter representing the direction, and the second is a hexadecimal index (0-9, then A-Z).

Overworld Directional Map:

  Q(NW) N(N) R(NE)

  W(W)  C(C)  E(E)

  Z(SW) S(S) J(SE)

C0: The special code for the Center/0-point (Main Continent).
R1: The 1st continent to the North-East.
SA: The 10th continent to the South.

Special Zone Codes:

X0: The code for the Nether Zone. The Nether is treated as a single, unique "continent" accessible via portals.

3.0 Advanced Routing: Network Zones & Explicit Filtering

This is the most critical change in LNAS v5.0. We are abandoning the simple !CC* filter for a more intelligent system.

A Network Zone is a collection of one or more continents connected by direct train lines (land bridges). Travel between zones requires a special transport method (a "boat" for sea travel, or a portal for dimensional travel).

Instead of a filter that grabs "everything not for here," our transfer points (ports, portal stations) will now use explicit filters that list exactly which zones they service.

3.1 The Bridged Continent Problem & Solution

Problem: Continent C0 is connected to E1 by a bridge. The sea port on C0 services the remote continent S1. With the old !C0* filter, a package from C0 to E1 would be incorrectly sent to the sea port.

Solution: The sea port's filter will now explicitly list only the continents it can reach.

Port Filter Pattern: {CC1*, CC2*, ...}
Example: The filter on the train line leading to the C0 sea port would be:
```
S1*
```
(Or {S1*, Q1*} if it also services the Q1 continent).
Result: A package for E1-HUB will not match this filter and will stay on the main line to cross the bridge. A package for S1-HUB will match and be diverted to the port.

3.2 Nether Portal Routing

The same logic applies to Nether travel. A train station built at a Nether portal is a transfer point to the "Nether Zone" (X0).

Portal Station Filter Pattern: X0*
Result: Any package addressed to X0- (e.g., X0-BLZ Blaze Rods) traveling on the Overworld network will be pulled by this filter and sent through the portal. The reverse is true for a portal station in the Nether, which would use filters like {C0*, E1*, S1*} to grab packages destined for specific Overworld continents.

4.0 Examples & Scenarios

4.1 Scenario: Delivery Across a Bridged Continent

Goal: Send Gears from Astral's Base (C0-AST) to a new base on the bridged Eastern continent (E1-HUB). The C0 sea port only services S1.

Packaging: Address the package: E1-HUB Gears
Local Sorting (at C0-AST): The standard !C0-AST* filter sends the package to the C0 train network.
Mainline Travel: The package travels the main train line. It passes the junction for the sea port.
- Port Junction Filter: S1*
- Result: The address E1-HUB Gears does not match S1*. The package is ignored by the port junction and continues along the main line, across the bridge to the E1 network.
Final Delivery: Once on the E1 network, the train delivers it to the E1-HUB station, which uses a standard E1-HUB* filter.

4.2 Scenario: Delivery to the Nether

Goal: Send Obsidian from Astral's Base (C0-AST) to a Nether base (X0-FORT).

Packaging: Address the package: X0-FORT Obsidian
Local Sorting (at C0-AST): The !C0-AST* filter sends the package to the C0 train network.
Dimensional Sorting: The package travels the main line until it reaches the junction for the Nether Portal station.
- Portal Junction Filter: X0*
- Result: The address X0-FORT Obsidian matches X0*. The package is diverted off the main line and sent to the portal station for transfer to the Nether.

5.0 Quick Reference Guide

Location	Purpose	Filter Pattern	Example (for `C0` network)
Local Conveyor	Send non-local items to train	`!CC-AAA*`	`!C0-AST*`
Train Station	Pull local items from train	`CC-AAA*`	`C0-AST*`
Sea Port Junction	Pull items for specific remote continents	`{CC1,CC2...}`	`{S1,Q1}`
Portal Junction	Pull items for the Nether Zone	`X0*`	`X0*`

svemat01/lnas.md