Releases: CodeW4VE/w4ve
Release list
w4ve 0.1.1
A published jar now beats the mc range somebody typed.
The catalog said ShapeBoard was >=1.21 <1.22 long after it started shipping a 26.2 build, so install refused a jar that exists. When a release explicitly names your server's Minecraft version, that fact wins over the declared range, in install and in doctor alike. This matters as the rest of the mods get ported to 26.2, since they all ship one jar per Minecraft in a single release.
Also: every flag has help text now. The command reference is generated from it, and nine flags were showing up blank.
curl -LO https://github.com/CodeW4VE/w4ve/releases/download/v0.1.1/w4ve.py
chmod +x w4ve.py && sudo mv w4ve.py /usr/local/bin/w4vew4ve 0.1.0
First release of the command line.
One file, standard library only, Python 3.8 or newer. Copy it to a server and it works: no pip, no virtualenv.
curl -LO https://github.com/CodeW4VE/w4ve/releases/download/v0.1.0/w4ve.py
chmod +x w4ve.py && sudo mv w4ve.py /usr/local/bin/w4veCommands: init adopt list search info profiles install update remove sync status doctor, all with -n for a dry run.
What it already gets right, because it was built against real servers and not against a wish list:
adoptreads thefabric.mod.jsoninside each jar instead of guessing from the file name, so a file calledCarpet Extra.jaris still recognised.- It knows the MCDR layout, where
mods/hangs offserver/andplugins/off the root. - Updates are the ones that suit your Minecraft version. It will not offer you Carpet for 26.2 on a 1.21 server.
- Conflicts carry versions on both sides, so a healthy pair passes and
updatestops the one that breaks: carpet-tis 1.82 with lithium 0.13 is refused, with the reason. - Downloaded files are readable by the user the game actually runs as inside a container.