You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d694783
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
SyntaxLauncher is a modern Minecraft launcher from SyntaxDevTeam, written primarily in Kotlin and developed incrementally from a minimal vanilla launcher into a modular launcher with premium authentication, isolated instances, mod loaders, Modrinth integration, modpacks and diagnostics.
4
4
5
-
The project has implemented a v0.2 Instance Manager, reached **v0.6 Modrinth development** and begun v0.7/v0.8 loader work. NeoForge processor execution is implemented and verified with an official Maven smoke test; Forge remains in preflight; Quilt Meta profile integration has been added. Microsoft app approval, v0.3 real-account acceptance and real Minecraft startup verification remain pending. The Kotlin/Compose launcher now connects the offline account, Mojang metadata, verified game preparation, automatic Java runtime installation, metadata-driven LaunchPlan and MinecraftProcessManager to an actual desktop Play workflow. A real clean-machine Minecraft launch is not yet verified.
5
+
The project has implemented a v0.2 Instance Manager, reached **v0.6 Modrinth development** and begun v0.7/v0.8 loader work. NeoForge processor execution is implemented and verified with an official Maven smoke test; Forge has a V2 installer adapter under CI validation; Quilt Meta profile integration has been added. Microsoft app approval, v0.3 real-account acceptance and real Minecraft startup verification remain pending. The Kotlin/Compose launcher now connects the offline account, Mojang metadata, verified game preparation, automatic Java runtime installation, metadata-driven LaunchPlan and MinecraftProcessManager to an actual desktop Play workflow. A real clean-machine Minecraft launch is not yet verified.
6
6
7
7
## Project philosophy
8
8
@@ -80,9 +80,16 @@ Fabric and Quilt startup were confirmed by the maintainer on 20 October 2026; lo
80
80
81
81
## Automatic GitHub Releases
82
82
83
+
**v0.7.0 publication blocker:** The 21 October 2026 version-change CI passed tests and Linux/Windows/macOS packaging, but GitHub rejected the release creation with HTTP 403 (`Resource not accessible by integration`). `launcherVersion=0.7.0` is in main, but the public Release is still absent. See [UPDATING.md](docs/UPDATING.md) for the optional write-authorized release token fix.
84
+
85
+
83
86
The sole product version is `launcherVersion` in [`gradle.properties`](gradle.properties), now `0.7.0`. Changing it to a higher **plain `X.Y.Z` version** (e.g. `0.7.0` → `0.8.0`) and pushing to `main` automatically publishes a normal GitHub Release `vX.Y.Z` after all Gradle/Python tests and Windows/Linux/macOS packaging succeed. **No GitHub pre-releases are published.** Ordinary code changes do not issue new releases. Matching plain-version manual tags remain supported. Each published release is eligible for the stable launcher updater; remaining gameplay and distribution acceptance limitations are recorded in the roadmap. See [publishing instructions](docs/UPDATING.md).
Forge modern installer V2 now shares a staged processor engine with NeoForge, while official installer discovery and SHA-1 verification remain loader-specific. Initial target: Minecraft 1.21.1 / Forge 52.1.20. The local mod manager recognizes basic `META-INF/mods.toml` identity and supports isolated Forge instances. Historical Forge V1 and older Java compatibility are not implemented. Forge stays unavailable as a public loader option until official installation and real game startup pass. See [v0.8 acceptance](docs/TESTING_V0.8.md).
91
+
92
+
## v0.7 — NeoForge (v0.7.0 version set; public Release not yet available)
86
93
87
94
A processor-backed NeoForge installer adapter is now connected to the existing
88
95
instance and launch pipeline. The desktop can discover compatible NeoForge Maven
@@ -96,7 +103,7 @@ and the existing Modrinth loader filter follows the selected NeoForge instance.
96
103
97
104
**Acceptance scope:** automated installer and official Maven smoke tests passed on
98
105
21 October 2026. The maintainer reported that testing is complete, but did not
99
-
provide an OS/version matrix or logs. This is a v0.7 development-line release,
106
+
provide an OS/version matrix or logs. This is a v0.7 development-line build,
100
107
not a certification of every NeoForge/Minecraft/mod combination. Cancellation,
101
108
recovery and broader loader compatibility remain tracked in the roadmap. Do not use this stage with your only
102
109
world save or assume filesystem staging is a security sandbox. See
@@ -126,7 +133,7 @@ touching installed files and explains unmatched local JARs. Managed updates now
126
133
SHA-256 provenance checks, a persistent backup of previous JARs and an explicit
127
134
last-update rollback action. Updates requiring missing/different dependencies are
128
135
deliberately blocked pending a full dependency reconciliation workflow.
129
-
Optional-dependency choice, richer conflicts and final UI/game acceptance remain open. Fabric and Quilt use the shared browsing/installing workflow. NeoForge has processor-backed installation; Forge's processor integration remains the v0.8 target. Local JAR import remains available. See
136
+
Optional-dependency choice, richer conflicts and final UI/game acceptance remain open. Fabric and Quilt use the shared browsing/installing workflow. NeoForge has processor-backed installation; Forge's common V2 processor integration is in v0.8 testing. Local JAR import remains available. See
130
137
[the v0.6 test plan](docs/TESTING_V0.6.md). Fabric and Quilt startup acceptance was confirmed by the maintainer on 20 October 2026; remaining mod-management and platform checks stay open.
131
138
132
139
## Current implementation
@@ -389,7 +396,7 @@ Loader support is intentionally staged:
Copy file name to clipboardExpand all lines: docs/ROADMAP.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -552,12 +552,12 @@ Goal: broaden loader support while preserving historical-version compatibility d
552
552
553
553
## Forge
554
554
555
-
-[ ] 🚧 IN PROGRESS — Discover official Forge Maven versions; processor installation and actual launch remain unimplemented.
556
-
-[ ] 🚧 IN PROGRESS — Inspect modern Forge installer V2 metadata/processor inputs in read-only preflight; no processor execution yet.
557
-
-[ ]Document exact supported Minecraft/Forge range if universal support is not practical.
558
-
-[ ]Launch Forge through common pipeline.
559
-
-[ ]Integrate Forge mod metadata handling.
560
-
-[ ]Integrate Modrinth Forge filtering.
555
+
-[x]Discover official Forge Maven versions with Minecraft compatibility filtering; Forge V2 processor adapter added, live acceptance pending.
556
+
-[ ] 🚧 IN PROGRESS — Verified SHA-1 Forge installer download and modern V2 profile/processor inspection implemented; synthetic and live CI pending.
557
+
-[ ]🚧 IN PROGRESS — Initial modern V2 target Minecraft 1.21.1 / Forge 52.1.20; legacy Forge V1 and historical Java combinations are intentionally unsupported until tested.
558
+
-[ ]🚧 IN PROGRESS — Forge uses shared ProcessorInstallerV2Engine and PreparedModLoaderProvider through common coordinator; actual Forge Minecraft boot acceptance remains open.
559
+
-[ ]🚧 IN PROGRESS — Read Forge META-INF/mods.toml IDs, names and versions and permit local mod operations under isolated Forge instances; complete TOML dependency semantics remain open.
560
+
-[ ]🚧 IN PROGRESS — Forge loader facet is supported in shared Modrinth adapter; installer/gameplay acceptance required before exposing Forge as supported in the desktop picker.
Copy file name to clipboardExpand all lines: docs/TESTING_V0.8.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,16 @@
1
-
# v0.8 — Quilt and Forge acceptance
1
+
# v0.8 — Forge and Quilt acceptance
2
+
3
+
## Forge v0.8 development (21 October 2026)
4
+
5
+
-[x] Official Forge Maven version discovery adapter and strict modern Forge V2 SHA-1 installer download are implemented.
6
+
-[ ] Forge profile read-only inspection and checksum/corruption/legacy V1 regressions — code added, CI verification pending.
7
+
-[ ] Shared V2 processor engine works with NeoForge/Forge; official Forge 1.21.1/52.1.20 live installation smoke and launch acceptance pending.
8
+
-[ ] Forge `META-INF/mods.toml` identity import, scoped installation, disable/remove and Modrinth operations — code added, CI acceptance pending.
9
+
-[ ] Historical Minecraft/Forge version matrix and required Java/argument behavior documented and tested.
10
+
-[ ] Desktop Forge selection exposed only after successful representative install, mod and graphical game startup.
11
+
-[ ] Portable builds, launcher/regression tests and actual native-platform interaction acceptance passed.
12
+
13
+
Forge V1 (legacy) is deliberately rejected; this phase never claims universal historical Forge support. Quilt Meta integration and maintainer-confirmed startup remain valid independently.
2
14
3
15
## Maintainer confirmation — 20 October 2026
4
16
@@ -9,7 +21,7 @@ The maintainer stated in the project chat that Fabric and Quilt tests had been p
9
21
-[x] Local `quilt.mod.json` identity/version/dependency parsing — deterministic regression passes.
10
22
-[ ] Quilt mod import/Modrinth installation/gameplay and loader switching acceptance.
11
23
-[ ] Quilt native Windows/Linux/macOS and representative version matrix recorded.
12
-
-[ ]Forge and NeoForge processor execution/generated artifacts implemented and tested.
24
+
-[ ]NeoForge generated artifact installation validated in v0.7; Forge V2 processor adapter implemented and awaits official live/game test.
Copy file name to clipboardExpand all lines: docs/WORKLOG.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,40 @@ Every code/build/documentation/CI task must add an entry according to `AGENTS.md
8
8
9
9
---
10
10
11
+
## 2026-10-21 — Begin Forge V2 milestone and diagnose v0.7.0 publication
12
+
13
+
**Milestone:** v0.8 — Forge/Quilt
14
+
**Author/Agent:** GPT-6
15
+
**Status:** Partial — implementation and CI verification ongoing
16
+
17
+
### Completed
18
+
- Implemented SHA-1-verified official Forge V2 installer preflight, strict checksums, cache, client processor inspection and fail-closed legacy handling.
19
+
- Reused the existing NeoForge V2 child-Java processor engine via `ProcessorInstallerV2Engine`, wired Forge into the generic `PreparedModLoaderProvider` and shared desktop dependencies.
20
+
- Added mocked checksum/legacy/target-version regressions and a CI-gated official Forge 1.21.1/52.1.20 installer smoke test.
21
+
- Added Forge mods.toml local identity parsing and expanded isolated local/Modrinth mod operations to Forge and NeoForge while preserving Fabric/Quilt behavior.
22
+
- Fixed a stale `manifest` reference uncovered by CI; addressed pre-existing Fabric/Quilt-only restrictions uncovered by the new Forge tests.
23
+
- Diagnosed v0.7.0 release CI: verification and all-platform packaging passed, but GitHub Release creation returned HTTP 403; added optional repository release-token fallback.
24
+
25
+
### Changed files
26
+
-`launcher-core/src/main/kotlin/pl/syntaxdevteam/syntaxlauncher/core/loader/ForgeInstallerPreflight.kt`, `NeoForgeInstallerEngine.kt`, `InstallerLoaderDiscovery.kt`, plus Forge regressions.
27
+
-`launcher-core/src/main/kotlin/pl/syntaxdevteam/syntaxlauncher/core/mods/LocalModManager.kt`, `ModrinthInstaller.kt` and mod tests.
- Write-authorized release token/policy required to publish v0.7.0 as an ordinary GitHub Release. The product SemVer remains 0.7.0 until v0.8 is accepted.
41
+
- Forge processor Java executes as third-party code; isolated working directory is not OS sandboxing.
42
+
43
+
---
44
+
11
45
## 2026-10-21 — Confirm v0.7 CI and publish version 0.7.0
0 commit comments