Every RootMC jar uses YEAR.MONTH.BUILD — not classic semver. The number tells you when it was built: which development year, which calendar month, and which build in that month.
YEAR . MONTH . BUILD 1 . 7 . 0 │ │ └── build # within that month │ └────────── calendar month (1–12) └────────────────── development year index
Read left to right: which year of RootMC development, which month of the calendar, which published build in that month.
Counts RootMC development years. It stays fixed for the whole calendar year, then advances on 1 January.
1 — first year → 20262 — second year → 20273 — third year → 2028On 1 Jan 2027, versions roll to 2.1.0 (year 2, January, build reset).
The calendar month the build was made in (1–12).
1 — January7 — July8 — August12 — DecemberWhen the month changes, the middle digit advances and the build counter starts over for that month.
Sequential publish count inside that month. It climbs with each suite (or plugin) build: 0, 1, 2, …
It does not keep climbing across months. August starts a new count — so 1.8.123 is the 123rd build in August 2026, not “build 123 of all time.”
| Version | Means |
|---|---|
1.7.0 |
2026 · July · build 0 (scheme baseline) |
1.7.42 |
2026 · July · 42nd build that month |
1.8.123 |
2026 · August · 123rd build |
1.12.5 |
2026 · December · 5th build |
2.1.0 |
2027 · January · first builds of year 2 |
2.7.10 |
2027 · July · 10th build |
YEAR calendar first version of that year ──── ───────── ────────────────────────── 1 2026 1.1.0 (or later when adopted) 2 2027 2.1.0 on 1 Jan 2027 3 2028 3.1.0 on 1 Jan 2028 n 2025 + n n.1.0 on 1 Jan
Formula: calendar year = 2025 + YEAR (so YEAR 1 → 2026).
Root-Core still compares versions left-to-right numerically (same as dotted triples). A newer YEAR.MONTH.BUILD wins in the manifest.
1.8.1 > 1.7.999 — August beats any July build2.1.0 > 1.12.999 — next development year beats December of the prior year1.7.10 > 1.7.9 — later build in the same monthLive catalog: rootmc.net/plugins. Updater details: Plugin update & APIs.