How to check whether a Project Zomboid Java mod is loaded

Add the status viewer only if you need it

Zed's Better ModList enhances the existing mod selector. Its README requires Build 42.12 or later, ZombieBuddy's one-time setup, and zdk. Obtain the original Workshop item and use its current required-items links for the dependencies; this site does not supply a replacement bundle.

1. Subscribe to the original items and enable Better ModList, ZombieBuddy and zdk.
2. Confirm the loader setup matches your actual launch method.
3. Restart, review the viewer's own Java approval, and check the ZombieBuddy loaded indicator.
4. Open the mod selector and use the Java filter to inspect the intended item and JAR path.

This optional viewer is for the client UI. It is not required just to change the camera and does not audit a dedicated server's complete runtime.

Read the three status pairs separately

Loaded / blocked

Did this Java file load, or was it blocked? A blocked item is not proof its Workshop download is absent.

Allow / deny

What decision applies to this file? If you denied the intended file accidentally, follow the targeted approval reset.

Persisted / session

Was the decision saved, or does it apply only to this session? Do not assume a temporary choice will govern a later launch.

The Enabled filter answers which mods are enabled; Java identifies Java-bearing items; New helps locate new items. Those filters answer different questions. Match the path to the intended item rather than judging only its display name.

If the Java filter or status fields are missing

Check that all three requirements are enabled and ZombieBuddy actually loaded. The viewer cannot reveal a Java runtime that never started. Return to the loader branch if its indicator is missing; do not install a second agent as a workaround.

If the loader is present but the viewer is not, preserve the startup log and its approval state. If the viewer loads but a companion is absent, check that companion's enabled state and exact required items. Use the installed version's instructions before assuming a screenshot from an older manager matches its UI.

Loaded is a starting point, not a compatibility verdict

1. Note the game build, loader version, mod ID, JAR path and observed state.
2. Use a backed-up test world and perform the feature's own action: O for Viewpoint, or the companion's configured control.
3. If it fails while the JAR is loaded, record the action and log rather than repeatedly resetting approvals.
4. If only multiplayer fails, compare the client state with the server’s intended mod set.

The viewer does not prove every patch applied correctly, every object has a model, or every player shares a compatible save. A Lua-only mod needs its own feature and log checks; this Java-state guide is not a universal mod-testing tool.