Flarendo the Furious Mount AVAILABLE!?

Just saw someone in Dornogal on the mount that isn’t supposed to be available until renown 20 of the raid renown. This week is renown 8.

I reported them for cheating already, but this is crazy. Also means they have the damage and healing buff of 18% now!

1 Like

It was a bug, not cheating. And no, they don’t have the buff, that was already rolled back.

1 Like

Not a cheater. There was a bug this past week in reset that allowed some players rep to shoot up to max in lfr lol they must’ve got to keep the mount.

The buff is def removed though

1 Like

Crazy that a bug like this happened. I wish I could have been blessed with getting the dino mount, lol.

3 Likes

They’ve removed it from anyone who did the bug with today’s reset.

Gallagio Loyalty Reward Renown Rollbacks After Bug Last Week - Wowhead News

1 Like

As cool as it is to get a raid boss as a mount. I really hope they make him and Torq tamable for Hunters as well. Having a mecha-devilsaur as a Goblin Hunter would be awesome.

2 Likes

I was thinking this earlier, how my Mechagnome hunter would love that dino as a hunter pet!!

I’m really happy about that. Good on Blizzard for fixing their mistake.

1 Like

They didn’t roll back the mount, they rolled back the Renown. Anyone who had the mount still has it in their journal, I asked someone who has it and they still do.

They still have it but they can’t use it until Renown 20.

1 Like

Ah, that makes sense.

An exploit that some people were able to take advantage of, intentional or otherwise.

1 Like

Most had no idea what was going on. It was a bug. It’s been rolled back. Y’all can relax.

1 Like

Wouldn’t exploiting a bug be its own form of gameplay sabotage in a way?

1 Like

That’s how exploits normally work. A small number of players work something hard to get early completion of something before most find out about it. I seem to recall seeing an article in wowhead very recently about renown being quicker than anticipated.

I think the solution was the right one. But the idea that nobody knew about this and having this happen was 100% accidental and not even noticed by those who did push it is out there.

If you’re working hard at something, that implies you know what you’re doing and trying to get an advantage with intent.

That’s very different from just doing LFR and then saying “WTF, I just got a mount?!” which is innocent of intentional exploit; you didn’t know about the bug until AFTER an item was dropped in your bags. I know this happened to one of our guildies who even posted a screenshot of being Rep-20 while the rest of us were Rep-8; none of us at that time could explain it as anything other than a bug and that guildie reported it as such in-game.

So no, exploits are not “intentional or otherwise,” they are always someone that KNOWS they are breaking the rules and continue to do it anyways.

Which some people did, considering that I was aware of this from reading wowhead alerts and the forum and don’t even play retail. My takeaway from what I was reading was that these sources were telling people to get it before it got fixed.

I think they came up with the right solution. I don’t have any feeling over whether this was something that showed up on the PTR, was reported, and reports ignored. Or whether it was put into the game utterly untested.

I saw several with this mount.

Needless to say, not anymore, lol.

Not for a few more weeks anyway.