I’m over here trying to write an addon to call out the @#$%heads that drop portals infront of the gate in BGs
but for some reason when other players cast portals the event doesn’t fire. The event fires for other units casting other spells, or for me on my mage casting a portal, just not for other units.
I hope you succeed, those people are the worst and deserve to be called out. Morons like the dude in this thread pretend like they’re doing everybody a service but I’m pretty sure if I head over to their house and spray their front steps down with water on a freezing cold day, “They should have watched their step!” isn’t going to get me off the hook when they slip and break their neck.
It’s deliberate trolling and anybody doing it deserves a ban.
Indeed. In wrath classic we had a mage in guild who couldn’t resist dropping a portal to stonard every single raid I originally wrote this addon to keep him from sending people to the middle of nowhere when we were trying to knock out a quick sartharion or halion.
The grief level is increased in this situation where people get the debuff so they can’t queue up again.
The only problem is that the API that worked in wrath isn’t the same in vanilla
more evidence that the anniversary community is disgusting i really wish all these people would just go play a different video game. why isn’t there some AAA modern game that attracts all these people? companies just can’t produce anything worth a dang anymore I guess.
Nah, we can’t pin this on the anniversary servers. Sadly, this isn’t even WoW. This is just humanity… apparently we have to be told not to be jerks to one another.
It was a common thing during my R14 grind in the fall of last year (on Era). I never got bit myself but I control my camera by holding right click and so I had to be extra careful walking through the gate every dang game to make sure I didn’t accidentally release/click again at the wrong time. It was unnecessarily annoying.
The easiest solution would be to just disable portals in BGs, there’s no real reason to allow them when you can just /afk out and cast a portal. Personally though, I’d prefer Blizzard to leave it in and then just quietly start flagging people who do it in the starting area. Let them think they’re hilarious for a week and then slap them with a 3 month ban for player harassment.
I don’t know anything about getting set up on curseforge I could probably figure it out if there is enough interest.
What you are asking is beyond the scope of what I am trying to do. Playing on classic anniversary I cannot test against casting a karazhan portal, more over though I made this version of my addon to only call people out in BGs.
The mages that have activated my addon have discussed all casting many portals to try to report me for spamming so we’ll see how that goes…
I’m sure we could work together to test it for a karazhan port. I think your primary usecase is 100% the right one, I’d just like to use it to have some fun in my guild if I can
I think you can just throttle it. I don’t know the WoW API super well but presumably you can get a time stamp for when you announce a message, so just throw it in a lua table keyed by the name of the player you’re announcing for. When you go to announce, check the current time against the stored time and if the time is greater than some threshold (say 60s), announce and store the new time.
Whenever you announce, it might be a good idea to process the entire table anyway and remove stale entries so that you don’t take up unnecessary addon memory.
Also, if you want to cut down on spam, do something like this…
MessagesTable = {
[0] = "%t is attempting to troll with a portal, heads up!",
[1] = "Watch out, %t is trying to bait you into clicking a portal, don't fall for it!",
[2] = "Hey, %t, that's not very nice. Everybody, watch out for the portal, don't get trolled.",
-- and so on...
}
function GetRandomMessage()
return math.Random(table.getn(MessagesTable))
end
That should prevent you from appearing too spammy since your messages will vary every time you announce.
I do currently throttle it to one message every 10s ( maybe that should be increased…) , but it does currently do a say and a yell. im not bothering to keep a per mage timeout.
If you’re interested in playing with the code I can certainly pop it up on github