Your fix didn't address this issue. oQueue still removes marks. It's not the other people removing marks. It's oQueue. Please make sure oQueue is checking with IsActiveBattlegroundArena() before changing marks.

Edit: Yes, I'm using 2.0.1.

Edit: Why isn't this thread being bumped when I post? It seems to be stuck on page 3 despite having relevant current information.

Just fyi, in 3 separate arena groups I joined today, including one that wasn't using oqueue, people I didn't know separately said some variation of "make sure to disable oqueue so it doesn't remove group markers". This is a well-known issue in the arena community, and spoils the otherwise-good name of oqueue, so I would consider it a top priority.

This was the last issue I've had with oqueue. Thanks so much again! :)

This is still happening. Please fix it! I can see places in the code where oqueue messes with raid markers (lucky charms), but I'm not sure exactly how I should edit it to fix it for myself, plus, it should be fixed for everybody. I'm tired of having to tell everybody to disable oqueue to keep my raid markers up on my arena teammates. They invariably get removed when someone has oqueue on and they happen to be handed leader.

"unfortunately, the vast majority wouldn't choose the correct arena type or would just get more or less then the number specified."

Here's how it should work IMO. The default premade subtype for arena would be "unspecified" like it is now, so what you're saying would not be an issue. If someone cared to set a minimum required rating, they would have to select the subtype (2v2, 3v3, or 5v5) first, which would unlock the minimum rating requirement box (which would be locked or hidden when arena subtype is "unspecified").

"as an extra bonus, there's not much room for additional data. groups have 255 characters with which to describe their group. b.net friend requests only have 127."

The arena rating requirement field would replace the current RBG rating requirement field, so there should be 0 difference in string length, except if there's not already space for 1 byte for specifying the arena premade subtype.

I think he wants to be able to set a minimum required arena rating for the particular bracket he's creating a premade for. This would go hand-in-hand with selecting the 2v2, 3v3, or 5v5 bracket in the premade sub-type list for arena.

If someone wants Icebox for Mac, they should send tiny a Mac for development.

Cool. Thanks so much! :)

As a side note, I can't seem to edit the "confusing" -> "confusion" typo I made and I don't see my thread on the oqueue forum anywhere. The new forum software or database or something has something strange going on.

Bug: oqueue removes group marker symbols

I am using version 1.9.7.

When I make an arena group with oqueue, I mark everyone with symbols before starting the match. This helps for seeing teammates' positions through boxes, pillars, etc. When we get into the arena prep room, the first person in is assigned leader, and can mark teammates with marker symbols. If that person is running oqueue, which is highly likely, symbols are removed at random from teammates' heads, which can cause positioning confusing when looking for those marker symbols to locate teammates. Disabling oqueue and clicking "go dark" work around this issue.

Next time it happens, I'll try that. However, once the problem goes away, having all addons enabled again doesn't bring the problem back, so it's really not going to be useful. I'll see.

I do not expect the problem to be confirmed and resolved without consistent reproduction. I will look out for exactly what causes it to happen.

I posted thinking there was probably an obvious fix from your perspective. If there's not, I have no fantastic expectations.

Thank you very much for your patience.

You didn't read my method for determining the source of the problem. I never logged out.

First, I reloaded UI to check if that removed the problem. I confirmed that it did not by attempting to change my title.
Second, I opened ACP and disabled only oQueue, then reloaded UI to check if that removed the problem. I confirmed that it did by attempting to change my title.

Yes, relogging would have worked around the issue, I'm sure. However, due to the above systematic, logical methodology, the problem is definitely perpetuated solely by oQueue. It's impossible to be something else considering what caused the problem to disappear; the fact that no other addons were disabled and the process of reloading alone did not remove the problem.

If you don't know how to fix it, just say that. I realize I didn't give enough information to investigate easily. I was just hoping you would have an idea. My methodology for determining the source of the problem is sound though. Your methodology would get rid of the problem and make it impossible to determine which addon caused it. It would be like immediately sterilizing a crime scene; a complete waste. If I had just wanted to temporarily work around the problem and not permanently fix it, I would not have posted here. I am only trying to help you improve your addon, which I do appreciate and enjoy.

My titles change normally, even while oQueue is on. The problem isn't constant in any configuration of addons. It's not easy to reproduce. It just happens sometimes. Disabling oQueue and relogging are the only ways to get rid of it. It's obvious that oQueue is the only addon perpetuating the problem.

I'm sorry if I sound disrespectful in any way. I'm just trying to be as productive as possible, and I seriously mean no disrespect.