Tagging shops?

[Ghost-chu]

Since #703 issue, I've been thinking about how to make it better for users to batch process a large number of stores.
Initially, my idea was to create a group and add all the stores that needed to be processed to the group, but it seemed too cumbersome - players always have to maintain a lot of groups.

Inspired by Twitter, maybe we can tag the store.
This way, we can have the flexibility to list all the stores we need to deal with just by tagging them.

• Looking at a shop
• /qs tag #alpha and target shop will be tagged with #alpha tag. (but in per-player scope).
• Refactor a little bit about command system, so player can use tag: arguments in everywhere in command for reference the stores like:
  /qs price tag:#period-promotion 150
  • Such parameters can be added repeatedly so that users can refer to multiple tags at once:
    /qs price tag:#period-promotion tag:#holiday-promotion 150
  • Depending on the order in which they are declared, users can also perform simple operations, like this
    /qs price tag:+#period-promotion tag:+#holiday-promotion tag:-#no-promotion-at-september
    In the exmaple above, all shops that tagged #period-promotion and #holiday-promotion will be joined the pending queue, but the shops that tagged with #no-promotion-at-september will be excluded from pending queue.
• The colon arguments are independent of the value passing system, which means they can be added anywhere in the command:
  • /qs tag:#period-promotion price 150
  • /qs price 150 tag:#period-promotion
  • /qs price tag:#period-promotion 150
  • /qs price tag:#period-promotion 150 tag:#hoilday-promotion

This is probably the easiest way I can think of for batch processing, all other methods seem to increase the user's learning costs significantly.

Any suggestions for improvement are appreciated!