Larian Studios Forums Baldur's Gate III Baldur's Gate III - Suggestions & Feedback Wizards spells from any class list?

I can teach a wizard any spell from any class spell list.
In regular DnD 5e, wizards can only scribe wizard spells into their spell book. With this change, I feel like other casters (warlocks etc) don’t have anything making them as enticing as a wizard! Why be a warlock or a cleric with a limited spell list if I can just be a wizard and cast literally whatever I want? The versatility is through the roof compared to the already-versatile wizard of regular 5e.

This was reported since day one. Every patch I wait for them to fix it. This and the fact that everyone can use scrolls.

It would make sense if this was done for universally testing spells during EA.
Larian not mentioning anything about it is worrying.

Its probably not a bug, more like a feature the threw in like the rest of dumb junk.

All this and the ability to change memorized spells at will.

These changes should come when the Sorcerer class is added to the game at the latest. Otherwise what's the point of a Sorcerer to begin with if Wizards can learn even Cleric spells and can switch their memorized spells at will.

Scrolls being free for all isn't good for the game either. It makes magic feel mundane and spellcasters far less special or needed. You should have at least SOME understanding of magic through multiclassing or a feat to unlock scroll use.

Magic in BG3 ties directly into the resting system as well. It does trouble me that Larian have made zero comments about magic system or resting. I can't help thinking they want to change all of it towards a classless/DOS system because they think less restrictions automatically mean more fun.

I like this, I like wizards being able to learn any spell off a scroll... I like it a lot.

And every character should be able to use scrolls, this was one of the worst design decisions in D&D 5e... so much so, that they created a new magic item in Tasha's in the form of spell tattoos that mimics the most common homebrew functionality of scrolls.

I do too, though I know it's not True DnD by a long shot. We should enjoy it while we can!

It sort of feels like this diminishes the specialisation/flavour of each class though if everyone can use scrolls (it's already bad enough with how the current combat mechanics do this to a degree as well).

Was it the case that in previous editions of DnD each class could use scrolls? I don't remember that being the case in previous BG games?

In 3.5 you could train a skill "Use magic device" that would allow you to ignore restrictions, and attempt to cast a spell from a scroll. But it was a roll every time you try to use it.

Allowing everyone to use scrolls gives players more freedom. But it blends all classes.
Spells are the main reason to play a spellcaster. Now, if my battlemaster can use a scroll to fill thet role, why would I use a wizard that is squishy?
And the system isn't symmetrical. For wizard to get access to battlemaster maneuvers he has to burn a feat.

Wizards are all about mastering magic and seeking out forbidden lore and stuff they couldnt learn normally. I have incorporated a rule at my table that lets wizards add any spell to their spellbook, if they have a scroll or a way to find that spell... but they have to pass an arcana check (in normal 5e, wizards have to pass an arcana check to add spells on a scroll, but only wizard spells... I remove the check for wizard spell scrolls, but kept it for non-wizard spells... representing a challenge to master things outside of what wizards know)

It has worked wonderfully at my tables and has done a lot to provide motivation to my wizard players to seek out the magical places and people of the world.

As for the blending of classes? I dont know, maybe spell saves and attacks should be MUCH LOWER, like ridiculously low, for non-casters using scrolls? and casters should just use their own modifier?

Apparently, they are going to fix that bug that wizards can cast any spell, which is DEFINITELY GOOD. Otherwise, why even bother having classes?

booo

In D&D you multiclass or spend feats to get other classes abilities like using scrolls. I see no reason to hand out that ability for free since it's already mechanically possible in a way that makes sense. I'd like to think magic is more than just reading some words in common from a scroll. Casting spells shouldn't be that mundane.

The divide between arcane and divine magic in D&D is very clear as well. I don't see any need to let Wizards start casting healing spells. It just makes both Wizards and Clerics less distinctive and overpowers one class at the cost of another.

Yes, of course. It's gotta be a bug.

It's a bug confirmed as a known issue to be fixed.

I logged a bug report and was given this response.

It feels like something that's fine for now and fits in with a different flavor of Wizards that is still cool but will get horrendously broken as the game goes on. If it's not fixed before the level cap is raised then there's a real problem.

Did you have other caster classes in the party? Wasn't they feeling robbed of their stuff? I know I would have been.
What do you think about giving every character the ability to hide and disingage as a bonus action? What are the thoughts of a rogue player?

It feels like a big problem right now, for me. I would much sooner get rid of scrolls entirely than keep them as they are. Ideally, they would be extremely rare (maybe you would see half a dozen spell scrolls throughout the entire game).

The existing consumable-happy approach robs the classes of their uniqueness, which sucks much of the fun out of the game.

My point of view;
Being RESTRICTED (class advantages/disadvantages for example) is what makes a strategic RPG game fun.
Having NO RESTRICTION is what makes an arcade/ action rpg game fun.

Just to temper your expectations going forward, please be aware:

While, as Scribe says, this is now considered a 'bug' that will be 'fixed', this is a new development.

Previously, this was not considered a 'bug' and was indeed reported by the bug response team as being working as intended (at least it was so in my earlier bug report dialogues, which were much earlier than Scribe's more recent and up-to-date ones.) This was part of their original plan, quite deliberately done.

They've now declared that it is going to be changed, and so, going off Scribe's more recent report, are also calling it a bug now.

There's a couple of take aways from this, one good and one less so. The less so is that it's another illustration of their dubious design philosophy. The good side is that this is apparently one place where they *have* actually buckled to fan pressure and agreed to change something based on overwhelming community feedback.