Yeah I have an idea of how it could work, but without knowing database schema's and other cache/processing functionality behind the scenes I wouldn't know where to start to help out. Technically I would just say adding a grouping table where you can have a parent group (dictated by a mod) and a you can assign a group to a snap. Considering that snaps span different tribes this could get a little messy.
If it can be made to work... wooo, if not... well no real loss.
Exactly. High five.
MegaSnap, Snap Group, whatever they call it, it would be a clean solution if they can work out the details.
Definitely a complex solution when it comes to backend integration, but it might be an effective one if we hash out the details.
Yeah I have an idea of how it could work, but without knowing database schema's and other cache/processing functionality behind the scenes I wouldn't know where to start to help out. Technically I would just say adding a grouping table where you can have a parent group (dictated by a mod) and a you can assign a group to a snap. Considering that snaps span different tribes this could get a little messy.
If it can be made to work... wooo, if not... well no real loss.
C'mon... say it... say "Great idea, now code it!"
You know you want to.