Editorial process and AI disclosure

This page explains how the guides on this site are made, who checks them, and how AI is involved. Google recommends disclosing substantive AI use, and beyond that it seems reasonable that anyone taking technical advice should know where it came from.

AI disclosure, stated plainly

Being more specific about what that means in practice: AI is used to gather what has been written about a topic, to identify which failure modes come up repeatedly, and to produce a first draft of structure and prose. It is not used to decide what is true.

The distinction matters because language models are confident about things that are wrong, and modding is full of advice that was correct three years ago. A model trained on the open web will happily tell you to install Forge for 1.21, or that OptiFine is the best performance mod, because that is what most of the internet says. Both are out of date. Catching that is the editing job, and it is why the draft is a starting point rather than a product.

How a guide actually gets made

The process is the same for every page and it is deliberately unglamorous.

• A real question is identified — something people are actually searching for, usually a failure they have just hit rather than a topic that sounds interesting.
• Existing coverage is reviewed to find what everyone else leaves out. The gaps are usually the same: no explanation of why a step matters, and no acknowledgement that the mods folder does not exist yet.
• Primary sources are checked. Mojang's documentation, the Fabric and NeoForge project sites, mod authors' own pages, and the Java specification for anything about runtimes.
• A draft is produced, with AI assistance, following that research.
• The draft is edited by hand: claims verified, out-of-date advice removed, structure reshaped, anything the model asserted without support cut.
• Sources are linked so you can check the reasoning rather than take it on trust.
• The page is published with a real date, and that date is updated only when the content genuinely changes.

The data tables are not written at all

Several pages carry tables of how many mods exist for each Minecraft version and each loader. Those numbers are not researched, estimated or copied — they are read directly from Modrinth’s public API by a scheduled job that runs daily, and each table prints the date it last ran.

This is deliberate. Figures like these are exactly the kind of thing that quietly rots: written once, correct for a few months, then wrong forever while still being cited. Reading them from the source means the table is accurate on the day you look at it rather than on the day it was written.

It also means the analysis built on them stays honest. The observation that older Minecraft versions carry deeper mod libraries than the current one is a genuinely useful thing to know, and it is only useful if the numbers underneath it are current.

What gets fact-checked, and against what

Not every sentence needs a source, but specific categories always get verified:

• Version requirements — which Java version each Minecraft release needs, checked against Mojang's documentation and the Java specification.
• Loader behaviour — checked against the Fabric, NeoForge and Forge project documentation rather than community summaries of it.
• Mod capabilities and licences — checked on the mod's own Modrinth or CurseForge page, which is also where every download link points.
• Anything about Mojang's rules — checked against the Minecraft Usage Guidelines directly, since a great deal of secondhand summary of those is wrong.
• Numbers of any kind — either sourced from an API or attributed to where they came from.

Corrections policy

When something here is wrong, it gets fixed on the page rather than quietly deleted, and the last-updated date changes so you can tell the page has moved.

For substantive corrections — where the previous advice would have led someone the wrong way rather than merely being imprecise — the change is noted on the page itself. There is no interest in pretending a guide was always right.

Reports go to sukielovesupport@gmail.com and are the single most useful thing a reader can send.

Review schedule

Modding content decays faster than most technical writing, because it depends on four moving pieces — Minecraft, the loaders, individual mods and Java — that update on unrelated schedules.

Pages are reviewed at least annually, and sooner when something specific changes: a new Minecraft release, a loader fork, a major mod being abandoned. A page reviewed and found still accurate does not get its date bumped, because a changed date that reflects no change is a small lie that makes every other date less trustworthy.

Independence

Server hosts linked from this site are chosen on whether they handle modded Minecraft well. No host has paid for a listing or for wording, and any affiliate relationship is disclosed on the page carrying the link.

Mod recommendations are based on download data and on what the mod actually does. No mod author has any commercial relationship with this site, and the ranked tables come from Modrinth’s numbers rather than from opinion.

Guest posts and paid link placements are declined. If that ever changes it will be stated here first, in plain language, rather than discovered.

What this site does not claim to be

It is one person writing about a hobby, with the help of tools, checking things properly. It is not an official source, it has no relationship with Mojang or Microsoft, and it does not have inside information about anything.

Where something is uncertain or depends on your specific setup, the pages say so. Confident-sounding advice that turns out to be wrong is worse than an honest “check your mod’s own page for this”, and you will find a fair amount of the latter here. See also the about page.