[FEATURE REQUESTS]

[jamestaylor141]

1. Hello! I have a problem. I'm claiming redpackets (envelopes) without a problem, until someone comes to a very great idea of detecting scripters by doing "$redpacket 1 witchfire 1s" like 10 times in a row, which all get claimed by the script. Then I get banned from the server. Is there a way to bypass this, while still claiming some bigger envelopes? Suggestion: In the current settings, you can ignore anything under $x.xx, make it automatically ignore anything without value. This should only be for the envelopes. The script should still claim no-value currencies for airdrops, phrasedrops and anything else.

2. Is it possible to do multiaccounting? (using tokens.txt)

3. Following up on 2, the script could have a setting of switching between the envelopes. First envelope is claimed by the first account, second envelope by the second account etc. This would bypass people saying "QuartzWarrior claimed the last 10 envelopes, ban him!"

4. The script could have a randomized CPM. I used 2 accounts and for all phrasedrops they were always first and second to say the phrase, which got me banned on both accounts. So the user could set a minimum and maximum CPM, and the script will randomize it.

5. Thanks for reading!

[QuartzWarrior]

1. I do have the feature 'Earnings Threshold: Checks if earnings are above a certain amount before claiming.' (IGNORE_DROPS_UNDER), but you could also use IGNORE_THRESHOLDS, which is in format value:chance_in_percent which has a chance to ignore any drop under that value.
2. Thats only in my premium golang version right now, I might add it in the future though.
3. Thats a valid suggestion, might add it to the premium version.
4. okay yeah, thats a good one. u could do a random delay, which could separate them a bit. Might implement this.

[jamestaylor141]

I don't have money to buy the premium version, but where can I find it?

…

: 1. I do have the feature 'Earnings Threshold: Checks if earnings are above a certain amount before claiming.' (IGNORE_DROPS_UNDER), but you could also use IGNORE_THRESHOLDS, which is in format value:chance_in_percent which has a chance to ignore any drop under that value. 2. Thats only in my premium golang version right now, I might add it in the future though. 3. Thats a valid suggestion, might add it to the premium version. 4. okay yeah, thats a good one. u could do a random delay, which could separate them a bit. Might implement this. — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIOHG53RNTGMSNEV5JIPISTZ3MUCZAVCNFSM6AAAAABP3Z66CCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZHAYTGOBQGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jamestaylor141]

Also redpackets don't work anymore, idk why

[jamestaylor141]

Another suggestion: You have the "whitelist servers where the bot should work". But can you also do "whitelist channels only"? Cause people create a #botcheck channel and just create a $0.0000001 airdrop, which gets picked up by the bot

[QuartzWarrior]

I don't have money to buy the premium version, but where can I find it?

https://shop.quartzwarrior.xyz/product/tipcc-go

Also redpackets don't work anymore, idk why

ill look into it

Another suggestion: You have the "whitelist servers where the bot should work". But can you also do "whitelist channels only"? Cause people create a #botcheck channel and just create a $0.0000001 airdrop, which gets picked up by the bot

alright, yeah, so add channel whitelist as well. alright.

[jamestaylor141]

I tested out a bit and realized that the script not claiming envelopes occurs when you have smart delay turned on. Hope that helps!

[QuartzWarrior]

yes, this is because envelopes are a 1 person claim. Smart delay waits a quarter of the time until the drop ends. so, if someone claims it before the wait time ends, it obviously won't claim it.

[jamestaylor141]

No no I meant it doesn't even try to claim it when there is no time limit. Maybe the smart delay could be only for airdrops/phrasedrops/mathdrops

[QuartzWarrior]

there is always a time limit... I could add a feature where you can customize where the smart delay is used tho

[QuartzWarrior]

try the update, lmk

[jamestaylor141]

Thanks for the update! But there is an error. After the setup (on the first run), it's all good. On the second run (close and reopen the script), the script just opens and instantly closes (I do "py tipcc_autocollect.py" and another cmd just opens closes)