# forgeChunkLoading.cfg — companion notes

Source: ported from 1.7.10 server (`industrial-server/legacy-reference/config/forgeChunkLoading.cfg`) on 2026-04-25.

## Scope

Only the two non-default fields are ported. Everything else regenerates with defaults on first boot.

## Ported fields

| Field | Legacy value | 1.12.2 default | Reason |
|---|---|---|---|
| `defaults.playerTicketCount` | `500` | `200` | Industrial pack — players run multiple persistent loaders (quarry + ME + mob farms + base). 200 is too tight. |
| `defaults.dormantChunkCacheSize` | `250` | `0` | Smooths chunk reload spikes when players cross chunk boundaries. Stock 1.12.2 disables this for memory reasons; we trade ~50–100 MB RAM for less stutter. |

## Dropped (kept at 1.12.2 defaults)

| Field | Legacy value | Default | Why dropped |
|---|---|---|---|
| `defaults.maximumChunksPerTicket` | `49` | `25` | The legacy override of 49 is risky — it lets a single ticket pin two full chunkload regions. **Recommendation: keep 1.12.2 default of 25** unless we hit an actual modpack chunkloader that demands 49. Revisit if mods complain. |
| `defaults.maximumTicketCount` | `200` | `200` | Already matches the 1.12.2 default. |
| `defaults.enabled` | `true` | `true` | Default. |
| `Forge.*` | (49/200) | n/a | Per-mod override section that just duplicated `defaults`. Useless. Dropped. |
| `FTBU.*` | (49/200) | n/a | FTB Utilities 1.7.10 mod section. FTB Utilities for 1.12.2 is a different mod (different config keys); drop and let it regen if installed. |

## Decisions

- **Did NOT carry `maximumChunksPerTicket=49`.** The legacy value was likely a blanket bump for an Ala* mod; without source-code evidence it's the safer default to start at 25 (Forge stock) and bump per-mod only if a mod's chunkloader actually fails.
- **`FTBU` and `Forge` per-mod sections were dropped** — those are 1.7.10-era artifacts. FTB Utilities 1.12.2 has its own `ftbu.cfg`/`ftblib.cfg` schema and ExtraUtilities2 doesn't use this mechanism at all.

## Risk

If on prod we see chunkloading start failing for a specific mod (`Cannot allocate ticket: <mod>`), bump `maximumTicketCount` for that mod by adding a per-mod section copying the `defaults` template.