2:18 AM
For Threads
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Location: This one's rather obvious, no?
Canon: Because once in a while we deviate from BtB, so clarity is good?
Warnings: Are there any spoilers or possible triggers?
Summary: Elaborate or be brief. Whichever works best.
Notes: Whatever you want here. Be sure to mention if it's private or a narrative.
For Networks
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Canon: Because once in a while we deviate from BtB, so clarity is good?
Encryption: Compound (Alliance can read if they dig for it) or Safehouse (Alliance can't read) are the two main ones
Filter: Privated to anyone specific?
For Multi-Scene CRP
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Location: This one's rather obvious, no?
Canon: Because once in a while we deviate from BtB, so clarity is good?
Warnings: Are there any spoilers or possible triggers?
Summary: Elaborate or be brief. Whichever works best.
Notes: Whatever you want here. Be sure to mention if it's private or a narrative.
Fancy Formatting: Here is an example of the first thread to use this format. It is meant to take large, multi-scene CRP threads and turn them into something easier to read - almost like little ebooks of awesomeness.
CRP Colour Codes:
Sorcha: </font><font color="#7A95FF">
Mandy: </font><font color="#CC00FF">
perkyshadowgirl: </font><font color="#CC00FF">
For Extremely Long Posts
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Location: This one's rather obvious, no?
Canon: Because once in a while we deviate from BtB, so clarity is good?
Warnings: Are there any spoilers or possible triggers?
Summary: Elaborate or be brief. Whichever works best.
Notes: Whatever you want here. Be sure to mention if it's private or a narrative.
( Cut text goes here. )
This is primarily for multi-scene posts which exceed IJ's post length limit. Properly format and post it onto DW, then link to the post here.
Ideally, make the headers and cut text identical between the two versions of a thread.
For Videos
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Canon: Because once in a while we deviate from BtB, so clarity is good?
Summary: Explanation of the video, and why it's being posted
Link: Link to the video
AU?: What - if anything - in this thread can be carried over into canon?
Original Chatlog
This is a nifty way to display the original chatlog when expanding a chatty concept into a full-blown thread or narrative. You click on the "Original Chatlog" button, and it displays or hides the original inspiration used when making the post. Here is an example of a thread using this code.
For Comparative Canon Divergences
This is a fancy format for showing divergence doc style 'this is canon and this is divergence' - useful in the case of setting the tone for a quick CRP etc. Here is an example of a thread using this code.
For Exposition Setup
This is set up to be like a 'previous episode' recap, including space to dramatically show off a quote. This might be useful for calling back to a previous thread or an event in a canon etc. before a narrative or as part of a thread starter. Here is an example of a thread using this code.
Horizontal Rule (Plain)
Just a plain, grey horizontal rule that looks nicer than the hard-to-see default in browsers. Useful for section breaks.
Horizontal Rule (Fancy)
A fancier, grey horizontal rule with a slight shape and center alignment. Looks nicer than the hard-to-see default in browsers. Useful for section breaks.
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Location: This one's rather obvious, no?
Canon: Because once in a while we deviate from BtB, so clarity is good?
Warnings: Are there any spoilers or possible triggers?
Summary: Elaborate or be brief. Whichever works best.
Notes: Whatever you want here. Be sure to mention if it's private or a narrative.
For Networks
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Canon: Because once in a while we deviate from BtB, so clarity is good?
Encryption: Compound (Alliance can read if they dig for it) or Safehouse (Alliance can't read) are the two main ones
Filter: Privated to anyone specific?
For Multi-Scene CRP
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Location: This one's rather obvious, no?
Canon: Because once in a while we deviate from BtB, so clarity is good?
Warnings: Are there any spoilers or possible triggers?
Summary: Elaborate or be brief. Whichever works best.
Notes: Whatever you want here. Be sure to mention if it's private or a narrative.
Fancy Formatting: Here is an example of the first thread to use this format. It is meant to take large, multi-scene CRP threads and turn them into something easier to read - almost like little ebooks of awesomeness.
CRP Colour Codes:
Sorcha: </font><font color="#7A95FF">
Mandy: </font><font color="#CC00FF">
perkyshadowgirl: </font><font color="#CC00FF">
For Extremely Long Posts
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Location: This one's rather obvious, no?
Canon: Because once in a while we deviate from BtB, so clarity is good?
Warnings: Are there any spoilers or possible triggers?
Summary: Elaborate or be brief. Whichever works best.
Notes: Whatever you want here. Be sure to mention if it's private or a narrative.
( Cut text goes here. )
This is primarily for multi-scene posts which exceed IJ's post length limit. Properly format and post it onto DW, then link to the post here.
Ideally, make the headers and cut text identical between the two versions of a thread.
For Videos
Characters: Because the obvious isn't always obvious.
Time/Date: Rough approximation or relation to other events in same canon are fine when specifics aren't available.
Canon: Because once in a while we deviate from BtB, so clarity is good?
Summary: Explanation of the video, and why it's being posted
Link: Link to the video
AU?: What - if anything - in this thread can be carried over into canon?
Original Chatlog
This is a nifty way to display the original chatlog when expanding a chatty concept into a full-blown thread or narrative. You click on the "Original Chatlog" button, and it displays or hides the original inspiration used when making the post. Here is an example of a thread using this code.
For Comparative Canon Divergences
This is a fancy format for showing divergence doc style 'this is canon and this is divergence' - useful in the case of setting the tone for a quick CRP etc. Here is an example of a thread using this code.
For Exposition Setup
This is set up to be like a 'previous episode' recap, including space to dramatically show off a quote. This might be useful for calling back to a previous thread or an event in a canon etc. before a narrative or as part of a thread starter. Here is an example of a thread using this code.
Horizontal Rule (Plain)
Just a plain, grey horizontal rule that looks nicer than the hard-to-see default in browsers. Useful for section breaks.
Horizontal Rule (Fancy)
A fancier, grey horizontal rule with a slight shape and center alignment. Looks nicer than the hard-to-see default in browsers. Useful for section breaks.