SamWibatt
commented
4 years ago Similar thing with names so can make #defines or enums out of trigger names, etc, and handlers for those too?
The reason to use an external spreadsheet is that multiple maps might use the same names / types but the ripping tools wouldn't discover them in the same order, or alphabetize them the same way if they weren't all present, or whatever.
Like how you map features in machine learning feature vectors
Currently have an enum for things like nogo, slow, etc.
But this should be configurable per game
What about a csv spreadsheet that lists an area type string, index, then other details about it (possibly even the name of a handler to call) and this all gets converted into code by some other little tool?