You can pretty much achieve this using just one rule with multiple actions, each of the actions can have a contraint to dictate which one of the actions will fire.
For exmple the rule could fire on Payment Processed with a Rule Constraint of Remaining Amount Equals 0 (if required).
Then below you could add the multiple duplicate actions, for example add an “Execute Print Job” action twice. (To add the same action multiple times you need to right-click on the list of available actions and select “Display All” - more info here)
The conditions could be like:
Execute Print Job
Contraint: '{TICKET TAG:TICKET TYPE}' == 'TAKEAWAY'
Print job: PrintBill
Copies: 2
Execute Print Job
Contraint: '{TICKET TAG:TICKET TYPE}' != 'TAKEAWAY'
Print job: PrintBill
Copies: 1
Note, you need to use the ' characters in the above conditions and also, remember that this compare operation is CaSE SenSITivE
So, The rule will be run evertime a payment is made, but these action conditions are helping us determine which of the actions should be run. If you have many actions you can fire them selectively as approriate using a variety of condition statements.