Ok, so in Vanilla, the LUA scripting engine was unregulated. You could use every single command whenever and however you wanted, with full language syntax and even to the point of if statements and complete scripting functionality. Even without addons, you could make a macro that would decide what attack to use based on how many combo points you had, what buffs you had, what debuffs the enemy had, and how much energy you had. There was a well used rogue macro that basically played the game for you on the Vaelstrasz encounter, and you never had to make a single decision, just spam it. For healers, a mod called Decursive would change the target of a unit frame, without user intervention, so that you could simply spam one button and remove magic/curse/poison/disease etc.
In TBC, they implemented Secure frames and Macro Conditionals. This meant that while you had far easier shorthand for a lot of stuff, addons were far more limited in their active capabilities and decision making while in combat. What spell a button cast, could not be decided on in combat except with preconfigured limited conditionals. Addons could not affect a Unit Frame in combat.
Those are the big changes between Vanilla and the modern API in terms of functionality. In Vanilla someone could have easily written one of these LFG mods and there were some with rudimentary features. However, the community of developers was far smaller, and less experienced.
The biggest difference between now and then, is the same change in the players. We know far more, we’re far more experienced, and we are far more capable than we were back then.
Calling out in Trade Chat was not what made the community strong back then. Vanilla would not have been damaged by a global LFG channel, and in fact for part of the time we had one. The community was built by people interacting, but the majority of that important interaction was inside the dungeon, not trying to get your voice heard in Trade among all the noise.
That’s why part of the uproar about this LFG tool is misinformed. The things that made the Blizzard LFG bad, were its cross-realm capabilities, an instant teleport to the dungeon, and the facelessness of the members of the team, since dungeons were made far simpler to cope with the lack of team cohesion.
The LFG broke the server identity because you were matched cross realm. It broke the roleplaying element, because you were instantly tranported in and out of dungeons instead of having to ride across the landscape to get there. And it broke the community because you didn’t have to rely on your own server community to get into dungeons and later raids.
This tool would have affected none of that, but the massive uproar because it was called LFG and didn’t put 5 rogues in a group together like Blizzard’s first attempt at an LFG tool, has made Blizzard consider breaking the Addon API in ways that have far reaching effects well beyond the kneejerk reaction about LFG.
I’m not worried about that addon. I’m worried about how much other unrelated stuff they’re going to break because of that addon, and I’d like to hear their thinking on what aspects to break, before it’s done, so that the community can weigh in with an informed response, instead of having to claw back the Vanilla experience we had from an overzealous management team.