We actually encountered an issue this year as we have a group now with over 20 tickets which tried to seat. They wish to be seated on two seperate rows, something the system disallowed.
Solution: New ruleset
- Once the group has seated on a row, that row is "taken" and any other seat seated on that row has to be next to a seat already taken by this group.
- The amount of rows that can be taken is the the rounded up integer of
n/10
Sounds like hell of an algoritm to write, but whatever