i was wanting to know how everyone whos playing both aor and eote is mixing careers how theg using duty and obligation together? would you use both obligation and duty at the same time.

I might. I am going to kick off an AoR campaign I think and the players are going to be involved in the war, but not necessarily true blue patriots so I will be considering that very issue.

i was thinking to use both alongside each other to show that even thougj we help the rebels we still take our smuggling, protection, assassinations,bounty or theft jobs on the side but still fight "the good fight" against the empire.

I may do that as well. We don't view Obligation as negative and use it as a form of meta currency in game. I think the friction and tension of balancing Obligation and Duty will provide great plot hooks.

In my last game, we freely mixed in careers from both EotE and AoR. It worked out pretty well; after all, who says a spy has to work for the Rebellion? And though we didn't get around to using it, I planned to use both Obligation and Duty at the same time, per the instructions in the AoR CRB.

We use both EotE and AoR data, Careers, Obligation, and Duty. Our group is a team of rebel agents with dirty backgrounds. We're sent on missions by the rebels to do things their normal troops can't. Such as, swaying a Hutt to join the rebel cause by doing some of his dirty work. So far using both has worked fairly well.

I think in reality you have to mix EoE and AoR careers if you are including the shady side of things in the war. The same way the US turned to the Mafia in WW2 to prevent labor issues with the east coast longshoremen and obtained intel from Sicily I think apply in Star Wars as well. The underworld in any system is a ready made clandestine organization accustomed and practiced at skirting the authorities.

We're working to clear up any Obligation before officially joining the Rebellion. From a story point of view, the Rebels don't want them bringing their problems and drama along with them since they've got enough problems to deal with.

So all the PCs have to get their Obligation down to zero, at which point they'll be officially welcomed into the Rebellion and will start using Duty instead of Obligation. Seems like a smooth enough transition.

As far as mixing careers from both sources, sure, why not. There's some overlap and maybe some combinations might make peeps a little OP in some areas if they stack a ton of ranks from two very similar permissions, but the GM can police that easily enough if it gets out of control.

The exact campaign I'll be running down the road will use both layered on top of each other. There's many character options that need duty to show progression within the campaign, but from a story perspective have that personal secret eating away at them behind the scenes in the form of obligation.

Additionally the players will have access to a pool of characters they can pull from depending on the exact adventure being played, so a characters obligation and duty will play a larger role. Pick a more skilled and advanced character, and the party's obligation will be higher and more likely to activate or come up negatively in the narrative, or go for a less advanced character with lower skills and fewer talents... but little or no obligation allowing you to run the adventure with little concern for unexpected setbacks and entanglements.