Bug: Tries to delete MEE6 Messages + Thread Messages (+ slows PC) about undiscord HOT 9 OPEN

@karcfa can you try the patch in #526 and see if that fixes it? You could comment your feedback in there.

Hi, it started deleting again, thanks
i added this line at this position:

I also recommend to set the delay before switching to next page to 5 seconds or something because the default 30 second would be too long and would also apply when the bot didnt remove anything on current page (cause they were all skipped)
(Not sure)

from undiscord.

I believe @ckcr4lyf may have a found a solution is #520 for the Archived threads, as well as #526 maybe having a line from @CactusHamster on the MEE6/bot/slash command error messages

from undiscord.

For Error deleting message (Thread is archived). Will increment offset so we don't search this in the next page... , this is just a WARN message, and it will skip it.

Previously this would hard error and reach an unusable state, but I fixed it in #518

from undiscord.

That is to say, the expected behavior is already "correct" for archived messages, i.e. "skipped". (A warning is printed so that the user knows some stuff was not deleted).

from undiscord.

That is to say, the expected behavior is already "correct" for archived messages, i.e. "skipped". (A warning is printed so that the user knows some stuff was not deleted).

But it got stuck for 16 hours on that, it was 4 years of data but it was just stuck on archived messages, using the fix in #520 fixed this and I got it done though fortunately, as well as putting in the line of code from #526 fixed the MEE6 bot issues, I would recommend putting these in main :)

from undiscord.

I would recommend putting these in main :)

Let's see when the author has time to review it. Till then I guess you'll need to use your fork

from undiscord.

same here. it tries to remove DISBOARD (/bump) and MEEE(?) messages and it slows down the operation a lot. It also wont remove many legit messages by the way, but it did in the past.

from undiscord.

@karcfa can you try the patch in #526 and see if that fixes it? You could comment your feedback in there.

from undiscord.

Fixed partially in #629 :)

from undiscord.