I’m definitely going to test out your plugin.
This discussion makes me thing perhaps we should revamp how the multi-axis tags work instead.
For ex. instead of a specific device, have the tags themselves be: #axis-vibration, #axis-twist, #axis-stroke, etc…
It’s more specific than just “more than 1 axis” and makes the same generic device expectations.
We can also still make the specific devices optional to include.
Or perhaps we just need a standard definition of Device vs Axis vs Device Type
like:
Device: Handy 2 pro (name)
Axis: Stroke (list of axis)
Type: Stroker (Generic device category)
idk about implementation though.
I don’t want to setup complicated names for tags. If a simple name doesn’t suffice with a descriptor, we’ll end up with mile-long tags that take up the whole screen. It would be best to have a system of simple names and a dedicated post to map out purpose like we (partially) have here. Obviously it could be expanded to not just the required tags.
I don’t see how paid scripts differ in this context. The requirement was added because of earlier discussion and I agreed.