There, that’s my counterargument. A statement and then an explanation that backs up that statement. It has just as much substance as your “arguments” which is to say, none. But I stated my argument and explained it. So now you have to debate me.
I guess we should skip pretending to do TBCC then and just release WoTLKC already?
Dual spec in TBC is not comparable to dual spec in WoTLK.
You can use your argument to say any future feature is tried and true and transferable to TBCC - which is clearly not the case. Deathknights are very popular, tried and true - have been in every future edition of the game since after TBC, why not add them to tbcc? Clearly it’s well known and risk free right?
So developing dual spec took longer to develop than much of the content of an expansion? Such that they had to release it 3 months a part?
It is possible that they didn’t prioritise the feature as highly as other features. But to me it also makes sense that they waited until the sweeping class changes and grouping changes they made in the expansion release were properly raid tested in live first before determining that the time was right for the release of such features as dual spec. This seems a very reasonable approach to me. It’s conjecture on both our parts. But we know they didn’t release it in TBC and in fact gave strong arguments as to why they wouldn’t.
Obviously it doesn’t fit your premise that the devs were concerned about dual spec having game balance implications. But I think you’re just glossing over that to suit your argument that it’s a risk free change. A baseless argument btw. I mean you maintain it is risk free simply on the basis that later expansions had it.
Some were transferred. If you started D2 with LoD installed things like bag space and bank were updated with the LoD changes. It’s been a long time since I played those games so I don’t recall all the changes added to D2 from LoD but there were several. I’m sure those who pay more attention to that type of thing could make a list.
That was a change they gave reasons for, reasons other than - future features are fully backward compatible.
I’m not claiming that no future feature is backward compatible, I’m claiming that you can’t assume that they are. There needs to be independent reasoning for implementing such a feature beyond “it worked in Wrath”.
If I’m the one making the assertion it’s contradictory - but I’m not. You’re claiming that the feature worked in WoTLK and is therefore compatible with TBCC, it’s been tested in the later expansion and it can, as a result, be assumed to be fine for TBCC (according to you).
I’m simply challenging that assertion by suggesting it is not a given at all. It MAY be compatible, or it may not. Simply being something used in a later version does not make it compatible with TBC and by extension TBCC. So, that fact that there have been other changes has no bearing on this at all. This change suggestion needs to be defended on its own merits.
Day 187. After slowing for a short time the dual spec debate has gained momentum once more. The reasons are elusive as there still no cause, good or otherwise, for dual specs to come to TBCC.
PS: Please forgive my use of the word “debate” as it anything but that, Im just contradicting myself to save time.
You’ve been asked to explain in detail why you think it’s not compatible, given we know exactly how TBC works and exactly how dual spec works you should easily be able to do so.
Because you haven’t demonstrated to my satisfaction that it is compatible. It’s your claim - you prove it.
And we don’t know how they work together. You’ve got a gut feeling they’ll work fiiiine. Good for you. I’m not finding your gut feeling convincing. I don’t need to prove why I have doubt beyond establishing that you have no evidence for your claim.
Edited after replies as an example.
Your example is like this:
Stones are a feature on the same planet as earth and as water. Given that we know stones sit on top of earth we know that they float on water as it’s all the same feature on the same planet.