So here's the difference in workload for us between states with state-only activity, and states with multi-state activity
- Create Customer fliter [click]
- Add all tournaments with State ID = ?? [click]
The end for the whole year
States with multi state leagues
- Create custom filter [CLICK]
- Add tournaments individually over the course of the year [CLICK]
The end . . . sort of sucks because it's a manual effort over the course of the year, far more likely to forget to include events.
Both versions simply pull from the points in our WPPR Results table in our database, so even the multi-state league work on our end isn't too much of a pain in the butt.
The SCS calculation just blindly adds all points it sees in the filter, and it's done.
This solution of manually assigning points based on some external criteria that our build script doesn't handle makes for a messy messy situation, and a ton of more work for Shepherd.
In theory it's a solid solution, but in practice there's no easy way for us to get this implemented.