If the orders go 'unit: day:' instead of 'day: unit:' (e.g. '856: 10:'
instead of '10: 856:', you could toss the orders through a simple sort
and get output grouped by unit/day. Another tactic I use at work to
differentiate error message output on programs is to use the special
characters such as '***', '###", '@@@', ')))', '>>>', etc. This way,
you get stuff like:
856: 10: >>> move 324
856: 10: [@] Will spend 7 days traveling to North Atnos .
1933: 12: >>> study 102 1
1933: 12: [%] Study combat at a cost of 2 gold per day for one day.
1933: 13: (%) Finished studying combat.
1933: 14: >>> work 7
1933: 14: [=] Will work at unskilled labor for seven days.
856: 16: (@) Arrival at North Atnos .
This way you can look for a single character indicating a type of command.
Just an idea. Note if you sort this message, you will get a clump ordered
by unit and then by day...
John Morrow - Varian