faderifting: (Default)
Fade Rift Mods ([personal profile] faderifting) wrote in [community profile] faderiftooc2019-08-27 09:12 pm
Entry tags:

MOD POST ↠ SEPTEMBER ASSIGNMENTS

SEPTEMBER ASSIGNMENTS

Assignment teams and details will be posted and linked as they're determined.

Follow That Baron - Overture: Athessa, Isaac, Leander, Mhav, Romain
21 Jump Street: Kaz, Derrica, Laura, Tavin
Tis I, a Humble Capitalist: Ilias, Darras, Mhavos, Silver
Burning Bridges: Lino, Yngvi, Kostos, Nell
Amaranthine Jones & the 100 Pillars: Eshal, Freddie, Wysteria
Lend Me Some Sugar: Athessa, Bastien, Coupe, Fitcher
Not in My Crossroads: Barrow, Anders, Matthias, Derrica
There's Something About Larry: Alistair, Flint, Yseult, Lino
Dragon Rage Origins: Aziraphale, Julius, Val, Mhavos
Test Flight: Teren, Nikos, Marcoulf

If you didn't sign up for assignments and wish you had, we'll have more next round (or sooner)! And if you did sign up for assignments and wish you hadn't, hahaha sucker.

Jk, just let us and your teammates know if you need to back out for any reason.

RULES

OOC, the only two rules regarding these assignments are: (1) they must be RPed in some way, not entirely handwaved, and (2) you have to file a report by the deadline. Otherwise, you can handle them basically however you want. For example,

Format: You can write a log addressing the main action/meat of the assignment, handwave that and do a log or crystal post that’s instead focused on deciding what to do about the problem or discussing how it went after the fact, or whatever else, as long as you RP about the assignment’s substance in some way.

Personnel: You can limit the assignment to only the assigned team, if you prefer, or you can take other people along, whether that means involving just one other specific character to go for some specific reason or turning the assignment into an open log/discussion that the whole game can participate in. Just make sure everyone on the team is on board with whatever you decide, and check with the relevant project leaders or division heads if you want to include someone whose suitability for something is in question, since they might not be willing to OK their inclusion.

Content: If you want to add obstacles, problems, pit stops, etc. to your assignment, you can, as long as they’re reasonable given the scope and spirit of the assignment. For example, if your characters are tasked with finding a lost child in the woods, it’s fine for them to accidentally wander into a bear’s den or to get caught in a storm that causes a flash flood in a ravine, because those are hazards that make sense given the assignment and its setting, whereas finding a zany artifact that causes bodyswaps or assassinating Corypheus would be outside the scope.
coquettish_trees: (letters 3)

FOLLOW THAT BARON

[personal profile] coquettish_trees 2019-08-28 04:31 am (UTC)(link)
TEAM: Athessa, Isaac, Leander, Mhav, Romain
DEADLINE: October 31

MISSION: The infamous Baron Deshaies. Go and find out if he's a Venatori loyalist who did it For The Cause, if he got blackmailed into it, or if he's just a traitorous opportunist (chase that paper).

BRIEFING:
I trust none of you have forgotten the illustrious Baron Deshaies. What exceptionally terrible security he had in his home that the Venatori were able to simply waltz in and make off with his honored guests! Let us help him address that.

We yet neither know how he became involved nor who involved him. That is to be your task. We have let some time pass such that he will likely have relaxed his guard somewhat, allowing for closer surveillance. Go and see who it is he keeps company with, his movements, whatever will allow you to find out if he was a willing accomplice or had his hand forced. If this was a singular event, or if he continues to keep such bedfellows. How it is they initially got in contact and how it is they remain, if they do.

To those of you directly impacted by his betrayal, I urge you to remember: whatever else he is, Deshaies is still a Baron of Orlais. Step carefully, find proof, and give Her Radiance no cause to be wroth with us.

DETAILS: Making your way (or returning) to the Baron's property won't be too much of a problem. What does pose a problem is how to go about accessing it. You might...

  • sashay in the front door and attempt to speak directly with the man himself
  • have a stakeout and observe the comings and goings of the estate
  • go in stealth and rifle through all his things
  • combine these!
  • something completely different!

    What all you'll find out depends on how you decide to approach the situation, so discuss amongst yourselves and let me know what you're doing and I'll tell you what falls out when you shake the tree.

    Alternately, if you'd prefer to know all available information up front and make your decision that way, you can let me know that too, and I'll just info-dump you and you can sort it out from there!
  • wythersake: (Default)

    [personal profile] wythersake 2019-08-28 11:49 pm (UTC)(link)
    Hello! We've discussed and the rough plan is:

  • Romain, Leander, and Mhavos will go in the front door.

  • Mhavos will be posing as Romain's servant, and use this as an excuse to talk to the other servants.

  • Athessa will enter by stealth, using the three of them as a distraction, and rifle around the Baron's things.

  • Isaac will hang around outside at a distance, to keep an eye on immediate comings and goings (though not to the length of a full stakeout). If it looks/sounds like Athessa's about to get murdered, he'll send a condolence letter. Or help her get out, I guess.

  • Off-screen, Romain will be using his connections as a Duke to attempt to bribe/intimidate for info.
  • coquettish_trees: (letters 3)

    [personal profile] coquettish_trees 2019-08-30 02:54 am (UTC)(link)
    A good plan plus I rolled a heck 20 means you get all the things!

    Isaac's distance position will allow the team to be well aware that our friend is not in the château, but saddling up suspiciously quickly for a 'hunting expedition'. This will mean that the front door crew will be able to avoid all the stalling/misdirection from the staff and catch him out.

    Caught this way, Deshaies will straighten up and lay it out. His motivations were self-protective: his land lies right in the path of the invasion (should it push further south), and he was being proactive in saving it from such a fate via making this deal with the Venatori. He has his family to think of and a responsibility to protect those who live and work on his land. He'll swear up and down that he's made no further dealings with them and is willing to tell you how to contact/locate his Venatori handler for your own purposes as well. Given the presence of one (1) intimidating Duke he'll even offer to set up the meet himself, to His Grace's--er--Riftwatch's specifications. Please don't kill him or tell Celene.

    From servants, Mhavos will find out: the names of two other minor nobles (randomize their names pel i know you have the power!) who began frequenting the estate and Deshaies' company around the same time, one of whom once notably absolutely lost it at a servant for walking into the room where they were talking to bring refreshments. Nobody will say these things are suspicious, of course, but that's because nobody has to.

    From doing crimes, Athessa will find: A nice little treasure trove of correspondence that could definitely be used as concrete proof, should you all decide to tell Celene, along with some documents that are obviously ciphered and some that are not but are so vague as to be immediately suspicious.

    --

    If you now have additional questions, let me know! Nice work, gumshoes.