From 710f57bca1cc3ab78fcae8aba9119c261644dd35 Mon Sep 17 00:00:00 2001
From: DCoded <dicoded@email.com>
Date: Sat, 15 Oct 2022 21:21:47 -0400
Subject: [PATCH] Removed old stuff
---
devNotes/scene guide.md | 183 +---------------------------------------
1 file changed, 1 insertion(+), 182 deletions(-)
diff --git a/devNotes/scene guide.md b/devNotes/scene guide.md
index 948f8736f43..dcbd72ff05e 100644
--- a/devNotes/scene guide.md
+++ b/devNotes/scene guide.md
@@ -10,11 +10,6 @@ If you would like to view examples of scenes currently in the game, there are qu
Writing a scene is similar to writing any other code for Free Cities; each scene should be a JavaScript function that returns either a `string`, `DocumentFragment`, or an `HTMLElement`. This main function can then be further broken down into subfunctions to increase readability.
-<!-- Most writing is basically just plain text with branches for different cases.
-Important cases to remember:
-
-It's important to handle every RELEVANT variation of the above cases. Depending on what you're writing, other cases may also warrant consideration; e.g. a breast-play scene will probably need to account for breast size and lactation a lot more than a generic fuck scene. If a scene only applies to a specific type of slave, you can restrict the cases you account for to the ones that are only possible for that type of slave. -->
-
### Considerations
When writing a scene, make sure you properly cover different variations of the event. Here are some things to keep in mind:
@@ -33,22 +28,6 @@ When writing a scene, make sure you properly cover different variations of the e
### Structure
-<!-- There are, broadly speaking, two main ways to do this:
-
-1. Write the same big block of text and then copy/paste it into each relevant case, and tweak the wording slightly.
-
- ++Less thinking required
-
- --LOTS of duplicate text; if you need to change something later, you have to change it in many places
-
-2. Decompose the scene into smaller segments or sections that can each be swapped out for the slave type in question.
-
- ++MUCH easier maintenance
-
- --Have to figure out how to phrase the scene in a way that can be broken down into discrete chunks
-
-You can also combine the two cases. For example, you may want a complex, interleaved set of `if` conditions for the common cases, and then have big blobs for the corner cases that are hard to handle. -->
-
Generally speaking, interaction scenes are split into 5 main sections: "intro", "setup", "consummation", "aftermath", and "cleanup". Though not strictly required, more often than not, your scene will contain at least one of these.
#### `intro`
@@ -246,166 +225,6 @@ function cleanup() {
<sup>From `src/npc/interaction/fButt.js`</sup>
-<!-- It can also be easier if you split the scene into a "prep", "main", and "finish" section (these would all be the same writing block, just 2-3 <<if>> chains in sequence); that way, you could, for example, take all the various possible cases that aren't really unique, and narrate them so that, in the main section, you don't have to do so much explanatory writing for the scene to make sense overall. Then, if necessary, wrap up with the finish section. (See src/pregmod/fSlaveSelfImpreg.tw for an example of this approach)
-
-All the variables for you and the slave are, generally, held in the variables $PC and $activeSlave, respectively. When the PC and the slave have the same attributes, they usually have the same name, but exactly what they do and mean can vary a little bit. RTFM for details. To access a specific variable, you do $var.attribName, so e.g. pregnancy is checked by $activeSlave.preg or $PC.preg. In rarer cases, you'll be dealing with an indexed entry in the $slaves array; if that's the case, you'd use $slaves[_u] or $slaves[$i] (or whatever) instead of $activeSlave. If a second (or third?) slave is present, it will be stored in another variable, the name of which will depend on the scene; for example, when impregnating a slave with another slave, the sperm donor is in $impregnatrix -->
-
-<!-- Conditions are usually checked by
-
-```js
-if (condition) {
- return `some text`;
-} else if (condition2) {
- return `different text`;
-} else {
- return `some other text`;
-}
-```
-
-Conditions are usually comparative (i.e. `a < b`, `b === c`, or `d !== e`) and can be chained together with `&&` (AND) or `||` (OR) and grouped with `()` - for example: `if (a > 1 || (b === 2 && c !== a))` lets you check that either variable A is greater than one, or both B equals two and C is not equal to A.
-There are also a few miscellaneous functions that let you check things like whether a slave can get pregnant or whether two slaves are mutually fertile
-
-"You fuck $activeSlave.slaveName" becomes "You fuck Beth"
-You can also explicitly print a variable by doing <<print _varName>> (for temp variables) or <<print $varName>> (for global variables) which can be useful in various situations; it also lets you print the output of code expressions, like <<print $someNumericVar * 10>>.
-If you want to change a variable, you do something like
-`<<set $activeSlave.devotion += 5>>`
-Which would, in this case, give a devotion increase of 5. -->
-
-<!-- Color is changed with YOUR @@.colorname;COLORED TEXT@@ HERE
-
-So a random (really stupid) example might be:
-
-```sugarcube
-<<if $activeSlave.fetish == 'mindbroken'>>
- Special big block of mindbroken text here.
-<<elseif isAmputee($activeSlave)>>
- Special big block of amputee text here.
-<<if $PC.dick > 0>>
- <<set _wasVirgin = ''>>
- <<if $activeSlave.vagina > -1>>
- <<set _orifice = 'vagina'>>
- <<if $activeSlave.vagina == 0>>
- <<set _wasVirgin = 'vaginal'>>
- <</if>>
- <<else>>
- <<set _orifice = 'ass'>>
- <<if $activeSlave.anus == 0>>
- <<set _wasVirgin = "anal">>
- <</if>>
- <</if>>
- You fuck $activeSlave.slaveName's _orifice.
- <<if _wasVirgin != ''>>
- <<if $activeSlave.devotion > 50>>
- $He @@.hotpink;loves@@ losing $his <<print _wasVirgin>> virginity to you.
- <<set $activeSlave.devotion += 5>>
- <<else>>
- $He @@.mediumorchid;@@dislikes losing $his <<print _wasVirgin>> virginity to you.
- <<set $activeSlave.devotion -= 5>>
- <</if>>
- <</if>>
-<<elseif $PC.vagina > 0 && $activeSlave.dick > 0>>
- $activeSlave.slaveName
- <<if $activeSlave.devotion > 50>>
- @@.hotpink;lovingly penetrates@@
- <<set $activeSlave.devotion += 5>>
- <<else>>
- indifferently hammers
- <</if>>
- your pussy.
-<<elseif $activeSlave.vagina > -1>>
- Lesbian sex here.
-<<else>>
- ERROR - PC doesn't have dick or vagina?
-<</if>>
-``` -->
-
-<!-- If you need to set a temp variable, prefix it with _ instead of $. This way, you don't go cluttering up the world with variables that only matter inside your little writing segment.
-
-You can "hot-test" stuff by text editing your HTML copy of FC, but it's a little more tedious because you have to "escape" double quotes, <, >, and & with " < > and & respectively.
-
-Some tips:
-
-- Write your logic first, so you don't forget to close tags. In other words, it's better to do
-
-```sugarcube
-<<if $cond>
- TODO
-<<else>>
- TODO
-<</if>>
-```
-
-And then fill it in later than it is to end up with a situation where you have a dozen unclosed tags and you can't remember where they are or what they do.
-
-- For very simple stuff, it's fine to "inline" your stuff. For example, when penetrating a slave, doing `"you fuck $his <<if $activeSlave.vagina > -1>>pussy<<else>>ass<</if>>"` to show "pussy" or "ass" as necessary. However, if you need to do the same comparison a bunch of times, do something like
-
-```sugarcube
-<<if $activeSlave.vagina > -1>>
- <<set _targetOrifice = "vagina">>
-<<else>>
- <<set _targetOrifice = "asshole">>
-<</if>>
-```
-
-And then, when you need it, do `"you fuck $his _targetOrifice"` in sixteen different places without having the pain in the ass of copy/pasting the same if/else clause every time.
-
-- INDENT YOUR LOGIC. USE TABS. I'm serious. Don't question me. It will make EVERYONE hate you, when they have to deal with your code, if it's not indented properly.
-This is much easier to read:
-
-```sugarcube
-<<if $cond1>>
- <<if $cond2>>
- whatever
- <<elseif $cond3>>
- whatever
- <<elseif $cond4>>
- <<if $cond5>>
- whatever
- <<else>>
- <<if $cond6>>
- whatever
- <</if>>
- <</if>>
- <<else>>
- whatever
- <<if $cond7>>
- <<if $cond8>>
- whatever
- <</if>>
- <</if>>
- <</if>>
-<</if>>
-```
-
-than this:
-
-```sugarcube
-<<if $cond1>>
-<<if $cond2>>
-whatever
-<<elseif $cond3>>
-whatever
-<<elseif $cond4>>
-<<if $cond5>>
-whatever
-<<else>>
-<<if $cond6>>
-whatever
-<</if>>
-<</if>>
-<<else>>
-whatever
-<<if $cond7>>
-<<if $cond8>>
-whatever
-<</if>>
-<</if>>
-<</if>>
-<</if>>
-```
-
-- Proof-read your shit before posting it. Spell-check wouldn't hurt. -->
-
## Tips
-- Make sure you proofread before committing your changes. Many text editors nowadays have plugins you can use to catch spelling mistakes as you write, which can be a huge help.
+- Make sure you proofread before committing your changes. Many text editors nowadays have plugins you can use to catch spelling and grammar mistakes as you write, which can be a huge help.
--
GitLab