[ SECRET POST #4099 ]

[case]

⌈ Secret Post #4099 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.

01.



__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.













Notes:

Secrets Left to Post: 02 pages, 46 secrets from Secret Submission Post #587.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

Re: Pairing preferences in a fic

[(Anonymous)]

I'm mainly going to be into A/B and want most of the focus to be there, but some A/C along the way is not out of the question, although it depends.

If A/C is a canon pairing, then it may be necessary to the story to end that relationship somehow before moving on to A/B. I don't mind it if the writer just ignores A/C entirely, but depending on the story, it might make more sense to just deal with it. I don't like it when this means trashing C, though, even if I don't particularly like C. It depends on the canon context and how the author handles it. Relationship breakdowns are fine, as long as it isn't portrayed as being entirely C's fault.

If A/C is not canon, including if C is an OC, but I don't ship A/C, it's still fine, but I don't want a story that's 99% A/C only for A and B to suddenly get together at the end. If I go looking for an A/B story, then want to read about the build-up to A/B and the interactions between A/B, not about A/C. Besides, stories that are mostly pairing A/C but with A/B as endgame tend to be about why A/C is so wrong for A and A/B is what's supposed to happen (but without putting in the work with A/B). If I only want A/B, then I want to read about why that pairing *should* happen, not why other non-canon (and sometimes canon) pairings *shouldn't* happen.

If I ship A/C in addition to A/B, then it's all good.

For the purposes of tagging, both pairings should be tagged in all cases.