Processing stations are where a single item is put in to be processed. For example the servery station, the oven and stove, and the cutting board. This page focuses on the developmental implementation, as well as listing compartible items with each component. Further information on how each system works as well as a visual walk through can be seen in the Station Inventory and Visualisation wiki page

UML Diagram

Sequence Diagram (Station Chopping & Station Cooking)

The following goes into the process of the user interacting with a chopping station. Note that, if the user interacts with a station which is already chopping, stopTimer() will be called at the end in ItemTimerComponent instead of startTimer() to stop the chopping.

The Station Cooking works the exact same way with the exact same process, with different files being used. Instead it utilizes StationCookingComponent instead of StationChoppingComponent, CookIngredientComponent instead of ChopIngredientComponent, and uses the "cookIngredient" and "stopCookingIngredient" as listeners/triggers.

Station Chopping Component

StationChoppingComponent allows for an item within a station to be chopped and the item itself updated to reflect this state. If an item is within a station that supports chopping like the cutting board and blender, then the methods chopIngredient() and stopChoppingIngredient() will be used when an item is placed in a station or taken out of a station. The structure of this component is quite basic and doesn't act as a brain at all and is simply called through event triggers within that station itself specifically the StationItemHandlerComponent.

List of ingredients which can be chopped:

all fresh produce (lettuce, bananana, strawberry, acai, cucumber, tomato)

chocolate

Station Cooking Component

StationCookingComponent is highly similar to StationChoppingComponent in that it updates items, however, it is specifically for stations which can cook items like the stove and the oven. Again, this component has 2 methods, cookIngredient() and stopCookingIngredient(), these are again called from within the StationItemHandlerComponent and called by triggers. Again, the structure of this component is intended to be basic, and simply acts upon what the item handler calls.

List of ingredients which can be cooked:

Steak

Station Submission Component

The submission component is the station where the player can submits an item which will be marked against the criteria given from the selected customer. This station used an animation to clearly identify where meals need to be submitted by the player. It's initialised to retrieve the ticketDetails class using the ServiceLocator so that it can be called to compare against the items submitted by the player.

Interactions with the station are handled in handleInteraction() by getting the first item in the players inventory and removing it (as well as it's display in the game). After this, it submits to an external function (submitMeal) which is where the item submitted by the player will be graded against the item that was wanted.

How the item that was wanted by the customer can be determined is further discussed in the ticket detail wiki page here.

Sequence Diagram