Track something more useful than percentages

[Sunlis]

Track in-game units for activities rather than as percentage of arbitrary playtime. Possible examples are amounts of prep materials transported, amount of credits earned, (maybe) time spent patrolling, merits earned undermining. The goal is to be able to estimate the total resources in each of these areas available to us each day/week.

This might be best done by watching every channel (especially 3public-orders and reports) and conditioning people to post their prep/fort updates with a consistent format.

[Sunlis]

The messages we get in other channels don't really come in one set format. It's random crap like:

• 28,487 @ madngela
• MADNGELA +200, now at 27,787. CHNUMAR 122835. HIP 116045 61869.

Or even worse, it's conversational.

Bob: How are we doing with Cubeo? Alice: 1200/5500

[Sunlis]

A few commands could solve this problem:

• !update <system> <partial>/<total>
  • This would update the known progress of system without attributing any new prep/fort to anyone.
• !prep <system> <added> [<partial>[/<total>]]
  • Record that the sending player brought added materials to system. If provided, use partial and total to update known progress (as in !update), but it probably shouldn't try to incrementally update totals, and should instead rely on explicit updates.
  • Is total even relevant for prep?
• !fort <system> <amount> [<partial>/<total>]
  • Just like !prep, but for forts.
• !check <system>
  • Return the known value for system, if any. Preferably show the name of the person who last updated it as well (subtle conditioning :P)
• !cycle
  • Clears all prep/fort numbers. Meant for use when PP cycles. Should probably gate this on a hard-coded list of "admins".

[Sunlis]

Another example of a report that is actually reasonably parseable.

Madngela +500: 31,797. Chnumar: 124,155. HIP 116045: 61,879

[Sunlis]

Ignoring the tricky parsing bit, the relevant information that needs to be stored is:

• System name
• CMDR
• Action type (prepare, fortify, undermine, nominate?)
• Action units (hours, merits, materials, kills, nominations)
• Action quantity
• Action "cap"
  • The total number of preps/forts/merits needed to "finish" the system

Might make sense to introduce a concept of which cycle we're on, so that the !cycle command could just increment that. Each cycle table would contain a row for every action event.

[Sunlis]

Do we care about tracking non-PP stuff like bounty hunting?

[Dinusty]

a bounty hunting or reporting feature would be nice