The Wildcats interface displays a different availability message for an available player and an unavailable player.
This excerpt runs inside an existing method with Boolean input isAvailable. The assignment stores a message; no display API is needed to understand the choice.
If the underlying C# feature is unfamiliar, use the lesson below while reading this example.
string message;
if (isAvailable)
{
message = "Ready";
}
else
{
message = "Unavailable";
}Read whether the selected player is available
When true, store Ready as the message
Otherwise, store Unavailable as the message
Continue after the selected assignmentUse these words to follow one execution before drawing it. Keep the same order and the same alternatives as the source; simplify the wording without adding work that the code does not perform.
Player available?.Set message to Ready and Set message to Unavailable on separate branches.true and the route to Unavailable false. Edit the connection labels rather than adding true and false as action nodes.Compare this reference with the diagram you built in Violet. Layout may differ; the source meaning, labels, and relevant connections should agree.
Trace isAvailable false. Only the Unavailable assignment runs. The true assignment is visible in the diagram but skipped during that execution.