Crystal Charge shouldn’t be marked as a stun given that it doesn’t, in fact, stun.
1 Like
But that’s how it worked back in the day too. Anything immune to stuns is immune to crystal charge… and there’s dozens of abilities / spells suffering similarly. (Damage + CC type combined in one effect means the damage is immuned if they are also not susceptible to that CC type)
There are a lot of things that have been changed even though “that’s how it worked back in the day.” That’s not a good reason to keep what was likely a bug back in vanilla caused by copy / pasting code from iron grenades without removing the “stun” designation. It was a bug then. It wasn’t caught then. Doesn’t make it sacrosanct in the “it should remain this way” world of things.
1 Like
Just go full sweaty mode and have the entire guild respec engineering for sappers. Then hes free loot every week. Its kinda nice. (and sweaty)
I mean, that’s an option, but not all of us are going full hardcore raiding guild either 
Don’t think we should have to when there is a viable option available that is bugged.
that’s your opinion but also happens to be a poor argument. if everything that was slightly unusual / bugged / copy pasted was suddenly changed, classic wouldn’t resemble classic at all anymore. people already have countless complaints about things that did have to be changed in modernity because of technical reasons, exploitative potential, economic reasons, etc.
Considering there’s places where crystal charge works perfectly fine, and that Goblin Sapper charge can work where crystal charge doesn’t, there’s player solutions to the inconsistencies.
Crystal Charge isn’t bugged, it’s just different. An argument in defense of its design is that Crystal Charge is dramatically easier to obtain than Engineering’s Sapper Charges, and so having some use-case restrictions on Crystal Charge means there’s still a compelling reason to be an engineer. This line of thinking was carried out for later expansions, specifically: if something is redundant or makes a tradeskill (or class ability) obsolete, adjustments are made so all applicable abilities/items still have a relevant purpose.
1 Like
Except this argument ignores the fact that nowhere in the description of Crystal Charge do we see the word stun. Nowhere in the history of the patch notes did it ever stun.
.
I do love your slippery slope argument back to my actual argument. If we changed everything it would blah blah blah blah. No one has asked for everything to be changed. #nochanges died before the game even launched due to layers being implemented, so please cut the bull.
.
It was an uncaught bug in Vanilla and if you are going to respond with “it has different uses than sapper charges” you could at least point to the aspect of Crystal Charge that indicates that it should have different uses rather than some lame conjecture based on some perceived difference that can’t actually be found on the item itself.
1 Like
“How things really work behind the scenes” is 100% part of the appeal of classic. Things are not well explained, tooltips are vague, and interactions in combat are not always intuitive. Your post doesn’t ask for everything to be changed, but thousands of posts just like yours, for different, one-off, small menial issues, should they all be acted on, would amount to a different game. If you think suddenly fixing hundreds of things players are using to their advantage, using to feel clever, or that they’re using to play in an obscure way would change the game for the better, that’s something you can’t be sure of. It might be easy to think fixing Sapper charge obviously affects nothing else and only makes it BETTER FOR EVERYONE, but that’s implicitly wrong. “Why cant you just fix this one thing.” is not a very critically thought out post.
That’s a long wall of text that says #nochanges without actually addressing the item at hand at all. Again, having a bugged item isn’t “part of the appeal of classic” for everyone. That’s your own personal bias talking. You want the bugged items. You don’t want them to fix x,y,z. That’s fine, but it isn’t a refutation of my point. At all. It is an attempt to take a pointed instance and generalize it so you can trivialize it.
.
So straight up, find me the place within Crystal Charge where it makes it a stun. Find me the functionality where it stuns. The best you have is that maybe, just maybe, at some point it was intended to have a stun, but at a later point they either accidentally left the stun off or decided it shouldn’t have a stun but forgot to change the item to reflect that it isn’t a stun. Either of those are bugs. Nothing you have said has refuted that fact. Nor have you tried to.
.
So for real. Come with something that directly applies to my bug report. Because it is a bug report not a general forum post. Don’t give me some philosophical garble attempting to trivialize the bug report due to your inability to find something that would actually say it isn’t a bug.
you wrote more than me raidlet
I also separated it out so you could read it. Still have no actual point regarding the item I see. Carry on.
Accept they don’t work the same, it’s a game similar to Vanilla running on the retail game server and client.
If everything was the same then a plethora of TBC changes would not have gone live in classic.
If it was the same then the guardian pet AI would work like it did in classic rather than bug out.
As for the crystal consumes, who knows how they actually worked in Vanilla on that fight because that’s one boss most guilds just skipped because he’s a pain if you don’t go full sappers for the globs. No one did that back then, so it was actually kinda a pain back then, and without eng it stands to reason it would also be a pain now too.
The amount of accurate information from the Vanilla time is so limited and or lost to the depths of dead servers so no one really knows for sure.
Also consider that Blizzard has this “reference build”, but chose to go with a retail server and client because it’s allegedly better. Stands to reason that the reference build may not be so complete with all the cumulative bug fixes that took place across the timeline of actual Vanilla, in turn making the reference client technically wrong.
That right there would actually explain some quirks that exist now, yet were bugs that got specifically patched out in mid to late Vanilla, yet here they are.
Example, getting hit by chain lightning on a bounce while in stealth was specifically patched out along with multi shot and cleave and so on.
Guess what often knocks me out of stealth when it should not.
It’s stands to reason there are a lot of bugs that made it live that we have yet to discover.