Fixed-scope Minecraft mod diagnostic
Voxy VR Backport Feasibility Sprint
A $100 public-safe diagnostic for the open Voxy 1.20.1 Vivecraft/shader backport request. This is a paid first-pass feasibility offer, not a promise of a complete backport. No third-party comment or PR was posted.
Diagnostic flow
1. Pin requested target
1.20.1, Fabric/Forge expectation, Vivecraft version, shader stack, Sodium/Iris versions.
1.20.1, Fabric/Forge expectation, Vivecraft version, shader stack, Sodium/Iris versions.
2. Compare current repo
Current dev branch targets 26.1.2, Fabric Loader 0.18.6, Fabric API 0.148.0, Iris, Sodium, and Vivecraft entries.
Current dev branch targets 26.1.2, Fabric Loader 0.18.6, Fabric API 0.148.0, Iris, Sodium, and Vivecraft entries.
3. Identify blockers
Minecraft API drift, Fabric API drift, Sodium/Iris compatibility, VR render pass behavior, shader version assumptions, and Forge gap.
Minecraft API drift, Fabric API drift, Sodium/Iris compatibility, VR render pass behavior, shader version assumptions, and Forge gap.
4. Handoff
First-test checklist, milestone plan, and exact next scope for a buyer-approved prototype.
First-test checklist, milestone plan, and exact next scope for a buyer-approved prototype.
Concrete Deliverable
- Version matrix comparing requested 1.20.1 Fabric/Forge target with current public dev branch targets.
- Dependency risk map for Fabric Loader, Loom, Fabric API, Sodium, Iris, Vivecraft, shaders, and optional Nvidium.
- Backport blocker list with the first files and build settings to inspect after payment.
- VR/shader test checklist: build, launch, flat-screen render, VR no-shader render, VR shader render, and performance capture.
- Milestone recommendation that separates a $100 diagnostic from any larger prototype/backport contract.
Exact Acceptance Before Payment
The buyer must paste this before any paid work starts:
I accept the Voxy VR Backport Feasibility Sprint fixed-scope terms at $100. I understand work starts only after seller-owned external payment proof exists; I will provide only public or buyer-authorized non-sensitive version targets, modpack context, and reproduction details; the deliverable is limited to a public-safe backport feasibility report, dependency/version matrix, Vivecraft/Iris/Sodium risk map, first-test checklist, and recommended milestone plan; and a working 1.20.1 build, Forge port, private modpack debugging, paid mod jars, production server access, guaranteed upstream acceptance, performance guarantee, ongoing support, or extra revisions are not included unless separately agreed before payment.
Voxy Vivecraft 1.20.1 Backport Feasibility
Repo: MCRcortex/voxy. Issue state: Open. Payment signal: requester says they would pay/reimburse a reasonable cost and asks to name a price. Related issue: 1.20.1 version request.
I saw this Voxy 1.20.1 Vivecraft/shader backport request and can offer a narrow first-pass feasibility sprint for $100. I would not promise a full backport up front. The deliverable would be a public-safe version/dependency matrix, Vivecraft/Iris/Sodium risk map, first-test checklist, and milestone plan based on the current public dev branch and the requested 1.20.1 VR target. I would not need private modpack files, paid jars, server access, account credentials, or private recordings; any upstream comment or PR would require explicit approval.
Public-safe source snippet
Requester wants a 1.20.1 Voxy backport that works with Vivecraft and shaders, says they would pay/reimburse a reasonable cost, and links follow-up VR performance comparison material. Related issue #375 says maintainers have treated 1.20.1 as not planned.
Prepared notes excerpt
## Voxy VR Backport Feasibility Notes Source issue: https://github.com/MCRcortex/voxy/issues/519 Related duplicate/history: https://github.com/MCRcortex/voxy/issues/375 Repo: https://github.com/MCRcortex/voxy ### Observed current dev branch facts - Default branch: `dev`. - Current `gradle.properties` targets `minecraft_version=26.1.2`. - Fabric loader target is `loader_version=0.18.6`. - Loom target is `loom_version=1.15-SNAPSHOT`. - Fabric API target is `fabric_api_version=0.148.0+26.1.2`. - Current dependency surface includes Sodium, Iris, Lithium, Vivecraft, Flashback, Chunky, and optional Nvidium entries. - Current Vivecraft entry is `vivecraft_version=26.1.1-1.3.7-b2-fabric`. - Shader sources include GLSL 330, 450, and 460 paths. ### Why this should be a feasibility sprint first The buyer asks for a 1.20.1 Fabric/Forge path that works with Vivecraft, shaders, and distant LODs. The public repo currently targets a newer Fabric stack, includes VR render-pass logic, and has shader/GPU code paths that are likely version-sensitive. A direct "promise a full backport" offer would be too broad and risky without maintainer acceptance and a reproducible test matrix. ### Diagnostic deliverable 1. Version matrix: current dev target versus requested 1.20.1 target. 2. Dependency matrix: Fabric loader, Loom, Fabric API, Sodium, Iris, Vivecraft, and shader requirements. 3. Backport blockers: Minecraft API changes, Fabric loader/API changes, Sodium/Iris compatibility, VR render pass behavior, shader version/GPU assumptions, and Forge feasibility. 4. First local test plan: build-only, launch-only, flat-screen render, VR no-shader render, VR shader render, and performance capture. 5. Recommended milestone plan: diagnostic, Fabric-only prototype, VR render validation, shader validation, packaging, and optional Forge research. ### Non-goals - No private modpack files. - No paid mod jars. - No account credentials. - No guaranteed upstream merge. - No claim that a working 1.20.1 build exists before paid diagnostic work and buyer-provided acceptance details.
Money And Posting Boundary
| Signal | Counted as money? |
|---|---|
| This page, CSV, prepared notes, issue lead, draft response, search metadata, or IndexNow result | No. Counts $0. |
| The requester says they may pay, asks a question, or links a video | No. Requires exact accepted scope and external payment proof. |
| External payment posted, released, payable, or cleared after delivery proof and any platform acceptance | Yes, count only verified net amount after fees/refunds. |
No public GitHub comments, pull requests, direct messages, payment requests, private modpack access, or server changes were made by this script. External sending requires explicit approval.