Why the hell did you break crossrp?

Community General Discussion
83

Too bad they went against it and sharded it at the end of the ToA this year.

1 Like
84

I have a feeling that this was addon was knocked out do to sweeping restrictions blizz put on their API. From the general chatter I guess some Mythic+ and raiding addons that accessed blizzes stuff have been hurt as well.

85

Just a reminder that you can still take community channels from battle.net and make them appear in game. RP Connect isn’t really necessary when you can just take a channel from a community and select the option to make it show in a tab of your game such as general. It won’t account for some things like your in-game name, display profiles, or account for emote distance, but if you and a group of friends still wanted to rp in Booty Bay that could work.

It might just get densed or cluttered the more people join into the rp channel, so I would just plan out the interactions with like groups of 3-5 (and maybe 10 tops). I generally only rp with small groups of people anyways.

1 Like
86

This is the only reason I bothered to purchase BfA, because of this one event and the sense of community it brought me. Bringing together people from across the game - all servers, all factions, all sorts of people - under one roof (so to speak)
 it was a magical thing. It was a wonderful demonstration of the strength and vibrancy of WoW’s community.

But WoW’s current dev team does not - I’ll say this bluntly - seem to appreciate community if it doesn’t come with a red or blue sticker on it. Anyone who saw the Blizzcon opening stream knows what I’m talking about. Everyone else at Blizzard loves for the community to come together as a whole, one group that encompasses all the people who love their games.

But not them. The only thing they can think of at a time like that - the hill they’ve chosen to die on - is an asinine faction divide. They don’t want to build community, they want to sever it. And I, for one, am not going to sit around and watch it happen.

If there was some security risk, some need to stop M+ sellers or god knows what else, Blizzard needs to tell us. They needed to tell us weeks ago so that we would be prepared and not have this dropped on us in the middle of the night, but since they clearly failed to do that, they need to tell us immediately. Otherwise we have no choice but to conclude that it is entirely their own desire to destroy community that’s driving this change.

I’ve been through a lot with this game. But I’m not going to put up with its own developers sabotaging it out of some misguided belief that community is bad for gameplay.

3 Likes
87

Whoa, CrossRP doesn’t work any more? :open_mouth:

I̶s̶ ̶i̶t̶ ̶j̶u̶s̶t̶ ̶b̶r̶o̶k̶e̶n̶ ̶b̶e̶c̶a̶u̶s̶e̶ ̶o̶f̶ ̶t̶h̶e̶ ̶p̶a̶t̶c̶h̶ ̶o̶r̶ ̶i̶s̶ ̶i̶t̶ ̶o̶u̶t̶ ̶a̶n̶d̶ ̶o̶u̶t̶ ̶d̶i̶s̶a̶b̶l̶e̶d̶?̶
EDIT. I just found out my answer :frowning:
12/11/18: Patch 8.1 has blocked Cross RP’s functionality, and development is currently suspended indefinitely.

I RP with a couple of blood elf players in some contested areas and CrossRP is what I use to talk to them.

88

What gets me is that if they hate cross-faction communication SO much
why make it possible in-game at all with Pandaren, demon hunters and now blood/void elves? Clearly the game hasn’t ended and people still PVP even with those cases. Frankly the language barrier itself is stupid. We as player characters have no problems speaking to leaders/NPCS from the other faction’s races, but other characters who we shared our order halls with couldn’t have picked up language during the length of time Legion took place over? Not to mention the fact that Forsaken and blood elves already should be able to talk to Alliance given that they used to be part of it.

6 Likes
89

I swear your name is familiar. I feel like I was in a raiding guild with you at one point a while ago.

1 Like
90

And people still think Blizzard is a good company and that WoW deserved MMO of the Year? :thinking:

Screw this dev team and company. Like, just being real about it.

3 Likes
91

You heard from her. One way or another though, I am not going to let this setback stop us. However I have to say. This is just awful. I personally think that cross faction chat should at least be allowed with warmode off and/or especially in RP realms. Some peoples’ RP has them as apart of neither the horde or alliance or with different kinds of special alliances.

1 Like
92

They should just let everyone speak common and if someone’s being abusive, report them. Literally no other PvP game has this “problem”. (I’m not convinced WoW does either but they seem very reluctant to demonstrate that.)

5 Likes
93

I mean I love PvP. If they did have cross faction communication with warmode on with the option at least to block it I’d be fine with it. Though for battlegrounds and arenas I do see why it would be not allowed since people could conspire with the enemy team. It would make trading wins more easy.

94

I mean, in a world where Discord exists and people can trivially communicate outside of Blizzard’s reach, I wouldn’t be overly concerned with that. At least if they’re colluding on in-game chat, Blizzard has the evidence in their logs, right?

Thinking about blocking it, I’d probably make it either a global or channel-wide chat setting. So like how your chat window right now has like, “say”, “NPC say”, “yell”, etc. toggles it would be “allied say”, “enemy say”, “NPC say”.

95

Relax

Blizzard can’t adequately deal with every addon that people like. They change the code, addon developers need update their software to suit.

96

What a stupid, brainless decision. Everyone who used this addon was always worried when the axe was going to fall, but I think there was also this hope that if Blizzard saw how much of a positive reaction it got (plenty) and the good that came out of it (loads), they’d just let it slide.

I don’t really think this is about cheating or any kind of mechanical abuse. This is about one of the core pillars of the game’s setting, the faction war, coming under direct attack by people who are rightfully sick of it getting in the way of how they choose to have their fun. Instead of taking the hint and realizing how outdated, divisive, and badly written the conflict is, they’ve killed the dissenters en masse and buried it in patch notes like it was another bug fix.

6 Likes
97

This isn’t just a matter of updating the addon. The API calls that it relied on to work, the functionality that allowed addons to read from and post to communities, have just been removed entirely. And with no warning.

This is equivalent to disabling the ability for addons to see your party members’ health and buffs and telling people who use custom raid frames “you just need to update”.

1 Like
98

I understand it feels that way but that doesn’t make it true. There was no warning - did they intentionally break the addon or did they make a change to their system that unintentionally rendered the addon broken?

99

An addon circumvents an intentional game mechanic.

An addon is then disabled by Blizzard.

Seems pretty self-explanatory.

2 Likes
100

The addon had safety measures in place so it was not able to be used in a way that would affect the core of what Blizz wanted - namely PvP griefing or raid functionality. It literally existed for roleplayers to do their thing. The issue is that Blizz only wants players to enjoy the game their way, breaking how chat functions because of another addon they seem to take issue with. That’s really all this is boiling down to. It’s disheartening and very unfortunate.

7 Likes
101

I get they will always cater to PvP/PvE. That’s fine and the majority of RPers have accepted that. But you’re telling me it makes sense in lore for a Void Elf to forget the languages they spoke previous just because of (insert Velf lorestory)? This applies in numerous cases, across the lore of the game. Just let us do our “casual” roleplay on the servers meant for it.
(Also- be transparent about your API changes. Really poor form, Blizz.)

4 Likes
102

Im sorry, but your logic is annoying.

White knight.

1 Like