mod.info. Wait about
30 seconds and hit sort again. Every later sort with those mods is
instant.,
},
{
q: 'i pasted the lines and the mods still are not loading',
a: <>All three lines have to land in the same servertest.ini (or
whatever your server is named), the server has to be fully stopped when
you edit it, and the values take no spaces after the =.
Full walkthrough: add mods to your server.,
},
{
q: 'what is a "missing dependency" warning?',
a: <>A mod declared require=SomethingElse and that something
else is not in your list. The game will load the mod and then break the
moment it reaches for the missing code. Use the [add]
button on the warning to drop the required workshop id straight into
your input, then sort again.,
},
{
q: 'my map mod does not show up, or spawns are wrong',
a: <>Map folders are their own line and their own fight: when two maps claim
the same cell, the one listed first in Map= wins.
We put Muldraugh, KY last so vanilla never eats a custom
cell. Detail: add map mods.,
},
{
q: 'half my mods are flagged "build mismatch"',
a: <>You are sorting on the wrong build. B41 and B42 mods are not
interchangeable, and Steam tags each item with the build it targets.
Flip the B41 / B42 toggle and sort again. Some items ship both builds in
one workshop id; those get a branch picker instead of a warning.,
},
{
q: 'two mods have the same mod id',
a: <>Two separate workshop items ship the same internal mod id, so the game
loads exactly one of them and silently ignores the other. Keep whichever
one you actually want and drop the other from your list.,
},
{
q: 'does the order of WorkshopItems matter?',
a: <>No. WorkshopItems= is only the download list. Load order
comes from Mods=, and map priority from Map=.
We still emit all three because the server needs all three.,
},
{
q: 'i want to drop a mod mid-save',
a: <>Removing a mod mid-save can strip items, vehicles or whole map cells
out from under your players. Read remove
a mod first, then re-sort the shortened list here.,
},
{
q: 'i sorted the same list twice and got a different answer',
a: <>A mod author published an update in between. We key our cache on
Steam's time_updated, so when a mod changes we re-read its
mod.info and its declared requirements may have moved.,
},
];
function HowItWorks() {
return (
Project Zomboid loads mods top to bottom in the order you list them in
Mods=. Get that order wrong and you get missing textures,
recipes that never register, and a server that dies on boot with a stack
trace nobody wants to read. Sorting it by hand is miserable past about
fifteen mods. So: paste ids, get the three lines.
mod.info,
the small manifest each mod ships. That is where its real mod id,
its map folders and its declared relationships live.
require= (load these before me),
incompatible= (never load with me), and
loadFirst / loadLast. Add any sorting rules
you paste in yourself, and that is a dependency graph.
WorkshopItems= (what to download),
Mods= (load order), Map= (map folder
priority). Anything we could not reconcile becomes a warning instead
of a silent guess.
The first sort touching a brand-new mod is slow, we have to download it to read the manifest. After that it stays cached until its author publishes an update, at which point we re-read it automatically.
Counted across every B42 sort run on this site, most recent snapshot. Not a recommendation, just what people actually run.
{m.title}
{m.blurb}
The longer how-tos live on the{' '} Project Zomboid wiki .