Haven't found a scripting solution for Interlude yet and maybe I never will
Code will always be more flexible than config files, but sometimes you gotta settle for what you have
In the meantime users would really benefit from theming their own score systems in
A score system is comprised of:
List of what judgements exist, their names and colors
Rules on hit windows and judgement assignment
Rules on point assignment
Rules for combo stuff
Future features:
In this same file you design HP rules too? Can't see a reason why these related things should be in two places if they are only going to be used in pairs
Possible "Score" output out of 1 or 10 million
Cases to cover in config:
Assign a value to hold head and tail separately
Assign a value to head + tail combined
Wife curve and osu rules for LN judgements will be hard coded cases
SC+ will get binned I think, literally only I used it and everyone else defaulted to osu!
Haven't found a scripting solution for Interlude yet and maybe I never will Code will always be more flexible than config files, but sometimes you gotta settle for what you have
In the meantime users would really benefit from theming their own score systems in
A score system is comprised of:
Future features:
Cases to cover in config:
Wife curve and osu rules for LN judgements will be hard coded cases SC+ will get binned I think, literally only I used it and everyone else defaulted to osu!