Senior Member
Lone Wolf Staff
Join Date: Apr 2013
Posts: 688
|
Client changes and improvements
Client bug fixes
Game mechanics
Last edited by Joe; February 26th, 2020 at 10:10 AM. |
#1 |
Senior Member
Join Date: Aug 2009
Posts: 479
|
One step close to what I have been waiting for for PF2... Being able to see my total Fame..
|
#2 |
Member
Join Date: Jan 2020
Posts: 52
|
What does HLO recognize as being a "unique" NPC?
|
#3 |
Senior Member
Join Date: Apr 2017
Location: Wellington, NZ
Posts: 100
|
Without searching for it, I think I read something to the effect of: Unique NPCs retain their damage between encounters. Non-unique NPCs are cloned for each encounter.
🎲 Pathfinder 2e GM Need spawns invention, but imagination gives rise to need. — Logic of Design |
#4 |
Senior Member
Lone Wolf Staff
Join Date: Apr 2013
Posts: 688
|
"Unique" NPCs are typically for named individuals that are characters in your story: Gandalf, Bruce Wayne, Godzilla. They can only be added to the stage once as an individual. They have a property we call "Persistence" that determines whether things HP/spells remaining stay with them after they leave the stage, or whether they are reset. I forget what the default is set to right now (we don't let you modify it yet, but we hope to make that available soon).
Non-unique NPCs are reusable/recurring grunts/mooks, e.g. "Town Guard", "Orc Raider", "Corporate Security", etc. They can be added to the stage multiple times to form ad-hoc encounters, if the players do something unexpected that you don't have a Scene Script prepared for. Non-unique NPCs can never be persisted, so changes you make to them while they are on stage do not get retained on the cast member long-term. |
#5 |
Member
Join Date: Jan 2020
Posts: 52
|
So then, is the "unique NPC" tag (or something) generated by the system when you edit a name, or do they have to be part of the campaign cast?
|
#6 |
Senior Member
Lone Wolf Staff
Join Date: Apr 2013
Posts: 688
|
It's one of the options you can configure on campaign cast when you edit their options (the "sliders" button on the right of each cast member on the cast members view)
|
#7 |
Senior Member
Join Date: Jun 2016
Posts: 204
|
Can we change the default to NOT unique? Find it a bit tedious needing to edit everything I add. Better yet, a checkbox next to the "create character" button to enable unique if that's what you need.
|
#8 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 8,232
|
Quote:
So... The assumption is that "global" cast members are primarily going to be individual NPCs that the party runs into on a recurring basis. For example, the BBEG, his lieutenants, the people that run the world (e.g. nobles), the local merchants (if you opt to spec them all out), etc. Each of those is assumed to a "unique" individual. There are also generic townsfolk that you might want to prepare for re-use, such as bar patrons, beggars, guards, bandits, and the like. Those would NOT be unique, but our assumption is that those are much less frequent than the unique NPCs. Cast members that only appear within a single scene are assumed to be created solely within the context of the appropriate script - as "local" NPCs. They're only used once, so they don't need to clutter up the reusable "global" pool. Now that I've hopefully clarified what our assumptions were, please explain how you're actually striving to use CT. Either we need to better explain the above model or we need to better understand what you're doing so we can make appropriate changes to accommodate the unexpected usage pattern. Or both. Thanks! |
|
#9 |
Senior Member
Join Date: Sep 2018
Posts: 305
|
Quote:
Say the PCs are walking down the street in a town-- who are they more likely to bump into: the Mayor, or a common merchant or beggar? Or, say the party is delving into an evil necromancer's dungeon-- who will they likely spend more time fighting: the Necromancer himself, or his hordes of undead minions? If you're prepping an encounter with a goblin raiding party, would you really spec out unique statblocks for every individual goblin? I certainly wouldn't... I'd make most of them generic "goblin warriors" and call it good. The leader of the band might be more powerful-- and he might even have a name and a backstory-- but even then he probably wouldn't need unique stats, just a generic "goblin lieutenant" statblock. Surely those kind of encounters are more common than ones involving unique monsters or NPCs, no? Last edited by dacoobob; March 6th, 2020 at 01:54 PM. |
|
#10 |
Thread Tools | |
Display Modes | |
|
|