Why Loaded - Chunk Loading Diagnostics

See why chunks stay loaded, inspect chunk tickets and available owners, and rank forced chunks with server-side commands for NeoForge 1.21.1.
Back to Files

Why Loaded 1.0.0 (Forge 1.20.1)

File namewhyloaded-1.0.0-forge-1.20.1.jar
Uploader
LanternGridLanternGrid
Uploaded
Nov 16, 2026
Downloads
2
Size
154.5 KB
Mod Loaders
ForgeNeoForge
File ID
9640445
Type
R
Release
Supported game versions
  • 1.20.1

Curse Maven Snippet

Forge

implementation fg.deobf("curse.maven:why-loaded-1790096:9640445")

NeoForge

implementation fg.deobf("curse.maven:why-loaded-1790096:9640445")

Learn more about Curse Maven

What's new

1.0.0 for Forge 1.20.1

  • First Forge 1.20.1 build of Why Loaded.
  • /whyloaded (op level 2, run as a player) shows the forced-chunk owners of the chunk you're standing in: mod, owner block, UUID or player, and whether it ticks. It also lists every ticket on that chunk with its level, and the chunk's effective load level.
  • /whyloaded top (op level 2, works from the console too) ranks forced-chunk owners in each dimension by chunk count, split into ticking and non-ticking. This includes vanilla /forceload chunks.
  • The commands only read; they never change anything.
  • Forge 1.20.1 tracks forced chunks by mod id. The controller column shows the mod id; on 1.21.1 it showed a ticket controller id.
  • Server-side only. Players don't need it.
  • Needs Minecraft 1.20.1, Forge 47.x and Java 17. Also tested on NeoForge 1.20.1 (47.1.106).

This mod has no additional files