Monstrous Compendium Vol. 1: Spelljammer Creatures
Frozen Sick
D&D Beyond Basic Rules
Basic Rules (2014)
Sign in to view your library & saved favorites.
Sign in- Marketplace
Monstrous Compendium Vol. 1: Spelljammer CreaturesFrozen SickD&D Beyond Basic RulesBasic Rules (2014)Sign in to view your library & saved favorites.
Sign in
And prior to Xanathar’s there weren’t any “setting agnostic” classes outside of the PHB, and yet somehow people managed to homebrew settings just fine.
That’s a fair point, but in this instance it at least seems to be a solid body of general purpose subclasses, magic items, and possibly a secondary background system to work with rather than just one or two subclasses.
I genuinely think that this is really about the mild inconvenience of 2014 Swashbuckler-centric 2024 Rogue "builds" no longer being RAW in general and/or supported by DND Beyond.
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
Again, there were 10 years where 5e was the primary system. Swashbuckler was released in 2015. Tashas came out in 2022. The vast majority of that time, the Swashbuckler was a "setting-specific" subclass, to use your inaccurate terminology. It stil hasn't been setting agnostic for longer than it was only in SCAG.
And just like when it was in SCAG, you can use it in any setting without having to use that setting. I've got a new Hollow Warden in one of my FR games, and she's certainly not in a Domain of Dread, yet it works just fine.
While I would like more settings agnostic books, that's because I want more mechanical content, instead of pages of lore. Having subclasses in settings books in no way at all prevents them from being used wherever you feel like it. It's a non-issue that people are desperate to be outraged about. Azeroth is probably one of the most D&D-esque third party settings you'll ever find.
We already have precedent on that subject, and you can still select legacy bladesinger on a wizard. It seems not unreasonable to assume this will continue.
We have precedent, & that the newest official version must be used at a RAW/AL table. There's a not-insignificant amount of people who feel Swashbuckler's 2024 update being locked behind giving Microsoft money in residuals will hurt their meta build(& internet reputation), & that this move by WotC is targeting their wallets because of their commitment to RAW(& commitment to minimal harm(sic).
They think that they can't play 2014 Swashbuckler at their RAW table if the new RAW is locked in a collab w/a(nother, given that WotC isn't exactly liked by some due to the Hasbro connection(Personally, guilt by association is BS)) bad company(That makes them look bad to others by association).
In the end, it's not just the RAW tables being affected. It's also a possible source of guilt by association(Which is BS) for some people because of the Microsoft connection.
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
I think there's a lot of people who are both massiverly overthinking it, and also overhyping the "issue".
I don't see people abandoning Candy Crush editions because "Microsoft residuals".
Yeah, while Maedra's experience might obviously be different I don't see a lot of people gnashing their teeth with guilt over using Microsoft products considering they're the largest supplier of the type of software we all use at work and one of the main producers of entertainment software.
Will the WoW book be allowed in AL at all? Answer hazy, ask again later.
As for "RAW tables". I'm sure they exist.
I also don't care about either one. They're an extremely tiny subset of actual play, of people playing under weird (and in at least one case, impossible) constraints.
If people want to play in such a way that they force themselves to use only the version in the WoW book, they can get the WoW book.
In normal play, either somebody will have the book, and you can use the subclass, or nobody will say boo about you using the old one.
...
What?
If you have principles that require you to boycott everything Microsoft-connected, then don't play new swashbuckler. Given everything else you've got to do to do so, avoiding a single D&D subclass is small potatoes. Having principles isn't free.