Ignored drop

[cupcup76]

tipcc_autocollect Ignored drop for 0.00008766 LTC ≈ $0.01 (tipcc_autocollect.py:724)

every drop, idk why

[QuartzWarrior]

Please send me your config

[cupcup76]

Please send me your config

"channel_id": 1,
"TARGET_AMOUNT": 0.0,
"SMART_DELAY": true,
"RANGE_DELAY": true,
"DELAY": [
1.0,
4.0
],
"BANNED_WORDS": [],
"MESSAGES": [
"tyy"
],
"WHITELIST": [],
"BLACKLIST": [],
"CHANNEL_WHITELIST": [],
"CHANNEL_BLACKLIST": [],
"IGNORE_USERS": [],
"WHITELIST_ON": false,
"BLACKLIST_ON": false,
"SEND_MESSAGE": true,
"CHANNEL_WHITELIST_ON": false,
"CHANNEL_BLACKLIST_ON": false,
"IGNORE_DROPS_UNDER": 0.0,
"IGNORE_TIME_UNDER": 1.0,
"IGNORE_THRESHOLDS": [],
"DISABLE_AIRDROP": false,
"DISABLE_TRIVIADROP": false,
"DISABLE_MATHDROP": false,
"DISABLE_PHRASEDROP": false,
"DISABLE_REDPACKET": false,
"DELAY_AIRDROP": true,
"DELAY_TRIVIADROP": true,
"DELAY_MATHDROP": true,
"DELAY_PHRASEDROP": true,
"DELAY_REDPACKET": false
}

[QuartzWarrior]

Was it a less than 1 second drop?

ima look through the code in the future, not sure whats up

[cupcup76]

Was it a less than 1 second drop?

ima look through the code in the future, not sure whats up

i try with 0 before its same
ok let me know

[QuartzWarrior]

im greatly unsure on what could be causing this. can you use the newer branch for now?

https://github.com/QuartzWarrior/Tip.cc-Autocollect/tree/feature-requests-stefffkec

[cupcup76]

nothing change xD maybe the screen can help you

[QuartzWarrior]

okay, replace this coed with the other code

original:

        if drop_ends_in < configuration["IGNORE_TIME_UNDER"] or drop_ends_in < configuration[droptype][
            "IGNORE_TIME_UNDER"]:
            logger.info(
                f"Ignored drop for {embed.description.split('**')[1]} {embed.description.split('**')[2].split(')')[0].replace(' (', '')}"
            )
            return

new:

        if drop_ends_in < configuration["IGNORE_TIME_UNDER"] or drop_ends_in < configuration[droptype][
            "IGNORE_TIME_UNDER"]:
            logger.info(f"{drop_ends_in } /// {embed.timestamp.timestamp()} /// {time()}")
            logger.info(
                f"Ignored drop for {embed.description.split('**')[1]} {embed.description.split('**')[2].split(')')[0].replace(' (', '')}"
            )
            return

and send me what it prints out

chances are tip.cc updated something with their timestamps

[cupcup76]

[QuartzWarrior]

Okay what drops are those? It's literally saying that it will end in -5 minutes ( the past ) I'll do some testing

[Unknownlord77]

Same problem as mine

[QuartzWarrior]

I'll have to do some testing

[Unknownlord77]

I'll have to do some testing

Lemme save you some time here

• Drop with time on them. For example ($airdrop all witchfire 5s)
• claims drops without any time limit. For example ($airdrop 10 ltc)

So far i only found this maybe it something to do with system instead. I ran it in a node which is quite secured and ran the same files in another node which is a bit less secured. The first one has a good firewall