Hey guys. One of the problems with fishing as its currently implemented is that two of the high-level fish aren’t worth a damn. Specifically, summer bass, and mightfish. Sunscale salmon to a certain extent as well, though some people like the strong troll’s blood potion effect.
The problem is really very simple. “Hot Smoked Bass” gives a +10 spirit buff for 10 minutes, “Mightfish Steak” and “Cooked Glossy Mightfish” give a +10 stam buff for 10 minutes. Not that bad until you consider that the Well Fed buff from basic high level cooking recipes (Spider Sausage, Tender Wolf Steak, Hot Chili Crab, Monster Omelette, Heavy Kodo Stew) give BOTH +12 stam and +12 spirit for 15 minutes. The only thing the fish have over basic high level cooking food is that they apply their buff instantly (still have to be out of combat, though).
To me, the solution is pretty simple. Let the unique fish buffs stack with the Well Fed buff. I know that’s not exactly “classic”, but there have already been other changes to the game that deviate from vanilla, and this would hardly be gamebreaking.
Because the basic cooking recipes are superior in almost every conceivable way. In addition, the raw fish don’t have the buff, they need to be cooked to give it, and they both require relatively high cooking and somewhat pricey cooking ingredients (two hot spices for Hot Smoked Bass, soothing spices for Cooked Glossy Mightfish, and hot spices and soothing spices for Mightfish Steak). The recipes ain’t cheap either. There’s no good reason to even cook them except maybe to level up your cooking if you aren’t at max level yet. Despite being rare drop high-level fish with pricey cooking recipes, they’re complete trash below even something like redgill and only barely even good for vendoring. The best you can hope for is to sell them to hunters on the cheap as pet fodder.
I mean, summer bass is supposed to be the the Spring and Summer season’s big seasonal fish on par with Winter Squid, and it’s not even as good as something like redgill or darkclaw lobsters, because it’s ingredients are expensive and it’s unique buff is worthless while it’s mutually exclusive with Well Fed.
Listen man. This is not a reason to add a change. If we go by this logic it opens up every single aspect of the game to being changed.
“May as well add deathknights, flying and monks. We made a change to the mail…”
See how ridiculous that is?
Now if you were supporting removing the pve’ers from pvp servers I could get behind ya on that. Lol
Nonsense, they already made changes from Vanilla, and “fish buffs stacking with well fed” isn’t the sort of change that slippery slopes into Panderan monks.
To my memory, the cross-realm battleground thing was introduced in TBC (and even if it wasn’t and I’m just mis-remembering, the cross-realm bullsh*t is absolutely in the spirit of the “bad” changes that ended up turning Retail into the sh#t that it is now), and yes they added more debuff slots on bosses. If you’re okay with more debuff slots, I don’t see how making a slight alteration to fish buffs is all that different.
Don’t get me wrong here. I actually agree (to an extent) with this. I think it would be great if we had server-only BGs. It would definitely set some servers apart from others when it comes to ranking, and rivalries, however, I suspect there would be exponentially more QQing on the forums over queue times (though, I could be wrong).
“Cross-realm battlegrounds were a feature of 1.12”
“I.e. Debuff Limit - in 2004 you could have 8 debuffs on a mob and that was it. In 2005 it was 16, BC it was 40, now it’s effectively uncapped. This originally was a technical limitation, not a design values problem. We will be restoring it to 16 debuff limit. It is objectively worse design but we don’t want to mess with the 1.12 data so we’re going with 16.”
So, well we might not consider the decisions to be the best in our opinions, they are at least in line with Vanilla.
So what are these changes that you are trying to use to get your change? How is it nonsense when you are literally using changes that have nothing to do with what youre asking for?
Let’s say they did enact your request. The next change requested uses your same logic. “Changes have already been made so X should be changed too”. Worked for your change didnt it? Why ot for flying, monks, and Dk’s?
That is not nonsense. That is the slippery slope. You can’t say it doesnt apply because your basis for change is “other changes were made” regardless of what those changes are or how they relate to your request.
It was Vanilla. patch 1.12. The whole point was making it as close to how it was. Xrealm bg’s was a part of that.
Again. A 1.12 change. A bit early but non the less was in Vanilla.
This was never a thing. But if youre ok with this then you must be ok with flying, monks, and dk’s because they only make the game better. See how that works?
Because a slight alteration to food buffs aren’t the same thing as entire new races and mechanics the current game world wasn’t built for.
If Activision wants to ruin Classic, there’s nothing magical about a strict “no changes” rule that’s going to stop them from doing that. And if you’re okay with cross-server bullsh*t for no other reason than because it was technically in Vanilla, you’ve completely missed the point of why Vanilla was the superior version in the first place.
It is when that “slight altercation” is used as justification for more changes. Just like you’re trying to do.
If that line of thinking is allowed to stand there is no turning back. Every single change can be justified because “changes were already made”.
I’ve said this for a long time: Any change should be weighed on it’s own merits. It’s effects on the game and the reason for the change.
This project was not about making a better game. It was not about “fixing” Vanilla. It was about as close as possible recreation of Vanilla. That doesn’t leave room for adjusting food buffs.
That doesn’t leave wiggle room for other changes because blizz left the modern mail system.
Yea? That’s in the ToS and has been since Vanilla. It’s blizz IP and they can do whatever they want to it. You agree to that when you click accept. We’ve been agreeing with that since Vanilla.
Sigh. Whether I like them or not is completely inconsequential. Were they a part of Vanilla? Yes. They were. Was there a time in Vanilla without them? Yes. There was. Longer without than with in fact. Both are true to Vanilla. That’s a fact.
It’s not that I’m ok with them because of what they are. I’m ok with them because they were indeed a part of Vanilla.
What i don’t agree with was blizz using them right out of the gate.
They shouldn’t have used them until P6 or until they were “needed”.
What made Vanilla the “superior” expansion is in the eye of the beholder. We can both play this if game.
If you think changing what is authentic, no matter how minor, is going to improve the superior authentic Vanilla mechanics you’ve completely missed the point of recreating Classic as close Vanilla as possible. As orchisly as possible. Warts and all.
Love her or leave her but don’t try to change her.
I’m not playing Classic for the nostalgia. I don’t care how close to “Vanilla” it was in the minor details. I’m playing because it’s the superior version of the game because it lacks changes made later on in expansions that slowly altered it into something completely unrecognizable and inferior in my opinion. I’m not going in for some weird museum piece re-enactment of the Vanilla development cycle sans the actual patches. I want what Vanilla was originally supposed to be before it’s death by a thousand cuts the expansions brought. There’s room there for a minor alteration to food buffs, but no room for crap like cross-server battlegrounds. We should demand an actual experience, not just a dogmatic adherence to some frozen-in-time state of the game with the inclusion of the early entries of very crap that ruined it in the first place.
And, like I said before, if Activision has it in their hearts to shove death knights into classic for whatever nonsensical reason, or really just wanna ruin it for their own ends, they are completely within their rights to do so, and some #nochanges demand isn’t going to stop them. All “no changes” is, is a strong demand from the community for a particular experience. The problem with sticking with a particular patch instead of an authentic Vanilla experience already shows itself when cross-realm battlegrounds are kosher under that logic.
The devil is in the details. Dude. They made a point to show how they reverted lights in the game to be Vanilla like. So I have to say not only have you completely missed the point of this project but you’re not even here for Vanilla experience.
Starting with very small cuts such as changes to food buffs.
Again. You’ve missed the point of the project and want your experience to be what you want and don’t give a damn that others who are here for those very things. The things that are the very scope of this project. As close to Authentic as possible. Naw B.
No kidding? i just told you that. You have literally been agreeing to that for 15 years. It’s not new. If that happens we as individuals will have a choice to make. Thinking that we have to sit here and allow these change requests to be brought up with us as individuals who don’t want your changes staying silent. well you have another thing coming bro.
you’ve said it yourself. death by a 100 cuts. Yet you’re eager to slice right in? Naw B. You want changes go suggest them for retail. keep your knives over there.
So you werent here for all the discussion on patches before launch? Guess what? People wanted patch progression. people wanted static 1.12. People wanted a frankenpatch. People wanted an amalgamation of Vanilla/TBC.
Guess who decided? Blizz because it’s their IP and we all agree to that when we click accept. This is what we got.
Play it or don’t but leave it alone.
And that, friend, is where you are wrong. I haven’t played this game in roughly 10 years and only returned for Classic. After I do some Naxx I’ll probably quit for good if they don’t release some sort of “Old School WoW” and never resub again.
Don’t really care if it was technically in Vanilla or not.