electronicboy / byof Goto Github PK

The initial setup process needs to be documented, bog standard fork + clone, plus an opinionated "best setup" guide (allowing easy updating of these scripts), (git init ., git remote...)

Initial start (iirc):
edit scripts/init.sh to set fork name (edit scripts/init.sh)

git submodule update --init
./concrete up
./concrete p

At that point, you should have an environment suitable for working

Would be nice to add support for patches of the MojangAPI module too. I solved it this way but not sure if that's the best tbh.

This project needs a more fitting name, the main script was renamed to concrete based upon a joke in the community as being a "better paper fork" (and being more generic), while I do like this given the joke, it would be interesting to see something more fitting and maybe not a "borrowed joke"