[x] Update QueueEntry.nextUserEntry getter to reflect this change, too
[x] Update wait time estimation to reflect this change, too
[x] Add some warnings about infinite queue signup having the chance of being interrupted
Here's the plan of action:
Add a frozenSubgroup property
Once a certain threshold (most likely 9 visits) has been reached, check for high priority visitors. (Probably as a simple function)
Check if frozenSubgroup is not null (if it isn't throw an error cause things went wrong really badly), and then copy the entire current processingGroup property into frozenSubgroup (change the internal counter back to zero on this step maybe)
Set processingGroup to null and proceed to prioritize the currently waiting people.
Once a multi-subgroup gets created, check if frozenSubgroup exists. If it does, copy it back into processingGroup, null out frozenSubgroup, and proceed execution
Here's the plan of action:
Add a frozenSubgroup property
Once a certain threshold (most likely 9 visits) has been reached, check for high priority visitors. (Probably as a simple function)
Check if frozenSubgroup is not null (if it isn't throw an error cause things went wrong really badly), and then copy the entire current processingGroup property into frozenSubgroup (change the internal counter back to zero on this step maybe)
Set processingGroup to null and proceed to prioritize the currently waiting people.
Once a multi-subgroup gets created, check if frozenSubgroup exists. If it does, copy it back into processingGroup, null out frozenSubgroup, and proceed execution