In this document I'm referring to Tasker terms as <tasker_term> to prevent any confusion.
There are 2 types of rulesets:
- actions, such as:
- set ringvolume based on media volume
- GamingMode
- ...
- the (poorly-named) profiles, such as:
- Home
- Work
- Meeting
- Outdoor
- Sleep
- set "constants" (datatype doesn't exist in Tasker afaik but it makes development a lot easier)
- set default values
- check & load config json
- generate vars based on config, fallback to default if necessary
- check & load profile_rulesets json
- generate action & trigger vars for rulesets
- enable based on trigger/action vars
- enable which are required by trigger vars
- enable deamon(s)