Larian Studios Forums Baldur's Gate III Baldur's Gate III - Suggestions & Feedback 5e Multiclassing

In addition to the part where this is how 5e works (and should work), this only seems like a problem to the few people it does because of the easy respeccing.
The easy respeccing devalues a lot of how this game and d&d are meant to work, honestly it would probably be better if it wasn't a thing, or at least far more difficult to make happen.
I could go on about reasons respeccing is actually bad for the game's design, but sticking to the one related to your thread:

No, a Wizard 1 that adds Rogue 1 absolutely should NOT be the same as a Rogue 1 that adds Wizard 1.
They are not the same thing, and should not be regarded as the same thing.
Their precise effectiveness should be different. Their proficiencies should be different.

Main and secondary. Only the class you start as at level 1 is your main class. It's the only class you have a history of being and training.
Any multiclassed class is a secondary class you only just started looking into.

A warlock who decides to start improving their martial training (multiclass into fighter) to go with their decision to take the blade pact boon, should not be as good at martial stylings as someone who focused on martial ability from the first place.
Meaning a warlock, even a bladelock, who multiclass into fighter should not get all the fighter proficiencies. Starting with not getting heavy armor. Their belated training won't get them accustomed to wearing heavy armors the same way someone who was always pushing in that direction.

Conversely, a fighter who's been working on their martial ability the whole time, but later decides to make a pact with some patron, should maintain all the martial skills they developed before making that pact.
Meaning they get martial proficiencies from having fighter as their main class, that a multiclasser won't get.

On both counts, respeccing devalues build choice, because it you decide to multiclass at level 6 (halfway through leveling), you can invalidate the entire notion of having been one class first by pressing Withers's magic button to "rewrite the timeline", and act like you were always something else.
You shouldn't be able to decide at a later level which class you want treated as your main class. Whatever class you actually took first should be your main class, your first class, because it literally was.
The question should not be "now that I'm a wizard/rouge, which do I want to treat as main? Should I respect to be rogue/wizard"
The question should just be "as the wizard I already am, do I want to add rouge and become a wizard main - rogue secondary?" Without any notion of rogue main - wizard secondary being considered an option.

Truthfully, every class should have something that you only get if you start as that class as level one. Something that isn't available from multiclassing into it.
When multiclassing, which class you take first should be a narrative one you make for the story of your character, not a mechanical one you make as a meta choice for your build.
But if you are going to make it for a build, the choice should not be between getting everything or losing something, as it is in some cases now. It should be between which of the main-exclusive things you want to get & not get.