That is correct.
No. It will not reflect in the Kitchen. Not yet anyway… working on that part, but need more features for Tasks to make that work. I am sure @emre will give us the tools we need - I have asked for them already, specifically because of Voids.
Yes. It doesn’t really care about Tickets per-say. The setup shown is only concerned with Orders. So if you add something to an existing Ticket, the added Order(s) get printed.
Yes. Again, it has nothing to do with Tickets, nor the Status/State of the Ticket. It operates solely on the Order-level.
Keep in mind, the setup shown is only 1 way to do this. It could be Ticket-based if you want. But I don’t really see the point, when it comes to using the Task Printer as a Kitchen Display mechanism. Kitchens are concerned with Orders, not entire Tickets, correct?
This could be used with Order Groups as well, so if you have “Set Meals” that have, say, Meat, Potatoes, Veggies, where each is an actual Order-line, you could group them, so they appear on a single Task Card instead of printing individually. It is just a matter of changing when and what you print, and the Template(s) you use.
If you want to use the Task Printer for another purpose - one which prints entire Tickets, you could do that as well. But the Ticket Lister Widget is more suited to that - it was designed for that purpose. People figured out some “clever hacks” to use as a Kitchen Display using States, etc., but the setup is really rather complex, as compared to using Task Printer. The Kitchen Display using Task Printer setup is really dead-simple by comparison.
I chose to configure this to print Food Orders individually, and Beverages combined (the setup steps shown do not do this). There are many other possibilities…