-
Notifications
You must be signed in to change notification settings - Fork 688
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
Predictions: 'Stealth Mode' betting #33
Comments
…p_points, bet top_poins -= random.uniform(1, 5) - stealth_mode #33
If you want you can try this feature on this branch 😄 |
I'm on it.. will report back! |
I can't see should I add it manually? |
closed it by mistake.. I can't see should I add it manually? |
Yup, I forgot to add in the example file. |
got it. running it now.. i'll report back |
so far I haven't experienced a prediction.. but for some reason the branch is running soooo delayed.. no errors, but I have 10 live streamers and there are 'gaps' of no script activity at all for like 15-20 minutes.. so strange. the main branch doesn't behave like this. I've restarted the script twice and same issue.. |
…p_points, bet top_poins -= random.uniform(1, 5) - stealth_mode Tkd-Alex#33
Would be nice to have:
An option to bet 1 point less than the current highest bet. I'll explain:
The prediction box, shows the username of the highest bet from OptionA and OptionB. So, in a small channel, where sometimes everyone knows each other.. If we show up as the highest bet all the time... and don't even talk.. we would raise suspicion. Plus, since we don't show up in the user-list.. they would freak out even more..!
So my suggestion is.. that at the moment we're about to place our bet to Option2 for example.... check the amount of the highest bet from Option2 and place the bet just 1 point less of it.. and continue to be 'hidden' from chat.
Of course, that value will continue to obey and be within:
bet_settings=BetSettings(percentage=5,max_points=50000)
if it's an option in run.py .. .we could call it
stealth_mode=True
;o)
Originally posted by @testdev123456 in #29 (comment)
The text was updated successfully, but these errors were encountered: