mpopp / netherbot Goto Github PK

Current viewers should not be a parameter. The service can fetch it directly in the init method call.

For now, as the bot runs locally, implement a "reinitialize" command which can be issued by mods. The command sets all viewers to offline, resets the session points and sets all viewers in chat to online again.

Bot should check for stream go-live and reset session points for viewers.

Bet command should add the possibility to bet on the outcome of a game.
Command syntax should be the following: !bet [win|lose] [points]

If the viewer bet correct, the points should be multiplied with a factor configurable in properties file and the amount should be added to the viewers wallet.
If the viewer bet incorrect, the points should be lost (and therefore subtracted form the viewers wallet).

The bot mustn't respond with a message to a !bet command, for staying within the 21 messages per 30 seconds restriction of twitch chat.

Reset session points of winner.

Don't remove the winner from the raffle pool (since session points are reset, chances for a double win are low anyways).

Blacklist should be a db table with the following columns:

• id: id of the db row
• nick: the blacklisted viewer
• feature: the feature for which the viewer is blacklisted

There can be more than one entry per viewer!

Current Feature values should be "points"

Currently the factor and starting points for that service are just set to some random values.

Calibrate the level curve with values that make actually sense and provide viewers with a smooth leveling experience (i.e. you shouldn't reach level 60 in the first streaming session right away).

Tasks:

• Define level progression speed
• Set values to match the progression definition

We want viewers to level up.
Level is determined by total points.
Needed points to get to next level is determined by this function:
f(1) = 1;
f(x) = f(x-1) * 1.2

Put the function into a strategy to be flexible there!

total point gain is determined by viewer "value":
lurker: 1p / time
follower: 2p / time
subscriber 5p / time
Put that one into a separate object too... makes the whole point gain more configurable.

session point gain is determined by total point gain rules + factor which scales by viewer level.

Only people active in chat should be considered in raffles. This should prevent bots gathering a high total win chance for the bot's owner.

However, totalpoints and session points should still be collected for the viewers that are NOT active in chat (so that they have their high chance if they were lurking for a long time).

Create an account and get an oauth token for it. Share between all devs.

only keep a template in the git repo.
The instance that's actually used for startup should be kept on the local machine somewhere else.

Use a centralized datastore instead of hibernate.

Preferably nosql to avoid schema redefinition, we just don't want to bother with schemas now.