Get an Epic Experience with Premium

iQueue

Data Broker Login to Add Favorites
  • 5 Likes
  • Project Manager: grdn
  • World of Warcraft
  • 321 Monthly Downloads
  • Supports: 5.2.0
  • 9,602 Total Downloads
  • Updated 03/05/2013
  • Created 06/30/2012
  • 10 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: All Rights Reserved
  • Newest File: 2.1.0-release5.2
or

About iQueue

End of iQueue, for now

Hi fellow iQueue users,

as you may already have noticed, iQueue wasn't fully working anymore. Blizzard protected an important API function due to battleground botters (who are now simply using a /click macro O_o) and another Queue addon which allowed people to build premade groups for random battlegrounds. This resulted in protecting the API function, of course, Blizzard did the right thing.

The bad message is that I'll quit maintain iQueue for now. My vision was to provide a broker plugin which fully replaces the minimap Queue icon. Because the API is protected now, you would need the minimap icon at least for leaving battlegrounds anyway. At first I thought about building my own dropdown menu without the leaving battleground feature, but that's really not what I want to do. I'm also not motivated in doing this.

As for now, iQueue simply displays all queues you are queued for, like always before. Hovering the LDB plugin displays the original QueueStatusFrame at the minimap icon, clicking the LDB isn't working anymore. I won't abandon the project because I hope for another API change which overhauls the complete WoW queue system - anyway, everyone who knows Blizzard will know that this will apparently never happen (for example, the quest log API is really weird and painful, but its working, so why should they overhaul it?).

Sorry.

Broker Plugin: iQueue

iQueue is an LDB plugin which displays your current queue status.

Requires an LDB Display Addon, f.e. Chocolate Bar!

Highlights

  • Supports all different queue types in the game: Looking for Group, Looking for Raid, Raidfinder, Pet Battles, Scenario, Challenge, Wintergrasp/Tol Barad...
  • Displays each queue on the LDB plugin, in different colors:
    • Grey: Queue paused (WG/TB: queue available)
    • Red to yellow: Assembling group
    • Yellow: Invites are out, click "Enter"
    • Green: You're in an assembled group

Requests, Bug Reports and Localization

  • Please use the Ticket System on CurseForge to report bugs, unintended behaviour, request for features, etc. I won't handle any kind of requests via comments on Curse anymore. Thanks.
  • I refuse to translate my addons with translators like Google since it feels wrong. If you can provide localized strings, please use the CurseForge localization tool.

Bindings

  • Plugin
    • Left-click: interacts with Blizzard queue dialog
    • Right-click: opens the options frame
    • Shift+Left-click: opens PvE frame
    • Shift+Right-click: opens PvP frame

------------------------------------------------------------------------
r36 | grdn | 2013-03-05 19:37:46 +0000 (Tue, 05 Mar 2013) | 1 line
Changed paths:
   A /tags/2.1.0-release5.2 (from /trunk:35)

5.2 ready
------------------------------------------------------------------------
r35 | grdn | 2013-03-05 19:37:26 +0000 (Tue, 05 Mar 2013) | 1 line
Changed paths:
   M /trunk/iQueue.toc

Bumped TOC to 5.2 even if iQueue is dead. I love you, guys. :P
------------------------------------------------------------------------

Addon Packs Containing This...

Comments

First Previous Page 1 of 2 Next Last
  • #21

    No, the sad part is the dregs and scum of humanity that abused the functionality, to the point where Blizzard felt it necessary to come up with the "protected" stuff in the first place, not sure how long you've played WoW, or coded AddOns for it, but that wasn't always there.

  • #22

    I'm here since Classic, coded addons since then as well (not cool stuff like BAM mod and so on...). The protection stuff was first introduced in late Classic, patch 1.10 when I remember right, where all Moving APIs got protected. Protection is necessary because the protected APIs are really powerful. But protection is also used on APIs which are used by third party people for automatization stuff or exploiting.

    All addon authors must take care themselves if they provide too much automatization or too much advantages over other players with their mods. If Blizzard thinks some author breaks the tolerance line, they break the addons functionality. Happened a few times in the past and happened once again now. :(

    Last edited by grdn on 1/17/2013 10:37:59 AM
  • #19

    Hi folks,

    I added a message to the iQueue description which explains why I quit maintaining the addon for now.

    Sorry!

  • #18

    That really pissed me off, not being able to leave a queue. They should make it for countries where the botters are. I am bein treated like a dirtbag because of some foreign hacker. wtf Blizz

  • #20

    Blizzard did the right thing (=> protecting the API). The problem is that people who really want to bot already found a way to continue botting, the users of an popular queue addon cannot use their addon anymore to kick poor random battleground players asses. But this protection resulted in breaking one of iQueue's main features, too.

  • #17

    Uploaded an updated version of iQueue. Leaving any kind of queues is currently not available anymore, because Blizzard protected an important API. Leaving battlegrounds will NEVER be possible via iQueue again. Its not my fault, its not iQueues fault. PvP botters are the bad guys since they forced Blizzard to protect the API.

  • #12

    He folks, pleeeaaaaase use the ticket tracker. I just view these comments under random circumstances, which means almost never. Anyway, the annoying bug is fixed by now. 

    Last edited by grdn on 12/21/2012 8:06:34 AM
  • #11

    Date: 2012-12-20 18:44:44
    ID: 2
    Error occured in: Global
    Count: 1
    Message: ..\AddOns\iQueue\iQueue.lua line 111:
    attempt to call method 'HideAllTooltips' (a nil value)
    Debug:
    [C]: HideAllTooltips()
    iQueue\iQueue.lua:111: OnEnter()
    Bazooka\Bazooka.lua:1431: showTip()
    Bazooka\Bazooka.lua:1246:
    Bazooka\Bazooka.lua:1237
    AddOns:
    ...

    Last edited by grdn on 12/21/2012 8:08:05 AM
  • #10

    Queued a specific battleground, tried to leave queue after realizing time too long, and got this

    Date: 2012-12-18 14:57:13
    ID: 1
    Error occured in: AddOn: iQueue
    Count: 1
    Message: Error: AddOn iQueue attempted to call a forbidden function (func()) from a tainted execution path.
    Debug:
    [C]: ?
    ..\FrameXML\QueueStatusFrame.lua:404: func()
    ..\FrameXML\UIDropDownMenu.lua:710: UIDropDownMenuButton_OnClick()
    [string "*:OnClick"]:1:
    [string "*:OnClick"]:1
    Locals:
    None
    AddOns:
    ...

     Even tried a reloadui.  Will have to relog.  Please fix =)

    Last edited by grdn on 12/21/2012 9:05:19 AM
  • #16

    Apparently there is nothing to fix anymore... The "leave BG" button executes the API AcceptBattlefieldPort, which was "half" protected since patch 4.1, calling this function from addons was only possible in syndication with a button click event, for example. Now, the function is "full" protected, what means that it cannot be accessed by addons and macros in any way - or simply: you cannot leave BG queues from the LDB anymore.

    THANK YOU GODDAMNED BG BOTTERS, YOU ARE(!!!) the reason Blizzard did protect the API function. I cannot do anything to fix it but completely recode iQueue to avoid accessing Blizzards dropdown menu. Mah... -.- iQueue was stable and fully working. Damn.

    Last edited by grdn on 12/21/2012 9:21:55 AM
  • #9

    This happens when I try to swap talents or glyphs:

    Date: 2012-11-29 15:09:56
    ID: 9
    Error occured in: AddOn: iQueue
    Count: 1
    Message: Error: AddOn iQueue attempted to call a forbidden function (RemoveGlyphFromSocket()) from a tainted execution path.
    Debug:
    [C]: RemoveGlyphFromSocket()
    ..\FrameXML\StaticPopup.lua:82: OnAccept()
    ..\FrameXML\StaticPopup.lua:3897: StaticPopup_OnClick()
    [string "*:OnClick"]:1:
    [string "*:OnClick"]:1
    Locals:
    None
    AddOns:
    ...

    I have to reloadui when this happens.

    Last edited by grdn on 12/21/2012 8:09:25 AM
  • #13

    iQueue does not try to remove glyphs. It got blamed by the WoW client because the WoW Client loves to blame randomly selected addons if it encounters UI taint. If the mod should have tainted the UI due to setting up a StaticPopupDialog, adding/removing glyphs shouldn't work for me either. But it actually does.

    Last edited by grdn on 12/21/2012 8:19:00 AM
  • #8

    I queued for AV, and it popped when I was on a flight taxi I clicked "Enter" and it didn't take me in.

  • #15

    iQueue has nothing to do with the actual "enter dungeon/battleground" stuff. iQueue just displays the queues you are queued for.

  • #6
    No Icon on Bazooka bar

    I use Bazooka for my LDB display and no icon is showing.

    The placeholder is there to interact with just no icon showing.

    Other than that everyting works fine for v2.0.3

  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Marriland Furious Fists Giveaway!