Regarding the actionload: Does every action a waiter performs count per single customer or per customergroup, e.g. if a group of size 5 orders is the corresponding actiontypeload of the waitstaff increased by 5 or by 1?
Additionally, do we even have to consider the type takeorder? Since it can maximally be the same amount as seated customers, and if a waiter can’t seat a customergroup he also can’t take their order
Every waiter action, including taking orders, is counted per individual customer (not per group), meaning a group of size 5 will increase the waiter’s TAKING ORDERS tick load by 5.
Yes, you must consider the TAKING ORDERS limit because the waitstaff assignment process only checks the waiter’s SEATING capacity, meaning a waiter could be assigned to seat a group but then be blocked from taking their order in the same tick if it exceeds their TAKING ORDERS limit
The first point is clean, thank you. But for the second point, could this ever happen? Because a weiter for example can seat 5 people and then take up to 5 Orders. After that He can maximally seat 5 more people and then again take up to 5 Orders. If his seatactionlimit is reached He can’t seat any customers anymore, and therefore not take anymore Orders. I can’t think of a way where the takingOrderLimit could be reached before the seatingLimit, thats my point why it theoretically could be omitted.
The TAKING ORDERS limit can indeed never be exceeded before the SEATING limit, making a separate capacity check for taking orders technically redundant.
Coupled Actions: A waiter can only take orders for a group they physically seat in that exact same tick. The TAKING ORDERS tick load for any waiter in a tick will always be less than or equal to their SEATING tick load.