Bake variants into the subclasses; most subclasses will have multiple variants (i.e. Thunder Cannon vs. Lightning Sword)42
Split off variants into new subclasses; most subclasses will not have variants, but more subclasses will be created where necessary.1
{'title': 'Artificer Subclasses: How to Handle?', 'choices': [{'text': 'Bake variants into the subclasses; most subclasses will have multiple variants (i.e. Thunder Cannon vs. Lightning Sword)', 'votes': 42}, {'text': 'Split off variants into new subclasses; most subclasses will not have variants, but more subclasses will be created where necessary.', 'votes': 1}], 'closes_at': None, 'created_at': datetime.datetime(2019, 5, 18, 7, 0, tzinfo=datetime.timezone.utc), 'description': None, 'allow_multiple': False, 'total_votes': 43}
Content
So the problem I ran into with the Artificer 2.0 was that almost all the subclasses started to have core variants with considerable variation. On one hand, it makes sense to make these options a core part of the subclass, and the Alternate Artificer is all about cool options.
On the other hand, part of the idea Artificer 2.0 was to simplify and streamline things a bit, and that was definitely not happening.
So... the options aren't going anywhere, but I have two main paths forward, and I figured I'd ask the people who care the most - you! :)
is only available to registered users.
Visit the
login page if you have an account.
Otherwise visit the
registration page to create one.