The latest info can be found in the displayed README.md at https://github.com/xiran-leternae/lusternia-secretary. Syntax and instructions will also be shown if you install the package and run the command FAIRYSEC or FS. Please feel free to ask any questions here.
As of this post, Fairy Secretary is in alpha. The triggers need to be manually enabled and logs read. This populates the log seen in FAIRYSEC REVIEW (the image of Tracked Activities above). Then a report can be generated with FAIRYSEC REPORT.
Triggers are already included for reading timequakes, designs, and library submissions (with stage coming soon). Domoths and other activities will require updating the triggers to match how your organisation members log them. If there is not a consistent format, there is an 'audit' trigger as a catch-all. This can also be used for anything else (org favours, donations, etc.) you wish to monitor. Then you can review and FAIRYSEC ADD or UPDATE items as needed.
Flat rewards can be changed easily. The code is organised for you to customise the tally functions (how rewards are calculated and individual activities are displayed) and the print functions (how the report is displayed) for your individual org.
The main branch of Fairy Secretary now gathers log entries for you from org and pointlogs, and trims entries outside of the given year. The new command is FAIRYSEC GATHER. I'm considering this pet project in beta and will be making adjustments to make it easier to configure for non-coders next.
Comments
Avatar made through Picrew
As of this post, Fairy Secretary is in alpha. The triggers need to be manually enabled and logs read. This populates the log seen in FAIRYSEC REVIEW (the image of Tracked Activities above). Then a report can be generated with FAIRYSEC REPORT.
Triggers are already included for reading timequakes, designs, and library submissions (with stage coming soon). Domoths and other activities will require updating the triggers to match how your organisation members log them. If there is not a consistent format, there is an 'audit' trigger as a catch-all. This can also be used for anything else (org favours, donations, etc.) you wish to monitor. Then you can review and FAIRYSEC ADD or UPDATE items as needed.
Flat rewards can be changed easily. The code is organised for you to customise the tally functions (how rewards are calculated and individual activities are displayed) and the print functions (how the report is displayed) for your individual org.
Avatar made through Picrew
I'm considering this pet project in beta and will be making adjustments to make it easier to configure for non-coders next.
Avatar made through Picrew