ResourceDing

tag 6cc02c4f24a8252962831101fb0e2ad82eec0a10 v1.2.3
Author:    Ironship <oleg.szew@outlook.com>
Date:    Fri Sep 4 10:39:20 2026 +0200

1.2.3

commit 60da098ba820fda49eda0b3c4927c3310a2115a2
Author: Ironship <oleg.szew@outlook.com>
Date:   Fri Sep 4 10:39:20 2026 +0200

    1.2.3: Classic Era is on 1.15.9

    The Classic manifest named 11507, which is 1.15.7, and a client that has moved
    on reads that as an addon it should warn about. The number lives in the
    repository now, so it is corrected here rather than in a build argument.

commit 7123742649242639057f80b134c2c41b7ab90ab1
Author: Ironship <oleg.szew@outlook.com>
Date:   Fri Sep 4 10:31:04 2026 +0200

    One manifest per game, so the packager can read the game version

    The CurseForge packager builds a tagged commit and takes the game version from
    the manifest, which the single manifest here could not carry: it named one
    interface number and the build rewrote it per game. That is how a Retail number
    reached the Classic artifacts -- nothing in the repository disagreed with it.

    The interface numbers now live in the repository, one manifest per game under
    the suffixes the client looks for, and the build takes the one for the game it
    is building. .pkgmeta gives the packager the same exclusions the build already
    applies, so both routes ship the same files.