9bd86e85b5
* Initial Commit
* Not quite all was staged, apparently.
* Multiline no longer necessary
* For my convenience...
* Forgot an important little tidbit in routes.tsx
* This updated, apparently.
* And now hell breaks loose
* First batch
* Second Batch
* Third batch (Unit Tests)
* Improvised shotgun ammo is gone; Vibebots are refactored
* UpdatePath sweeps in our fulp_modules/_maps folder
* I can't bring myself to do it.
* Map stuff
* Didn't mean to leave this uncommented
* I carpet-bombed them with Find-Replace. Let's see what linters think
* I sure do hope this is comprehensive and doesn't break other things
* This may take a while
* Next Round
* Hopefully the last batch before getting on with actual fixes
* Telescreens
* :/
* Stragglers
* Helio Emergency Shuttle; NearStation adjustments.
* Only one more commit for greenchecks... Shuttle code be dammed.
* Pff, the file was missing
* Same treatment as the other map files.
* Missed a comma :P
* BZ chambers for Xenobiology
* Odd. Most of these got done earlier. Not sure why this one wasn't.
* Mapping sweep. I didn't adjust C_tags in Theia. Another time.
* The balloon alerts overlap
* I hate TGU I hate TGU
* I meant to say "I hate TG" on the last one. Freudian slip.
* Fix Fix
* Nanite research cost rebalance
* TGU-Update: Step 0
* Yeah I figured it'd do this.
* I accidentally undid this
* Failed to catch this one
* I don't trust hundredths not to break or be broken somewhere.
* Little air alarm tweaks
* Ports #1228
* Stuff I missed
* Silly
* TGU so nice we're going to make it thrice
* Yarn
* Should be all? Fixes cult stun too.
* Thermomachine layers
* Free square spellcheck to rerun tests and see if it's consistent
* All credit goes to QLA for reminding me to actually do this
* Update to e40becd742
* github folder
Hypnagogic
What is this?
This folder will hold a set of cached versions of hypnagogic, our icon cutter. We autodownload the tagged version from github on build.
How is it used?
The cutter works off 2 inputs. A file, typically a png, and a toml config file in the format {filename}.{other input extension}.toml
The input resource is transformed by the cutter following a set of rules set out in the .toml file. Typically these are very basic. We have a set of templates in repo stored in cutter_templates/ and most uses just copy from them.
You can find more information about it in its repository, found here, the examples subfolder in particular contains fully detailed explanations of all the config values for the different types of cutting (there are more then one)
How does it work?
Anytime you build the game, CBT will check and see if any of the files that the cutter cares about have been modified If they have been, the cutter will perform a full runthrough, and compile all inputs down into typically dmis
These dmis can then be committed, and badabing badaboom we have autocut sprites.
If you want to change the cutter version we have a set of config values in dependancies.sh that control it.