Jakau Ryuu
Member
|
Ehh... soft, purely-anecdotal counterpoint to the "most would choose the class over the character" sentiment I'm seeing here? I'm personally keeping Fleshweaver to one character for the immediate future. I'm just too invested in Aegis purely as a character and the potential he presents in-story to make that call for the rest of them, regardless of how strong the class is; I mean, I am absolutely looking forward to seeing what the training process looks like for it, but I still don't think I need to see it more than the one time given all it implies about the gameplay experience going forward. And honestly, doing the class-leveling grind across multiple characters in quick succession got old real quick even when it was just my original Warrior/Rogue/Mage trio way back when, so even if I were to go through it a second time it probably wouldn't be for quite a while anyway. That all being said, I do agree that it feels... unprecedentedly odd that this one single class has these sorts of stakes in the first place, even if it makes sense from a purely-narrative standpoint. Pretty night-and-day from letting the player train Pirate and Ninja when the two factions in-setting are at constant odds with one another, and certainly odd given the player can train all of Paladin + Necromancer + DeathKnight and barely get so much as a side-eye for it. Or, y'know, Dragonlord and Dragonslayer, that's a weird pair too and seems pretty unlikely from at least the prior's general perspective. If anything, this choice is almost more comparable with the base classes being mutually-exclusive with one another outside DC swapping, which... I don't mind it overmuch there either, exactly, but it feels to me at least like a biiit of a relic from the era when the starting classes determined which "variant" of a few other classes the character would have access to (anyone else remember how at least Pirate and Ninja used to swap a few skills out depending on base class, back in the game's early days?) Edit: There's also something to be said about the amount of work an Aegis lockout could create for the team going forward. Best case scenario, if a story beat requires Aegis' presence, either you lock out Fleshweaver characters entirely or you need to write an alternate version around that change, with the easiest form that could take being wildly different dialogue featuring Secundus. And I mean, that sounds cool and all, but that would add to the workload over time, and might disincentivize using Aegis in the plot, period. Not to mention how other Soulweavers et al are likely to respond, as I'm sure the other elemental spirits would notice the sudden disappearance of a character we're informed is fairly important and well-known in their culture, and suspicion would immediately fall on his living ally... so word would probably get around rather quick, which means more dialogue changes or total lockouts whenever we're in a position to engage with at minimum a plurality of a very setting-prominent field of magic. That's either a lot of extra effort that might result in a gradual de-emphasis of something that's seen years upon years of development and focus, or swathes of story inaccessible to some characters, over one player choice that - as has been pointed out - seems fairly out-of-character for the "canon" player-character personality.
< Message edited by Jakau Ryuu -- 9/1/2026 17:06:27 >
|