local.properties.example

# Machine-local settings — the TEMPLATE, and this file is committed on purpose.
#
#   cp local.properties.example local.properties     # then edit; that copy is gitignored
#
# So the pair reads oddly on first sight and is meant to: `local.properties.example` is tracked and
# carries no real paths, `local.properties` beside it is ignored and carries yours.
#
# Keys are FREE-FORM: every line in local.properties is loaded onto each project, and a build script
# reads one by name. Nothing enumerates them, so this file EXPLAINS rather than declares — the build
# neither reads it nor refuses a key missing from it. Write a new setting down here anyway; one nobody
# documented is one the next person finds by reading a build script.
#
# Forward slashes on Windows too: a backslash is an escape in a .properties file, so `C:\Users\...`
# silently loses its separators. Spaces in a path need no quoting.
#
# The examples below stay COMMENTED. An unedited copy then reads as unset and says so, where a live
# placeholder would have Gradle create `C:/Users/you/...` and report a successful deploy into it.

# ── PrismLauncher instances ─────────────────────────────────────────────────────────────────────
#
# The instance DIRECTORY — the one containing `instance.cfg` and `.minecraft`, not the `mods/` folder
# inside it. `deploySingleJars` appends `.minecraft/mods` itself, which keeps `logs/latest.log` and
# `crash-reports/` reachable from the same setting when a failure has to be read back.
#
# ONE LINE PER INSTANCE, and as many as you like:
#
#     prismInstance.<label> = <instance dir>
#
# The label after the dot is what `prodSmoke -PcgTargets=<label>` drives it by, and what the capture
# files are named. Nothing enumerates the labels, so adding a target is a line here rather than an
# edit to build.gradle.kts. A target is a version AND a loader and they fail differently -- Forge
# 1.20.1 runs SRG members, NeoForge 1.20.4 runs official names, Fabric runs intermediary, 1.7.10 is a
# different engine again -- so give each its own line.
#
# The four `prismLauncher<X>Dir` keys this replaced are still read when no `prismInstance.` key is
# present, so an older copy of this file keeps working.
#
# `deploySingleJars` copies BOTH CrystalGraphics' and CrystalGUI's jars -- CrystalGUI does not run
# without CrystalGraphics beside it -- and deletes the previous pair first, so a loader switch cannot
# leave a jar built for the other one behind. Unset is fine: that instance is skipped and the task
# says so.

# The launcher binary itself, which `prodSmoke` drives. Required by that task and nothing else.
#prismLauncherExe=C:/Users/you/AppData/Local/Programs/PrismLauncher/prismlauncher.exe

#prismInstance.1710         = C:/Users/you/AppData/Roaming/PrismLauncher/instances/Crystal 1710
#prismInstance.1201forge    = C:/Users/you/AppData/Roaming/PrismLauncher/instances/Crystal 1201 Forge
#prismInstance.1204neoforge = C:/Users/you/AppData/Roaming/PrismLauncher/instances/Crystal 1204 NeoForge
#prismInstance.1201fabric   = C:/Users/you/AppData/Roaming/PrismLauncher/instances/Crystal 1201 Fabric

# Which of those get `crystalgraphics-joml-<version>.jar` beside the mod, as a comma-separated list
# of labels.
#
# Minecraft ships JOML from 1.19.3 on. BELOW that the companion is required, because CrystalGraphics'
# public API names `org.joml` and always will; ABOVE it a second copy is a split package and Forge
# dies in module resolution before it writes a log line. The label cannot imply this, so it is stated
# -- anything pre-1.19.3, 1.7.10 and 1.17.1 alike, belongs here.
#prismInstanceJoml = 1710