Challenge 7, #1 [GLOGtober]
We interrupt our regularly scheduled posting for this breaking post prompted by this GLOGtober prompt: "Take an old post of yours that you don't like and renovate it."
A Trip Down Memory Lane
My blog is relatively new. I've only had this blog for a month or so. Truthfully, I like all the posts I've made so far.
However, there was a time I had another blog. I had this blog from 2020-2021. It was a small blog of little importance. I would name it or link the post I'm talking about, but I deleted all the posts and the blog itself. The name of the post in question was titled "On Fighters".
Given that I cannot link the post, allow me to briefly explain its contents. This post was a short, off-the-cuff rant about how fighters should be approached now that we are decades away from the original fighter. The basic premise was that every fighter designed should have a niche and that the "fighter" as a class was unnecessary now. Now was the age of the specialized fighter instead, where each fighter fulfilled some niche and was wildly different from the next.
It was a post made in response to a conversation that was going at the time in either the OSR server or Phlox's Glog server. It was little more than a "hot take". It was the best performing post on that blog, the only post to reach over 1000 views.
I hated it.
I didn't hate it because of the content, though my opinion has since changed. I hated it because of the reception. My best performing post was not one I had spent hours on in collecting information and compiling it into a series to share with the world; it was a one-off rant that took me 10 minutes to make. All my other posts never came close to that post, despite the effort put into the other posts.
This is the post I will be renovating.
On Fighters
I do not plan on giving a fighter GLOG class. There are already so many that exist, mine would just be redundant at this point. Instead, I want to focus on fighter as an archetype, which is something that has been floating around in my brain for awhile as I flesh out my GLOG classes.
I am thinking of "fighter" not as a class, but as an umbrella under which classes exist. A class within "fighter" would have something in common with all classes within "fighter". This commonality would signify that a class with it is considered, broadly, to be a fighter.
Perhaps every fighter starts with "fighter die" which they may add to combat maneuvers. That seems to be an inoffensive mechanic which is not counter to the vast majority of fighter classes, nor is it complicated. The only issue may be redundancy, but I think this base would free up fighter classes to explore their niche more without having to use a level template to say, "I'm a fighter".
This would be the "base template" for a fighter class; perhaps a template 0/a/@ or whatever was decided for the template before A. I understand this is nothing new. It is really just "sub-classes" elevated to "classes" and "classes" elevated to "archetypes", but I think it will prove useful down the line in my own hack. It will also allow perhaps another level of specialization. Now that sub-classes are classes, what becomes the new sub-class?
I'll have to think about that more.