Home Esplora Aiuto
Accedi
mutantstandard
/
build
mirror da https://github.com/mutantstandard/build
Segui 2
Vota 0
Forka 0
File Problemi 0 Wiki

Mutant Standard Build Files

Ramo (Branch): main
Rami (Branch) Tag
build
ZIP TAR.GZ
Caius Nocturne b0f12c2c34 Bundle improvements and fixes 5 mesi fa
input d30c572d00 Added smilies 5 mesi fa
manifest b0f12c2c34 Bundle improvements and fixes 5 mesi fa
texts 3b2eaf2668 Credits update 6 mesi fa
.gitattributes d75bc70a5a Initial commit 6 anni fa
.gitignore c246d4009b Initial Commit - Doing a reset on my end 1 anno fa
README.md c246d4009b Initial Commit - Doing a reset on my end 1 anno fa
out_all_slice.sh 0c02750584 Script fixes 1 anno fa
out_bundle_test.sh b0f12c2c34 Bundle improvements and fixes 5 mesi fa
out_coherence_test.sh eafb744eeb Smiley fixes 1 anno fa
out_final_full.sh 5b046673ce 2024.06 sponsored emoji, version bump 6 mesi fa
out_final_slice.sh 5b046673ce 2024.06 sponsored emoji, version bump 6 mesi fa
readme.md a8ff078c38 Mutant Standard 2020.02, improved scripts 4 anni fa
translating.md 89f218e3ec Rounded the hearts a bit, more name consistency 1 anno fa

README.md

Mutant Standard Build Files

This repository contains all of the files required to build a custom Mutant Standard package using Orxporter.

These files are for anyone who is techy enough and is interested in seeing what a large Orxporter project looks like, or wants to create their own Mutant Standard packages in a format that's not offered by the website.

If you're a regular user, I highly suggest you go to Mutant Standard's download page and download a package that's best for you.

License

Everything in this repository is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Requirements

There shouldn't be any significant difficulties in using this on various major OSes, and both Orxporter and Forc have been written to be cross-platform. From one time to another these tools have been used on both macOS and Linux.

Images

  • Download the latest version of Orxporter.
  • Place the Orxporter folder in the root of this directory.
  • Start running export commands from the root directory of this repo.

If you want some ideas on how to make your own scripts and commands, in the root of this repo there are .command executable scripts, all of which are the ones I use in everyday tests and for the final export of each release.

The Orxporter repo has full documentation on how to create your own build commands and understand manifest files.

Translating?

Check out the translation doc for some guidance.

Locations of things

  • /input is where the input emoji SVGs are.
  • /manifest is where all the manifest files are, including license metadata.
  • /Orxporter is where Orxporter should go.
  • /Forc is where Forc should go.
  • /out is where the exported emoji go (I recommend putting the output of any task in a sub-folder so you can make multiple types of exports without conflicts).

Fonts

(I have decided to stop developing font technology on my end, but it's still easy to compile a font using Orxporter and Forc.)

  • Download the latest version of Orxporter and put it in this folder (as described above), export like this:
./Orxporter/orxport.py -m manifest/out.orx -i ../input -q 32x32 -o out/font_sources -F svg,png-32,png-64,png-128 -t 4 -f %f/%u
  • Download the latest version of Forc.
  • Place Forc in the Forc directory.
  • Then build fonts with Forc like this...
./Forc/Forc.py -m manifest/font/manifest.json -a manifest/font/aliases.json -i out/font_sources -o out/fonts -F [formats] --afsc

See Forc's help (-h flag) to see what formats you can export to. Forc also has a readme and documentation.

(the --afsc build flag is super-important if you're building a SVG font with Mutant Standard's images, do not remove it.)