Jeremy Crawford Reveals Why One Popular D&D Class Won't Be In The 2024 Player's Handbook

screenrant.com:

While a new for is in the works, a statement from developer Jeremy Crawford has explained why one popular class from 5e won't be making its way into the newest edition. While the fifth edition of has seen several new subclasses, rulings, and settings added to it over the course of its lifetime, the 2024is starting out with a relatively smaller selection — and while developers have promised that the changes will still be compatible with 5e, some choices may still prove to be unpopular.

As confirmed by Jeremy Crawford at the panel at Gen Con 2024,the Artificer class won't be a part of the 2024, which will instead opt for the same 12 base classes as 5e. Expanding on why the class won't be available, Crawford stated that "," going on to explain that the developers felt that the class was somewhat too niche to fit into the default handbook. Crawford also made clear, however, that Artificer will be officially reintroduced in the future, saying that there are "."

Although most of D&D 2024 is made up of tweaks to 5e, one new addition is groundbreaking and could change the way people play the game.

Since its introduction in supplementary materials for 5e, Artificer has been a popular class for many players, with a large part of the community supporting its inclusion as one of the default classes going forward. As only the second class to make use of the Intelligence attribute, and with a unique flavor to distinguish it from other spellcasters, Artificer fills an important niche for many players who want something outside what the default 12 classes have to offer.

However,the unique flavoring of Artificers as magical inventors and tinkerers can also make it a hard class to fitinto every possible setting, which makes the decision to leave it out of the 2024understandable. In addition, with the newest handbook for making major changes to most of the 12 classes represented in it, the work required to bring Artificer in as a default class was likely deemed too much, and it