Blizzard supposedly removed the auto-accept function from Group Finder. You must now manually approve all members that join your group. Automatic search & pasting text into the search box no longer work as well.
Update: According to our friends at MMO-Champion, you must now search for Groups manually and enter text into the search box as well, pasting does not work.
A player got a Game Master response and posted it on the official forums, claiming that the change is intended. Waylay, however, thinks it’s just a bug and we’re going to see it hotfixed in the future.
It looks to be unintentional. They are securing the Auto-Accept feature more in today’s hotfix by providing lua access to a C function:C_LFGList.CanActiveEntryUseAutoAccept()
I tried to bypass it with:/run C_LFGList.CanActiveEntryUseAutoAccept = function() return true end
While this gave me the Auto-Accept checkbox when I relisted, the checkbox immediately un-checks itself when I turn it on. This is probably because filling in the checkbox also calls a C API function which checks the real CanActiveEntryUseAutoAccept rather than my attempted bypass.
As C_LFGList.CanActiveEntryUseAutoAccept() appears to be returning false all the time, even when it should return true, I must assume it is broken. The function is either incomplete or bugging out with incorrect condition checks.
Given that many of the more technical experienced GMs didn’t realize the option is gone under normal circumstances that it should be available, and that it was NOT mentioned in any hotfix notes, this helps confirm that it’s just a bug.
We should be able to use the Auto-Accept button again in a future hotfix.
There are also other possibilities here as well. The C function for enabling the Auto-Invite feature may also be possible to turn on and off server-side. The developers might simply be testing the LFG tool load conditions between having it enabled and having it disabled, and could turn the feature back on at any time.
Perhaps it would provide folks some comfort if a link to my post was included in the OP/thread starter post.
For reference, here is the Interface code change diff:--- a/Interface/FrameXML/LFGList.lua +++ b/Interface/FrameXML/LFGList.lua @@ -1224,7 +1226,9 @@ function LFGListApplicationViewer_UpdateInfo(self) --Update the AutoAccept button self.AutoAcceptButton:SetChecked(autoAccept); - if ( UnitIsGroupLeader("player", LE_PARTY_CATEGORY_HOME) ) then + if ( not C_LFGList.CanActiveEntryUseAutoAccept() ) then + self.AutoAcceptButton:Hide(); + elseif ( UnitIsGroupLeader("player", LE_PARTY_CATEGORY_HOME) ) then self.AutoAcceptButton:Show(); self.AutoAcceptButton:Enable(); self.AutoAcceptButton.Label:SetFontObject(GameFontHighlightSmall);
It was only by coincidence that I managed to have the interface code from yesterday saved haha!
Can always just look at UI diffs
The changes were probably hastily done for whatever reason they want. Maybe they felt automated grouping would be bad for servers on launch. They stated in in past that those addons affected server stability. in fact, last few days, a few realms have been crashing and immediately recovering. Whether or not that’s related is anyones guess. So this could be a very quick and dirty for now, and cleanup later, just as you surmise.
One thing is clear though, destroying automation was their goal.
EDIT. CanActiveEntryUseAutoAccept(). This function SHOULD return true/false (currently false to all) on whether or not the currently listed activity in group finder has permission to use auto accept or not. So it’s CLEARLY intended to disable auto accept on a per activity basis. We just need the list of what is permitted and what isn’t.
We’ll let you know more as soon as we have updates regarding the issue.
(Image courtesy of redditor Feywhelps)