Aurora

Aurora

352k Downloads

[Bug] Can't list any LFG group if Aurora is enabled (and no BNet authenticator) on Retail 10.2.7

Heregellas opened this issue ยท 3 comments

commented

Is there an existing issue for this?

  • I have searched the existing issues

Game Client

Retail 10.2.7

Current Behavior

Hello !

So, when creating a LFG group (whether it's a dungeon one, or a raid one), if you don't have a BNet authenticator, usually you just can't edit the fields, but they are auto-filled with a generic name, and you can list the group.
However, with Aurora enabled, the title is not auto-filled, thus the group cannot be created under any circumstances.
Here are 2 screenshots where you can see the difference between the behavior with and without Aurora, the button to create a group being greyed-out with the addon enabled, and zero way to create it unfortunately.

Dungeon : https://i.gyazo.com/8a2d56ce0bc3ff54122291015ad58c54.png
Raid : https://i.gyazo.com/a4644ef94b5bfdc004a6beec70601532.png

I know one other easy fix would be to activate authenticator, but still, it should normally auto-fill these fields and let us be able to create the group regardless.
Curiously enough, there is no LUA error tied to this behavior.

(The "Goal" and "Playstyle" dropdown lists are not working too it seems, as we can see on these screenshots)

Thanks a lot for your time when you'll check this issue !

Expected Behavior

No response

Steps To Reproduce

No response

Additional context

No response

commented

This caused by an anti taint fix that I put into 10.2.7.1. The taint is caused by Blizzard. I will check if my "backup" wow account have authenticator to test this.. but this is a bit "damned if you do damned if you dont" situation. And the reason there is no taint and no error is that the fix is to overwrite a blizzard function :)

92b2fe8

This is the fix if you want to try to remove it. And see if you get the lua error/taint instead

commented

Hey,

It seems removing the fix works (I can now list LFG groups), and I got no new error in the process.
Do you know what else can happen by removing this fix, just in case ?

commented

Fix is in 10.2.7.4