Labels Milestones

New Issue

Add an "Achievements" feature #4

Open

opened 2 years ago by tdeeb · 0 comments

tdeeb commented 2 years ago (Migrated from github.com)

Owner

This could be a way to further engage viewers, especially those who prefer to watch instead of play.

The idea is to have a simple streamer-defined list of achievements that viewers can work towards. Some examples:

• "Contribute 1000 inputs"
• "Type 500 total messages in chat"
• "Earn 10,000 credits"
• "Follow the channel"
• "Subscribe to the channel for 4 consecutive months"

Achievements may or may not have credit rewards, but the bot should at least notify everyone by sending a message in chat when a viewer satisfied an achievement.

These can be defined in an Achievements.txt file in the TRBot Data folder. Viewers can use a separate command to see their achievement progress (Ex. "!achievements" to see the achievements list, "!acprogress NumeroUno" to see their progress on a specific achievement). The user info command can also show the list of achievements they have accomplished.

The system should start out simple and be easily extensible.

This could be a way to further engage viewers, especially those who prefer to watch instead of play. The idea is to have a simple streamer-defined list of achievements that viewers can work towards. Some examples: - "Contribute 1000 inputs" - "Type 500 total messages in chat" - "Earn 10,000 credits" - "Follow the channel" - "Subscribe to the channel for 4 consecutive months" Achievements may or may not have credit rewards, but the bot should at least notify everyone by sending a message in chat when a viewer satisfied an achievement. These can be defined in an **Achievements.txt** file in the TRBot Data folder. Viewers can use a separate command to see their achievement progress (Ex. "!achievements" to see the achievements list, "!acprogress NumeroUno" to see their progress on a specific achievement). The user info command can also show the list of achievements they have accomplished. The system should start out simple and be easily extensible.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

NET6Upgrade

ReadExternalEvents

ReworkInvalidInputCombos

SyntaxTutorialUpdate

develop

master

1.0

1.5

1.6

1.7

1.7.1

1.8

2.0

2.1

2.1.1

2.2

2.2.1

2.3

2.3.1

2.4.0

2.5.0

2.5.1

Labels

Apply labels

Clear labels

bug
Something isn't working CI
Tasks regarding Codeberg Continuous Integration critical
Critical bug or issue that needs to be addressed as soon as possible documentation
Concerns documentation duplicate
This issue or pull request already exists enhancement
New feature or request good first issue
Good for newcomers help wanted
Extra attention is needed high priority
Higher priority issues that aren't critical but take precedence over other issues invalid
This doesn't seem right low priority
Low Priority Issues meta on hold
Will be revisited at a later date ongoing
Concerns work that persists over longer periods of time question
Further information is requested refactor
Primarily involves heavy code refactoring service
New service or a problem specific to one wontfix
This will not be worked on

No Label bug CI critical documentation duplicate enhancement good first issue help wanted high priority invalid low priority meta on hold ongoing question refactor service wontfix

Milestone

Set milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Assign users

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview

Loading…

Cancel

Save

There is no content yet.