-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Campaign incorrectly labeled as unlinked #309
Comments
This is not in the plans anywhere in the future. Regarding the issue itself, please perform a clean reconnect. To do this: • Disconnect the accounts. For Twitch, use the Connections page, find the affected game and click on "Disconnect". For the affected game, go to it's designated account control panel, and try finding an account disconnect option there. Disconnecting at least one side is necessary, disconnecting both is recommended. If you're not able to disconnect both sides, you may run into re-linking errors later - just keep that in mind. Essentially, re-logging into each account first, before attempting to re-link, ensures fresh authorization tokens and no hidden errors will result in the process staying in an invalid state. Please give it a try and let me know how it went. |
A clean reconnect is not an option in this case, as Battle.net states that a reconnect is not available until 7 days after a disconnect, and at that point it would be too late. I could try it after this campaign, but it may not be necessary, as most previous campaigns have not exhibited this problem. For now, it seems the only other option is to hope it works manually in my browser at 4am. This example aside, I've also had several cases in the last couple years where I've wanted to mine drops for games that I don't yet own or play, but expect to in the future. It's nice to have them all currently sitting in my inventory, awaiting the connection of an account that will eventually exist. You could argue that I should have created accounts for these games from the start, but that seems like an arbitrary prerequisite when it's not required by Twitch. |
Incorrect. This is a requirement for Twitch, and how drops have always worked. If you claim a drop with an unlinked account, the drop is no longer valid. There have been numerous posts and PSAs on the internet about this: https://www.reddit.com/r/animalroyale/comments/qgghvg/psa_for_twitch_drops_link_your_account_before_you/ Some games have an external page that will allow you to refresh your connection after the fact to get re-linking/re-acquisition done, while others don't. |
Ok. I can't speak to the implementation of individual games, especially if they used the old drop system. It's clear that Twitch intended to support linking accounts after claiming drops and built their UI with that in mind, but perhaps it's a regularly broken feature. They do mention this:
It probably would be smart of them to surface this time limit for unlinked drops instead of hiding it in the FAQ. |
This cooldown is only for new/other twitch accounts, not if you unlink-relink the same account [source]. But in the case of the Mercy drop, it won't help. The drop is broken for some/all? [source] |
I see, good to know, assuming this forum post is correct.
Yeah, this is not surprising. It seems likely that the required connection was just misconfigured when the campaign was created. IMO it remains the case that it would be useful to be able to mine this drop ahead of them fixing the problem with the connection, which may or may not happen by the end of the campaign. |
This will never ever be added. Please see the project goals: https://github.com/DevilXD/TwitchDropsMiner#project-goals Regarding doing the clean reconnect, you should be able to just re-link without waiting. If you really fear it's going to put you in the 7 days long cooldown state, you can still try following the clean reconnect steps list, but without doing the disconnect step. Re-logging during the linking process is the most important part, as the most common cause for broken inter-account connections, is having a stale session token. |
As mentioned above, there is no point in reconnecting, as the problem is with the campaign. The connection between my account and Battle.net remains perfectly fine. Twitch confirmed this to me in an email yesterday. Anyway, it's your project, so your choice. Since the functionality is supported by Twitch and quite useful, I implemented it myself. I appreciate that your code is clean and easy to work with. |
There is currently a campaign for Overwatch 2 that appears disconnected on Twitch:
No amount of reconnecting or refreshing fixes this. However, the connection already exists, as evidenced not only by Battle.net but by a different campaign for the same game:
While this seems like a bug in the Twitch campaign listing, it still allows the drop to be obtained manually. Unfortunately, the miner filters it out:
Ideally there would be a way to allow the miner to ignore the connection status, since it apparently can't be fully trusted.
The text was updated successfully, but these errors were encountered: