Powermaster Prestige Class Notes
-
It occurs to me as I have been doing a little optimizing this morning, that in 2E the powermaster had what was characterized as having a processor and a co-processor for each class, and a physical processor with a co-processor for a total of four brains.
The physical processor is where you did your standard attack action (waving your sword about), the physical co-processor was really only ever used by Daren for additional movement or other sort of move-related things like picking up weapons that sort of small easy thing to do. The other processors in 3.5 lingo, are where you do your standard casting action, casting spells, magnification, spell amalgamation (i.e. the heavy lifting of spell casting abilities).
Do we want to call or consider what was referred to as a co-processor in 2E, a swift action in 3.5; are they synonymous?
-
@halfgiant said in Powermaster Prestige Class Notes:
Do we want to call or consider what was referred to as a co-processor in 2E, a swift action in 3.5; are they synonymous?
As an unrelated note, if I remember correctly that is how I played 3.5 Sazerac previously. I have no memory of socializing that however, I may have just done it.
-
the initial build of the powermaster had 3 primary processors - one for each “spellcasting” class, mage cleric and psion. i think it was the 3rd or 4th gen where a “physical” processor was added - for melee, movement or whatnot. a few generations after that, a set of 4 co-processors was added, taking the load off the main brains for minor actions like ongoing spell concentration, shifting targets, gem actions, refreshing stoneskins, etc. the co-processors are limited to self/personal effects only - fiddling and diddling with things running in the background on the powermaster himself.
so, for example, if Daren was casting a prismatic spray at some lich that pissed him off, triggering the lich’s dim-door contingency - a coprocessor could re-target the ongoing spell and hit the bastard anyway (provided he was in range, obviously), but the coprocessor isn’t “smart” enough to initiate the casting in the first place as it involves both casting and targeting (a non-personal effect).
