Use the row that matches the edition
Most bad Verity Mod advice starts with a shortcut: a title says "latest," a video says
"updated," or a reposted file name looks familiar. That shortcut skips the most important
question, which is whether the player is on Java, Bedrock, MCPE, or a modpack profile. A
Java JAR cannot be imported into Bedrock. A Bedrock MCADDON does not belong in a Java mods
folder. A ZIP can be a modpack instead of the standalone file. A copied beta URL can keep
circulating after the maintainer removes the active version record.
The source map keeps those differences visible. Each row names the host, owner, Project ID,
current or historical record, package type, local guide page, and caution note. If you write
a community answer, cite the row and tell the reader why it matches their edition. If you
maintain a spreadsheet or wiki, use the CSV and keep the local guide URL beside the official
project URL. If you run a bot or route checker, use the JSON and check the generated timestamp
before showing a verdict.
What the CSV is for
The CSV version is intentionally flat. It is easier to paste into a Google Sheet, a Discord
moderation note, a wiki draft, or a content calendar. Columns such as projectId,
recordId, packageType, and localGuideUrl are designed
for quick comparison. If a user says "I downloaded Verity" without more detail, filter by
package type first, then match the owner and record number.
What the JSON is for
The JSON version preserves the same route fields with a schema URL and source snapshot links.
It is better for scripts, bots, and automated site checks because each record has a stable
routeId. The JSON also carries the platform-counter summary: 13,829,693
displayed downloads across the four tracked CurseForge project pages, or 14,167,449
when the official Modrinth Verity JE project counter is added. Those are platform counters,
not unique players.
Maintenance rules for reuse
Treat the generated timestamp as the freshness boundary. If a maintainer changes the current
file, removes a version, updates a Bedrock build row, or changes a project description, the
source snapshots should be checked first and this map should be rebuilt from those facts. Do
not manually edit a single CSV cell in a public copy and call it current. That creates a forked
reference where the page, JSON, CSV, and update feed disagree. A good community note should
keep three links together: the official project or file record, the matching local guide page,
and this normalized map. That gives players a path back to the maintainer page while still
explaining why a similarly named result is Java-only, Bedrock-only, stale, or a separate
modpack. If the question is about malware, privacy, payment, or account security, use this
table only for source identity and run a separate security review.
What not to do with it
Do not use this source map as permission to mirror files, reupload jars, sell download packs,
or claim that a metadata match proves a file is safe. It is a routing and citation asset. A
player still needs to open the maintainer page, check the edition, install the correct loader
or addon type, and follow the official setup notes. If a page hides the final URL behind a
short-link chain, downloader, password archive, or APK installer, treat that as a separate
source-risk problem.