Releases: geode-sdk/cli
Releases · geode-sdk/cli
CLI v1.0.6
Changelog
- Spritesheet
.plist
and font.fnt
exports are now sorted, so identical texture inputs should always produce identical outputs
CLI v1.0.5
This minor release brings some new options and helpers.
Changelog
geode new
no longer uses the oldcom.developer.name
format for mod IDs- New
--shut-up
option forgeode package resources
- SDK now uses the
GEODE_SDK
environment variable for location
CLI v1.0.4
Changelog
- Add default SDK path on Windows (fixes
geode sdk install
command not working)
CLI v1.0.3
Changelog
- Changes to
geode sdk
commands to reflect how the nightly / stable system actually works - New command
geode sdk install-binaries
for automatically installing pre-built binaries - Remove references to Geode installer as the installer is currently not available
- Fix bugs with config
CLI v1.0.2
Changelog
- Add
geode sdk version
command for querying installed SDK version - Fix
geode new
command specifying invalid target Geode version
CLI v1.0.1
New features
- Automatically migrates config if you have used old cli
- Added
geode config setup
for setting up a profile if you have manually installed Geode
CLI v1.0.0
Geode CLI
Changes from v0.2.5
- Rewritten from the ground up.
Installation
- Download the executable for your respective platform, and add it to the system's path (instructions for Windows).
- Verify it works by running
geode
from the command like (You may need to restart your command line after adding the executable to your path).
Usage
- Run
geode help
for instructions. If you're a Geode mod developer, you will most likely not be using the CLI manually, but through the Geode CMake.
CLI v0.2.5
Changelog
New Features
- Added
launch
command for launching GD - Added
edit
command for modifying.geode
packages
Changes
- Improved
config
command - Other minor changes & improvements
Geode CLI v0.2.4
Changelog
- Now up-to-date with mod.json once again, using the exact target loader version instead of an enigmatic number
- Various other fixes & improvements
Version number bump was intentional; we just never made a release for v0.2.3