I have a player who's obligation is Obsession. He is a droid who served as an assassin during Order 66. He was heavily damaged in a fight and was deactivated. 15 years later he was reactivated but lost much of his previous programing. He is now "obsessed" with figuring out what happened to his old programming and being the best assassin and combat droid in existence.

If I roll his obligation, how should I use that?

There are a few ways you could go about it, off the top of my head whilst spooling down for sleep, though;

He could perhaps run into a droid of the same make and model as he is, or happen upon a site owned by the person or company that developed him.

I have a player who's obligation is Obsession. He is a droid who served as an assassin during Order 66. He was heavily damaged in a fight and was deactivated. 15 years later he was reactivated but lost much of his previous programing. He is now "obsessed" with figuring out what happened to his old programming and being the best assassin and combat droid in existence.

If I roll his obligation, how should I use that?

Incorporate it into your sessions going forward. I typically don't use someone's Obligation trigger in the session it triggers other than the mechanical effect. I use the details of it in following session(s). I actively farm Obligation and build my campaign ideas around what the PCs choose for their Obligations. It makes it feel more organic to the story and not like some mechanical feature tacked on as a sort of 'in addition to' kind of effect.

Introduce him to the HK series assassin droids via clips off YouTube.

Eventually let him find out he was originally built as an inferior copy of the original during the KOTOR MMO era that HK destroyed itself.

Recovered by the Separatists he was rebuilt as a standard battledroid but surviving the clone wars they eventually grew dissatisfied with their current state and used a number of antiquated parts to upgrade itself one of which included a recording of the HK training protocol leading to their current delusion.

The true fact is that they are much more than they thought but they aren't the HK Assassin droid they thought they were...

I have a player who's obligation is Obsession. He is a droid who served as an assassin during Order 66. He was heavily damaged in a fight and was deactivated. 15 years later he was reactivated but lost much of his previous programing. He is now "obsessed" with figuring out what happened to his old programming and being the best assassin and combat droid in existence.

If I roll his obligation, how should I use that?

Incorporate it into your sessions going forward. I typically don't use someone's Obligation trigger in the session it triggers other than the mechanical effect. I use the details of it in following session(s). I actively farm Obligation and build my campaign ideas around what the PCs choose for their Obligations. It makes it feel more organic to the story and not like some mechanical feature tacked on as a sort of 'in addition to' kind of effect.

So we roll Obligation and my Zeltron Entertainer's (Nomi Long) Obligation trips. I know he owes some debts to a privateer ship captain, Zeemo the Hutt, and a Zygerrian slaver baron. I put that in the back of my head during the current session, and my next session I will use one of those aspects of his Obligation to form the session's story. I run my sessions episodic and I like to wrap things up each session. However, even if they were on some other longer mult-session 'quest' and it triggered, I'd simply make some element of the story next session involve their particular Obligation. So the mechanical impact I apply in the session it is rolled, and the narrative just waits until the following.

Now if Obligation didn't trigger the previous session and I've planned something unrelated, if it does trip in the current session, and that particular PCs applies, I can just swap a name for an adversary easy enough and incorporate it on the fly during the session.

I also don't wait only on the rolls to use it. I actively use the PCs Obligations to form my story ideas. When I laid out the campaign to begin with, I told them for CHARGEN, think down on your luck, from the wrong side of the tracks, running to Hutt space to avoid problem X, your last few credits in your pocket and you wind up in some two but gin joint off the spaceport to start drinking your sorrows away...

I use Obligation as a meta currency and there was rarely a session where someone wasn't losing some and the group wasn't gaining some.

Ok. So I've decided that because the story is broken up into acts I'll roll obligation at the beginning of each act. Then at the end of the act something will happen.

If his programming is "broken", then his self-repair systems are likely to be trying to recompile it. Memories or commands could re-surface at any time.

If his programming is "broken", then his self-repair systems are likely to be trying to recompile it. Memories or commands could re-surface at any time.

1. His first combat against a Fallen Jedi he will do a hard computers check if it works then any combat checks against a Force user will get a boost die.

Or

2. We have a mechanic in our group he can do a daunting mechanics check or hard computers check and try to find it.

Something to consider - roll for Obligation at the end of each session, for the upcoming session. Buy yourself a little time to plan things out, instead of trying to come up with something on the fly.

It's a big help.

I find it useful to try to keep Obligations to be more literal and leave the motivations up for interpretation. So, for example, Addiction would stay strictly to being addicted to like death sticks or something along those lines. Whereas motivation like Ambition, Love could be interpreted to be something as different as a love of some object they had left in their dwelling place.

It works very well for me, it gives the group a uniform standard that they have to stick to.