Poly Mod Loader 1.0.0

Minecraft: 26.1, 26.1.1, 26.1.2, 26.2

Highlights

• Poly Mod Loader 1.0.0, the first stable release: Fabric, Forge, NeoForge and Quilt mods are all fully supported on Minecraft 26.1, 26.1.2 and 26.2, each checked with popular real mods on the client, the game test server, the dedicated server and installed profiles.
• NeoForge mods now run by default with NeoForge's own loader, no option needed; the files NeoForge needs are downloaded on the first start.
• Fabric, Forge and Quilt mods can be mixed in one game. NeoForge mods do not run in the same game as Fabric or Quilt mods yet: they are left out with the reason (POLY-COMPAT-216).
• For mod developers: a Poly Mod that declares "poly": ">=0.1.0-alpha <0.2.0" does not load on 1.0.0, because that range ends below 1.0.0. Declare ">=1.0.0 <2.0.0", as the mod template, the examples and the SDK documentation now do.

주요 변경

• 첫 정식 버전 Poly 모드 로더 1.0.0: Minecraft 26.1, 26.1.2, 26.2에서 Fabric, Forge, NeoForge, Quilt 모드를 모두 완전히 지원합니다. 로더마다 실제 인기 모드로 클라이언트, 게임 테스트 서버, 전용 서버, 설치한 프로필에서 확인했습니다.
• 이제 NeoForge 모드는 옵션 없이 기본으로 NeoForge 자신의 로더로 실행됩니다. NeoForge에 필요한 파일은 처음 시작할 때 받습니다.
• Fabric, Forge, Quilt 모드는 한 게임에 섞어 쓸 수 있습니다. NeoForge 모드는 아직 Fabric·Quilt 모드와 한 게임에서 실행되지 않으며, 이때는 이유와 함께 빠집니다(POLY-COMPAT-216).
• 모드 개발자 안내: "poly": ">=0.1.0-alpha <0.2.0"을 선언한 Poly 모드는 1.0.0에서 로드되지 않습니다. 이 범위가 1.0.0 아래에서 끝나기 때문입니다. 모드 템플릿, 예제, SDK 문서처럼 ">=1.0.0 <2.0.0"으로 바꿔 주세요.

Full changes

NeoForge (ADR-0026, adopted)

• NeoForge mods are fully supported on Minecraft 26.1, 26.1.2 and 26.2 (docs/COMPATIBILITY.md "NeoForge 완전 지원 점검"): the real-mod corpus's NeoForge mods play a saved world on the client, save it and quit (corpusNeoForgeClient: 54 mods on 26.2, 55 on 26.1.2, 36 on 26.1), run on the game test server and the dedicated server, and the installed launcher profile and server run them. Not supported yet: NeoForge mods in the same game as Fabric or Quilt mods (POLY-COMPAT-216).
• NeoForge mods run by default with NeoForge's own loader (FML 11) on Minecraft 26.1 (NeoForge 26.1.0.19-beta), 26.1.1 (26.1.1.15-beta), 26.1.2 (26.1.2.122) and 26.2 (26.2.0.93). NeoForge has only beta builds for 26.1 and 26.1.1; Poly Mod Loader uses the last one. -Dpoly.neoforge=off keeps the old behaviour (NeoForge mods diagnosed and left out).
• The real-mod corpus's NeoForge mods run on the game test server (corpusNeoForge) and start the dedicated server up to the EULA check (corpusNeoForgeServer) on 26.1, 26.1.2 and 26.2, with the same game layer as NeoForge's own installation. Mods that stop a NeoForge server under NeoForge's own launcher too (Sodium and the mods that use its classes, ImmediatelyFast's 26.2 build, Zoomify; on 26.1 three builds for later NeoForge releases) are left out of the server runs; each was checked against NeoForge's own server.
• An installed server runs NeoForge mods from mods/ on the game test server and the dedicated server (serverInstallTest); the launch jar's Java agent opens java.lang.invoke to NeoForge's loader.
• A NeoForge server now has the libraries NeoForge's own server class path has (LWJGL's core and tinyfd on 26.1.x, tinyfd on 26.2), so ImmediatelyFast's 26.1 build starts on a server as under NeoForge.
• NeoForge's ModList.getModFileById and isLoaded answer for Poly Mods too (ADR-0025); new code POLY-COMPAT-218 when NeoForge's ModList is not the checked code.
• The log line is now Loaded mods per loader: N Poly, N Fabric, N Quilt, N Forge, N NeoForge, and the title screen has a "NeoForge mods" line (English and Korean), drawn above NeoForge's own branding. The lines are added to the list NeoForge's branding is drawn from (BrandingControl.getBrandings), so mods that draw the title screen's branding themselves, such as FancyMenu, show them too. POLY-COMPAT-219 is retired before any release used it.
• Sodium's NeoForge jar (an FML library with an early service, the mod nested in it) now loads as under NeoForge: FML loads it as an early service and the nested mod from its JarJar, also for mods outside the mods folder. Before, FML saw it as a library only, and Iris, Sodium Extra and Reese's Sodium Options found Sodium missing on the client. Regression scenario neoForgeEarlyService.
• A NeoForge launch could hang while mods were constructed in parallel: the game class loader asked FML's plugin class loader under its own class loading lock, while that loader asked the game class loader under its lock. The game class loader now asks its parent and fallbacks without holding its lock.
• The NeoForge requirements check (POLY-COMPAT-217) takes nested jars from JarJar's META-INF/jarjar/metadata.json, as FML does, so Lambda Dynamic Lights' nested API (in META-INF/jars/) counts as installed.
• When no Fabric or Quilt mod runs (NeoForge or Forge mods only, or only Poly Mods), game and mod code no longer see Fabric Loader's and Quilt Loader's API, which Poly Mod Loader carries for its bridges; under NeoForge and Forge they are not there either. Yumi, in Lambda Dynamic Lights, took the NeoForge client for a Fabric one, could not find Lambda Dynamic Lights' default configuration, and the client stopped while starting (ADR-0026, decision 27). New test mod neoforge-environment-probe, which corpusNeoForge uses to make the same lookup headless.
• Build: the 26.1 NeoForge client runs leave out Lambda Dynamic Lights 4.11.2+26.1.2, whose client code needs a NeoForge class that NeoForge 26.1.0.19-beta does not have (real NeoForge stops there too); it still runs on the 26.1 server.
• NeoForge mods still do not run together with Fabric or Quilt mods (POLY-COMPAT-216); ADR-0026 gives the reasons.
• New tasks: neoForgeWorldTest (every supported version), corpusNeoForgeServer, startupBenchmarkNeoForge, tickBenchmarkNeoForge, and the window tasks neoForgeClient, corpusNeoForgeClient, launcherProfileNeoForgeTest. New test mod neoforge-client-session. corpusNeoForgeRun is replaced by corpusNeoForge.

Install: on Windows run PolyModLoader-1.0.0.exe; elsewhere run PolyModLoader-1.0.0.jar (Java 17 or newer).
설치: Windows는 PolyModLoader-1.0.0.exe, 그 밖에는 PolyModLoader-1.0.0.jar(Java 17 이상)를 실행합니다.
NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG OR MICROSOFT.