Reply to thread

Message

<blockquote data-quote="EzekielRaiden" data-source="post: 6746010" data-attributes="member: 6790260">Like how it's dumb that we have three races that alphabetize under &quot;half-&quot;, one of which is not actually half of something else? Or how we have two classes that alphabetize under &quot;bar-&quot; despite *both* names having possible offensive connotations? <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink&nbsp; &nbsp; ;)"&nbsp; data-smilie="2"data-shortname=";)" />I voted Sardaukar just for the lulz. I don't see a real need to change the name, but if it's a sticking point, I'm fine with Captain/Commander, Marshal, or Banneret pretty much in that order. The PDK shows up that it's fine to have a (sub)class whose name is context-specific, so I see no reason not to include a comment, sidebar, or subheading on the subject. It's not like space is at a premium for classes that will never be in the PHB.</blockquote>

[QUOTE="EzekielRaiden, post: 6746010, member: 6790260"] Like how it's dumb that we have three races that alphabetize under "half-", one of which is not actually half of something else? Or how we have two classes that alphabetize under "bar-" despite *both* names having possible offensive connotations? ;) I voted Sardaukar just for the lulz. I don't see a real need to change the name, but if it's a sticking point, I'm fine with Captain/Commander, Marshal, or Banneret pretty much in that order. The PDK shows up that it's fine to have a (sub)class whose name is context-specific, so I see no reason not to include a comment, sidebar, or subheading on the subject. It's not like space is at a premium for classes that will never be in the PHB. [/QUOTE]

Verification