-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several Suggestions #98
Comments
I say +1 on adding tags to rewards so you can have different categories of rewards, it would be easier to handle if you have a lot of rewards |
@the-economancer Can you agree that your recommendations fall under the following labels?
With the above in mind it would seem adding a card to Trello for your idea of a library of tasks and rewards would ensure your suggestions are on "on the board". Once that card is up are you cool with this ticket being closed? |
sure |
@SlappyBag Can you please raise a Trello card for "Library of Habits/Dailys/Todos/Rewards anonymously crowd sourced from users' databases for the purpose of providing inspiration to other users." and reference this thread? |
I've been working on something similar to this, but have lacked the expertise and time (or rather, I haven't made it a priority) to get it quite this far. Given my track record with completing projects like these, I feel I can pass on my ideas, since I doubt I'll get around to them.
I've browsed through a few suggestions, and from what I've seen these are "original", but forgive me if there are any that I've missed.
First, a library of tasks and rewards, compiled from other users, that you could search through and add to your own "character sheet" (or whatever you're calling the interface) would be helpful in giving people ideas for what they want to do. This would also be very useful in standardizing tasks and rewards between users for analytic purposes. It would also help users determine the appropriate price for certain common rewards (or at least, categories of rewards), as this price could be calculated as an average of what other users have set (preferably those of a similar level and with a similar number of tasks earning coins).
In addition to this library, categorizing tasks and rewards would be beneficial for several purposes, including analysis (i'm an economics/math/data analysis geek, so obviously that's my first thought), and the possible implementation of a character classes. Categorization would most easily be accomplished in a user tagging system, and the library could be organized according to these either pre-defined, or user generated tags.
Speaking of classes...I noticed someone else had suggested this, and that it was being considered. Classes would obviously be related to types of tasks accomplished (fitness - warrior class, academic goals - a magic using type class, literary and musical tasks - bardic class, etc), these tasks being largely standardized via the library. Classes could then either be assigned based on what the user accomplishes, or alternatively, the user could select a class as a goal, and either earn extra experience for tasks associated with that class, or perhaps level the class separately (gaining standard character exp, as well as class exp). This has the advantage of making multi-classing a premium via tokens, if you want to go that route.
deep breath
Next up, and I'm sure this has been suggested somewhere, but an obvious feature would be quests based on to do's with dependencies. Users could create quests for themselves, or post challenges for others with reward values based on the difficulty, number of sub-tasks, and possibly adjusted for player levels. This would also permit "sponsored" quests, where companies/groups could post challenges/quests, and be featured somewhere on the character sheet or prominently on a quest page, for a fee of course.
I have a lot more ideas, many of them a bit more technical in nature. I'll wait for feedback on this tip-of-the-iceberg and to get more familiar with things before taking up too much more space.
The text was updated successfully, but these errors were encountered: