To ensure that macro usage aligns with our overall goals for addons, there have been some minor changes made to macro capabilities that were recently deployed to the live client:
- Macros are prevented from setting a target marker on more than 3 units within a very short time.
And the following restrictions only apply while the player is in an active encounter:
- Macros are no longer allowed to send chat messages to chat channels that are not exclusive to the group (custom chat channels, guild, communities, etc).
- Macros are still allowed to send chat in group-exclusive channels (/raid, /party, /rw, etc), but are prevented from sending multiple messages to those channels within a very short time. In addition, all members of the group must be inside the instance or macro chat will not be allowed in these channels.
- Macros are still allowed to send chat in whispers but the whisper target must also be in the instance. Macros are also prevented from sending multiple whispers within a very short time.
2 Likes
Define minor. This changes are anything but minor lol.
No offense, but this number of draconian changes to macros and addons feel excessive , and hardly anyone likes them (and rightfully so) . Please reconsider your stance.
Also, your basic UI is still a mess. How in the world are healers supposed to do dispels with this sorry excuse for a UI?
Also also, please tell the devs they have a laundry list of bugs and issues still unresolved in the live game (like the Fish for the Fire World quest for example) , so please solve those first. Thank you.
4 Likes
imo you guys should just start permabanning people who try to exploit systems rather than making the game like this for normal ppl
3 Likes
i haven’t been able to finish the first quests of the intro of midnight for 4 days now and THIS is what is important to fix.
Thanks a lot for making me feel like a valued customer…
i am talking about the first 3 quests (my son, Champions of Quel’ Danas and Where heroes holds )
3 Likes
Why is the nochanneling macro not working. been at least a year.
Macros such as these two cause your abilities to lock and be unable to use any cast for a few seconds. This is something to many players, some have no issue using these macros.
/stopmacro [channeling]
#showtooltip Reap
/cast Reap
/stopmacro [channeling:Void Ray]
#showtooltip Reap
/cast Reap
1 Like
More garbage changes nobody asked for, thanks.
What happened, Linxy? The only thing I can think of is that PVP came into play, and someone started spamming a macro message. It could be PVE, but the likelihood is far less than PVP.
- You could have created a chat lock on the player to prevent spamming of a macro message.
- Within a certain timeframe, their chat is locked.
- The player can see a timer showing them that their next message can be sent after a certain timeframe ([XX:XX]).
If I were a developer, that’s how I would have handled the situation. That’s common sense, so why not lock out chat when someone uses a macro message too many times? It makes no sense.
I can see some players not liking my idea as well because it hinders them, outside of groups/raids, in normal chat, from getting a message across when someone is pulling a mob, needs help, or needs to move to a spot, etc. Some macros are helpful, while some are harassing.
Bad changes. What next? You gonna ban background voice chat programs and in game chat entirely? Gonna ban all forms of communication so no one can do anything to counter your bosses? Why not just make the boss invincible and call it a day instead. This war on addons has been a train wreck and done far more harm than good.
1 Like
Can you give a plausible scenario where any of those changes would affect you detrimentally?
Don’t you dare tell me we can no longer /yell and /emote in macros!
This concerns me as a mythic raider for Undaunted which is a guild for the deaf so we don’t use voice chat at all. We rely heavily on macros for communications due to not having voice chat as an option. Our RL has multiple macros for raid callouts and sometimes multiple has to be used concurrently to address a situation/mech.
How are we supposed to beat communication based bosses when our communication tools are taken away and the one available is inaccessible to deaf players? We would like to experience content and push as much we can but we need macros to do so.
10 Likes
How restrictive is this?
My guild, Undaunted (the deaf guild), uses macros to spam the Raid Warning channel as a method for calling out important raid info. It’s basically our “voice chat.”
We already lost the ability to modify the Raid Warning pop ups with the addon changes. In its default format (tiny red text that often gets washed out by the game’s backgrounds), it’s virtually impossible for us to see, so spamming it is even more necessary to us than it once was.
I have already posted requests to allow us to change the size, location, color and background color of the Raid Warning alerts to make them more useful to us. If this change is going to limit how much we can spam Raid Warning, then we need to be able to modify how it looks on our screens to improve visual clarity.
10 Likes
Ok @Linxy if you could please send this report back up the chain as this is absolutely going to destroy so so SOOO many addons and really break them, and they have nothing to do with many of the issues as to the reasoning.
Logging in tonight revealed that certain API is completely removed from the game now, like this:
GuildRosterSetPublicNote and GuildRosterSetOfficerNote.
You can no longer write to the guild info.
These API seem to be replaced by the C_GuildInfo.SetNote(). Here’s the problem, that is a 100% protected, non-usable API.
I am the author of the Guild Roster Manager addon and this will now 100% break so so SOOO many features permanently. There is no way for the addon to auto-add join dates to player’s officer notes when they join. Or, to export the dates to the notes if they are synced from other players. GRM has a feature that auto-updates member profession info to the notes as it changes. Also broken. Exporting main name to alt groupings? Broken. Mass restoring player notes from internal GRM backup in case of trolls? Now broken.
I can’t even auto set important detail to guild info anymore. The API appears to now be protected for some reason. This is critical data in a guild!
Wouldn’t it make more sense, given your goals with addons, if this stuff was only protected or only returning secret info when in combat or a PVP instance? As of right now, this all has 100% functionality removed even rested sitting in a city. This is not just GRM that will be affected, but so many addons that use things to update player notes with useful info, like DKP, attendance trackers, alt management addons, and many others. This is actually a HUGE blow to guild management efforts and will actually make people’s lives worse.
9 Likes
From the documentation, it doesn’t appear to be.
It will not accept secret arguments in combat, but that shouldn’t be unduly restrictive.
https://warcraft.wiki.gg/wiki/API_C_GuildInfo.SetNote
so it sounds like i need to remove yell from my warlock’s soul well macro i use to get people to see its going down at the start of a run. and my druid’s battle resurrection macro is back, if i change to party/raid… for those wondering…
#showtooltip
/run m=""; l={"Party","Raid","Yell","Instance_Chat"} ; for i,v in ipairs(l) do SendChatMessage(m,v) end
/cast Create Soulwell
and
#showtooltip
/run m=""; if (UnitIsPlayer("target") and UnitIsDead("target")) then SendChatMessage(m,"YELL") SendChatMessage(m,"WHISPER",nil,GetUnitName("target",true)) end
/cast Rebirth
You could put down your Soul Well before the boss is pulled; most Warlocks do. The changes only matter during an encounter.
Also, the announcement says whispers within the instance are allowed. SendChatMessage may not work in combat though.
“during an encounter” (i.e only in dungeons/raids)
i’m sure your open world messages will still work fine
How about I have a simple macro that I use to mark my party at the start of a dungeon or group content that no longer works consistently.
There will be lots of other simple stuff that will now be broken too.
These things may not affect how YOU play the game but that doesn’t mean they’re not detrimental in ways you haven’t encountered.
Glad I quit and chose to no longer support this blatantly evil dev staff. This is absolutely unreal and this is a war that they started and chose to die on this hill. Well, I hope they get their wish, figuratively speaking, of course. This is creating very tangible barriers for disabled players, barriers that were never in existence prior to the idiotic decision of removing mods.
I really hope that disabled players rally on this one and start pushing the issue, legally. Something has to give here.
If not, blizzard will just continue to go down this road, and continue to move the goalposts on this issue when players come up with a new alternative to counter them. All the while, it will screw players with legitimate accessibility issues.
1 Like