▶ The Writing Guide & Tutorial 10/9/2024 No.299697

At the bottom of the page, click the ☀ to change to dark mode.
This post aims to clarify the intricacies of writing and focuses on particular points someone might struggle with. This guide mostly contains information on writing for CoC (it also functions as such for a broader spectrum of erotic games), and is meant to teach the very basics of what one needs to get started. The second chapter is specifically on how to use commas, as that is something people constantly wrestle with. It's very in-depth and nitpicky, but one often has to be in order to improve.

Always keep in mind that you can turn to others to proofread your writing; this counts not only for your grammar and usage of words, but also for consistency with the established lore and the sorts.

General Writing Tutorial

>Actual writing

How do I start? What am I meant to do?
Like many things in writing: Start simple.

Pick a character, monster, or any other existing part of the game and add something to it. Choose a fetish you like, or an interaction you think is missing. A small example is adding a benign and cutesy single-paragraph scene where the player plays with their children that they have with X NPC like Sophie or Kiha in CoC's case. Wouldn't be hard, wouldn't take long. This is a good way to become more comfortable. As you go, you can amp it up; add a sex scene with a character/monster that has little content, like a female/herm player mounting a defeated amarok in missionary as a victory rape. There is no pressure to ever get beyond that level of depth, though from there you are free to create brand new enemies, make large expansions, new quests, etc.

Just don't rush directly to doing a large project! Special note: Always assure when you write a character that other fans agree that it fits that character. It's easy to get your own head-canon around these things!

>General writing tips

For brevity's sake, I'm going to assume you know much of the fundamentals. Special mentions for game submissions are:
You should never directly quote the player's thoughts or speech. Do not say You tell her"Suck my dick, bitch", instead say You demand she service you, eliciting nervous compliance from her. These are role-playing games, everyone's personality varies.
Do not use any special characters, such as smart-quotes (“”), fancy apostrophes (’), or anything else that isn't an actual key on a standard keyboard. The game itself will often replace the standard quotes "" and apostrophe ' with the fancier equivalents for you. Always use totally basic plain-text.

>Parser How-To

Many text games rely on a parser to fill in player variables from things as simple as your name to as complex as genital measurements, species of your legs, or what kind of tongue you have. Sound hard? Really isn't.
In any case where you would refer to anything that can be changed, just replace it with a standard term in [brackets]. Example: Your hips sway, swinging your massive dick like a wrecking ball. > Your [hips] sway, swinging your [cock] like a wrecking ball. Some games, such as Lust Doll (made in RPG Maker), parse with `ticks` or another symbol instead of brackets, but the concept is mostly the same.
Some things will be more nuanced, such as using parsers in a longer series of references. You don't want every instance of dick to gush about the details. The parser doesn't know how many times you used it, you'll have to make the distinction yourself. It may be better to just plainly state "dick" instead of letting the parser say "swollen, meaty horse cock". Limit yourself to one use of any given parser code per paragraph.
For more information on parsers, the Parser Tutorial section can help you.

>Pseudo-code

Sometimes you need or want some kind of function call or variation. Dare you try to code that in on your own? You could, but it's not necessary. Generally speaking, a coder is happy to make what you write become a functional scene in the game. Despite this, there are steps you can take to make your intentions clear!
[if (condition) {output if the condition is true|output if the condition is false}]
Often times any special case you wish to add can be done via that system. You need not even have an "else", in the case of no condition being met, if you don't want anything to happen. This convention may not always be exactly what makes it into the final code. This is solely about getting your intention across in an obvious and concise manner. The coders will do the actual work.

>Tools

Any text-editor will do for the writing phase; most recommend Notepad++ for its simplicity and support for proper coding (with dark settings to stop your eyes from bleeding). On Linux, Kate works. Regular notepad works. Plaintext editors in general just work.
You should always use pst.moe to share your writing and submissions, due to it being in plain text thus making it easier to read and translate into code. If you use a host with rich text options, I urge you not to put in any rich text effects yourself such as italics or bold and instead stick to [i:italic] and [b:bold] so nothing is lost.

"I still suck ass at writing, though!"
As a broad subject, you can find many resources for writing online.
On a game-specific level, examples can be found in submissions from other people. Often it's likely there are people learned in English that can give you pointers for your grammar, wording, sentence structure, topics, and all that sort of shit.


On The Usage of Commas

Authored by our esteemed comma connoisseur, Mothman.

Commas have a lot of uses in English, but this guide should hopefully help you with a few of the more common ones. I'm including a glossary of terms at the bottom, with the terms that appear there being shown in [brackets] to indicate such. This primer assumes that the reader has some basic familiarity with English grammar, especially word categories (e.g., verb, noun, adjective, etc.), but this will be subject to change if more explanations are necessary.

1.) With lists

Lists of three or more things joined by a [conjunction] require a comma in between each item. The last comma (the one directly before the conjunction) is known as the Oxford comma and is occasionally omitted, but because it's the standard in CoC (and most of America), you should use it. Hopefully this rule, at least, should be familiar to you.

Examples:
Go to the store and buy milk, bread, and eggs.
He walked to the store, bought a few things, but forgot the milk.

2.) With compound sentences

A compound sentence is one which contains two or more independent [clauses] joined by a conjunction. In a compound sentence, a comma must be put before the conjunction. This rule often confuses people, as it can be unclear for some when it's clauses being linked or verbs being linked and whether a clause is independent or not. It's anecdotal evidence, but I feel that these are some of the most commonly missed commas for most people, so I would recommend trying to familiarize yourself with this rule.

Examples:
✓ I went to the store, but they were out of milk
//Here we have two clauses, each with a subject ("I" and "they") and a predicate (identifiable through the verbs, "went" and "were") which are linked together by the conjunction "but." Thus, a comma is necessary here.
X *Go to the store, and buy me some milk.
//This comma is incorrect, as there is only one clause in this sentence. While there are two verbs, there is only one subject, so the conjunction must be linking the verbs.
✓ Items that are in this glossary are surrounded by brackets, because this is on fucking rentry and I don't have any better formatting options.
//This is a good example for illustrating what an independent clause is. "This is on fucking rentry" and "I don't have any better formatting options" are both full clauses with subjects and predicates, but because they're both objects of "because," they're both dependent clauses, and thus there doesn't need to be a comma before the "and" linking them.

3.) Introductory phrases

This is a catch-all category for the various [prepositional], [participial], and other [phrases] which may appear at the start of a sentence, before the subject. These usually require a comma inserted afterwards, but when very short (I've seen four words or less given as a metric), it can sometimes be omitted. This only really works if the phrase in question is closely related to what follows, and since you're never wrong if you do include it, I would recommend not omitting these unless you have a solid grasp on what you're doing.

Examples:
On his way to the store, he dropped his wallet.
Searching the ground nearby, he found it in a bush.
After he stood back up, he noticed that there was some cash missing from it.
Yes, I'm already tired of making these.

4.) With quotations

When a quote is grammatically integrated into a sentence with a [dialogue tag], it must be separated from the rest of the sentence by a comma. If the dialogue tag comes after the quote, the comma replaces the period which would usually go there, but not exclamation points, question marks, or ellipses. Commas should go to the left of the quotation mark, and see the note at the bottom for a short overview of why that is.

"Well fuck," the man said.
He asked a nearby lady, "Did you see anybody touch my wallet?"
"No," she replied, "I didn't."

5.) With parentheticals

While "parenthetical" technically means "inside parentheses," it is used for anything in a sentence which breaks off from the main point or is construed as sufficiently separated from everything else to merit being set off by commas. That's all a bit vague, but these commas will probably feel intuitive/natural once you see them for what they are. If you want to make this kind of interjection stand out more, you can also use em dashes (—) instead of commas (but make sure to look up how to use those).

Examples:
He, although somewhat exasperated by this entire situation, decided to be polite and drop the matter.
The woman, her mouth twisting into a grin, snickered as the man walked away.

6.) With direct address

When a character (or you, if you're talking to somebody) calls someone by name/title in a sentence, that name is set off by commas.

Examples:
I'm not sure where I was going with that little story thing, anon.

//The above examples constitute the most common comma usages, as well as the ones people most frequently make mistakes with. The following comma usages are a little more specific, so feel free to stop here for now if all that was overwhelming.

7.) With focus shifts

When the focus of a sentence changes part-way through, a comma is optional. This is a tricky subject, as you have to know when not to separate things which shouldn't have a comma between them and people differ in which commas of this variety they view as "correct" (I, for instance, don't like commas before a conjunction only linking two verbs, but that's a relatively common usage).

Examples:
I'll move on to normal examples, as I've run out of creativity already.
I like the above example, but hate this one.
//Use the above with caution.

8.) With participial phrases

This could be considered more of a subset of the parenthetical usage case, but it's specific/common enough to warrant a bit of explanation. Participial phrases are often seen at the end of a sentence, far removed from the nouns they modify (like "removed" in this sentence, if you don't mind me getting ahead of myself). These need a comma in front of them unless they directly follow what they're modifying.

Examples:
The fact that I'm writing a new sentence here instead of lazily reusing that one from earlier is honestly surprising, brightening my day just a bit.

9.) With appositives

An appositive is a secondary noun phrase which follows a primary one to give it additional clarification. The rule with these is that if the appositive is necessary for identifying the noun, it's used without commas, but if it's not, you have to put them on both sides.

Examples:
My favorite anon, you, always puts a smile on my face.
My brother Dan is imaginary.
//This appositive doesn't need commas because it's necessary for identification.

10.) Lists of unrelated adjectives

Lists of adjectives that are all modifying the same noun in the same way must be separated by commas. The way to test this if you can add an "and" in between the adjectives, they need a comma. Another test is whether you can reorder them, in which case you also need a comma.

Examples:
Thank god I don't have to come up with another shitty, stupid example.

11.) With question tags

Use a comma when there's a question at the end of an otherwise declarative sentence.

Examples:
Guess I was wrong about that one, huh? Can't always get 'em all.

12.) With negation

Use a comma to separate parts of a sentence contrasted with "not" or another negative.

Examples:
This is a mod, not vanilla.

13.) With dates/addresses

If you're writing long form dates or addresses in a porn game, I'm going to assume you're autistic enough to not need my guidance.

666.) Comma splices

I'll be upfront about the fact that I'm a little bit more strict about these than some others, so keep that in mind while reading this. A comma splice is when two independent clauses are joined with only a comma, resulting in a run-on (this is essentially case 1, except without a conjunction). I've been informed that this is properly termed "asyndeton" (which you should appreciate if you're a boring loser like me). While technically incorrect, they are sometimes used when the two clauses in question are particularly related/close together. A semicolon (;) would normally be used in situations like this, but they're pretty gay, so people don't like using them too often (and you should be very careful of using them too much, especially in informal writing like CoC) (you know who you are).

Glossary

//If you are ESL, I might recommend that you search for these terms in your native language, but feel free to plow ahead too.

Phrase

This is the first item on the list because it's an important one that's not likely to be known by a decent percentage of people, and I'll be using it throughout. Simply put, a phrase is a group of words which form a unit. Any clump of words which can be moved around in a sentence or replaced entirely by something else (like a pronoun for noun phrases or the word "do" for verb phrases) can be considered a phrase (these two metrics are known as constituency tests, but that's a little bit outside of the scope of this overview).

Conjunction

I generally use this term to refer to coordinating conjunctions and not subordinating conjunctions, but for an explanation of the latter, please see "Clause" below. These are words which are used to connect words or phrases together. There aren't too many of these, so you'll often see them grouped into the classic "FANBOYS" list (for, and, nor, but, or, yet, so).

Clause

A clause is a subject joined with a predicate (both terms are explained below). Clauses can be either independent or dependent, depending on how they're integrated into a sentence. Independent clauses are those that stand on their own. If you can take a clause out of the sentence it's in (minus any coordinating conjunctions used to join it with other clauses) and it still works as a complete utterance, it's an independent clause (these may be a difficult test for non-native speakers, so be careful). Dependent clauses are those introduced by a subordinating conjunction like "because," "when," or "if." When taken on their own, these clauses are known as fragments (a fairly common grammatical error).

Subject

This term can be a little tricky to define, as it's actually used to mean a couple different closely related things, but generally speaking, it's the noun that's doing/being the verb. For example, the noun "term" in the first sentence of this entry.

Predicate

This term has the same issues as "subject" with regards to definition, but it's generally viewed as the part of the sentence which isn't the subject. That isn't very helpful, so I'll note that you generally find them in English by looking for a verb to go with the subject of the sentence. If any of the last three terms are at all confusing, I recommend looking them up, as others will have certainly done a better job than me explaining them.

Preposition

These are generally defined as words which show the relationship between a noun and something else in the sentence. The reason this is so vague is that they can both describe and modify a lot of different things, but there are only \~150 of them in English, and some of the more common ones (in, of, at, etc.) are words that you know very well.

Participles

Participles are adjectives formed from verbs, usually using the "-ing" or "-ed" suffixes. There are irregular verbs in English which can have different forms (e.g., hung, brought, thrown, etc.). Be careful not to confuse these with gerunds, which are nouns formed from verbs using "-ing" (e.g., "I enjoy shitposting").

Dialogue tag

These are used to grammatically integrate dialogue into a sentence. They generally involve a subject and a verb that can take a direct object (e.g., "He says"). It's not enough that the verb can take a direct object, you must also make sure that nothing is filling that slot, because the dialogue needs to be the object of the verb.

A closing note on comma placement with regards to quotation marks: commas should always go to the left (like ,"), even if they aren't part of what's inside the quote. This is what's known as Typesetters' Quotation, and it is standard practice in America (and mostly what's used in CoC). Logical Quotation is used in many other parts of the world (and may in fact be the superior convention), but consistency is important, so you should use TQ.

Anyways, I hope this helps with your Mensa applications and/or the babyfur NTR snuff-fuck scene you've always dreamed of. Godspeed.


General Punctuation

Authored by the prince of punctuation, Mothman.

Apostrophes

I see people fuck these up constantly, especially native speakers. ONLY USE APOSTROPHES TO SHOW POSSESSION (and contractions, but that's not the problem here). They are never ever used for the plural suffix, and I've even seen people use them for third person singular present verbs (e.g., *run's). Don't do this; it makes my eyes bleed. I'll also talk about the possessive with nouns ending in "s" (e.g., "demoness") There is a lot of variance in how people handle these, but I'll recommend you always use the full "'s" suffix if it's pronounced in the word (e.g., "demoness's). Some people omit them from all words that end in the letter "s" (but not the sound [s], as both "cockatrice's" and "Alice's" are fine with everybody), and some only do this with proper nouns. It's most important to be consistent, so just make sure that you always do this the same way.

Dealing With Dashes

There are actually several different types of horizontal lines used in English writing, but most people just use hyphens for everything. Here's a list of the three most important kinds:

Hyphens (-)

These are the smallest and most commonly used (although often incorrectly) dashes. The primary purpose of the hyphen is to join certain compound words in English. It's important to note that not every compound gets a hyphen, and that people have very different ideas of one when is warranted (e.g., "em dash" vs. "em-dash"), so you have a bit of leeway here. Another usage you'll see elsewhere is when a word is cut in half by wrapping text (but you don't need to worry about that for CoC). You will also sometimes see them used with prefixes (e.g., "pre-cocoon").

En dashes (–)

These are the least useful/common dashes, so you don't really to have pay too much attention to this section. En dashes are used for ranges of values like page numbers or dates (e.g., "pg. 45–77").

Em dashes (—)

These are the ones that people screw up the most, as well as the primary reason this section is being written. Em dashes can be used in place of colons and parentheses/parenthetical commas, as well as for interruptions in speech/thought/narration. They can have spaces around them (with which they are called "open") or none ("closed"). Some people also happen to use open en dashes in place of em dashes, but this is not super common. Notably, you should NOT use hyphens for any of the functions listed above—that's just wrong.

For the sake of consistency, you should use closed em dashes when writing for CoC, but keep in mind that this may not be the case everywhere, as there may be situations where you have freedom with this or there's a different convention you'll have to follow.


Parser Tutorial

Authored by the parser professional, Mothman.

Parsers basically allow the game to replace certain words enclosed by brackets, for things that vary based on the player/gamestate. There's a big parser function that the game runs almost all text through which does things like fix double spaces and make quotes fancy. It also looks for any text contained in square brackets and checks them against a list of parser tags in a file. If it finds a match, that file tells it what text to spit out, and if it doesn't, it returns an error. All of these parsers are lowercase, but if you capitalize the first letter, the same thing will happen to the text it returns (for use at the start of sentences).

Body Part Parsers

These return a relevant description for the given body part. Some of them can be a bit tricky (especially the skin ones), so make sure you know what you want.

Sexual Body Part Parsers
Parser Description
[allbreasts] or [alltits] returns descriptions for ALL breasts.
[ass] or [butt] (e.g., "cushiony, full butt")
[asshole] or [butthole] (e.g., "virgin pucker")
[assholeorpussy] returns a pussy description if you have one and an asshole one otherwise. See individual parsers for examples.
[balls] (e.g., "pair of testicles")
[ballsfull] is just more detailed (e.g., "a quartette of cantaloupe-sized gonads").
[breasts] (e.g., "baseball-sized tits") //but why?
[lastbreasts] or [lasttits] returns a description for the bottom-most row of breasts.
[chest] returns either a description of your tits or of your chest if you don't have them (e.g., "chest").
[clit] (e.g., "diminutive clit")
[cock] (e.g., "nice prick")
[cunt] or [vag] or [vagina] (e.g., "virgin, wet muff")
[eachcock] (e.g., "your ample ordinary-looking tool")
[fullchest] (same as "chest" but works like "allbreasts")
[multicock] describes all of your cocks.
[multicockdescriptlight] does the same but with less description.
[nipple] (e.g., "pronounced nipple")
[nipples] (same as above, but plural)
[lastnipple] returns a description of one of your bottom-most nipples.
[lastnipples] (same as above, but plural)
[onecock] (e.g., "your ample prick")
[pussy] (same as "cunt")
[sack] (e.g., "nutsack")
[breastcup] (e.g., "b-cup")
[lastbreastcup] returns a description for the bottom-most breast cup.
[vagorass] returns a description of your vag if you have one and your ass otherwise.
[cockplural] all of the "plural" just return the word or its plural form if you have more than one.
[dickplural] (see above)
[headplural] (see above)
[prickplural] (see above)
[wet] returns a word describing the player's vaginal wetness (e.g., "dry").
[genitalis] returns things like "cock is" (but modified for your genitals).
[genitalsdetail] is the same as the above but with the full description (basically like "[cock] is").
[genitals] returns the plural for your genitals (whatever they may be).
[cockhas] returns "cock has" or "cocks have."
[cockeir] returns "its" or "their" depending on cock number.
Skin Parsers
Parser Description
General skin note: skin is built from several parts, including tone, type (desc in the code), an adjective (adj in the code), and fur color (if you have it)
[skin] returns the adjective, tone, and description (e.g., "smooth, white skin"). It still returns "skin" if you have fur, wool, or feathers (for use when you'd still feel something on your actual skin).
[skin.noadj] same as above but without the adjective (e.g., "white skin" without "smooth")
[skindesc] returns the type of skin you have (e.g., "skin", "scales", "wool")
[skinfurscales] returns the adjective, the fur color if you have it or the tone if you don't, and the desc (e.g., "thick black fur").
[skinshort] is the same as "skin" but without the adjective or tone.
[skintone] returns just the tone (e.g., "white").

Gender Term Parsers

These all return the appropriate gendered noun/pronoun (e.g., "he" or "she"). Most of them are male, so try to use the male versions, even when writing scenes that are generally intended for girls. Note that you can feel free to put any gendered term in brackets, and coders can handle the rest.

Parser Description
[boyfriend] -
[dad] -
[daddy] -
[father] -
[he] -
[him] -
[himself] -
[herself] -
[his] returns "her" as the female version, not "hers."
[hers] is used for when "her" wouldn't make sense (e.g., "That book is [hers].").
[king] -
[lord] -
[maam] -
[ma'am] -
[madam] -
[man] -
[men] -
[malefemaleherm] returns the word that you are (e.g., "male").
[master] -
[mister] -
[sir] -
[son] -
[boy] -
[guy] -

Conditional Parsers

These can be used with the conditional notation mentioned earlier ([if (condition) {\<true text>|\<false text>}]. Some of them evaluate to true/false (e.g., "hascock") and some of them evaluate to numbers that you can compare (e.g., "strength"). There are a bunch of them, and most are pretty straightforward, so only a small list of the most common/important ones are included here, but always know that you can do something like [if (hasclaws) {whatever}] and we can make it work.

Parser Description
(all of the base stats) all stats can be compared (e.g., if (str > 50)).
"fatigue" -
"hp" -
"hour" -
"days" -
"hascock" -
"hasvagina" -
"hasbreasts" -
"hasballs" -
"isnaked" -
"singleleg" returns true for players that don't have legs (like nagas and goos).
"hasplainskin" returns true for players with normal skin.
"isfluffy" returns true for players with everything but normal skin or scales.
"silly" returns true if silly mode is on.
"ischild" -
"isteen" -
"isadult" -
"iselder" -
"metric" returns true if the player is using metric measurements.
"nofur" returns true if no fur mode is enabled.
"allowchild" returns true if underage is half or on.
"allowbaby" underage is fully on.
"guro" -
"watersports" -
"builtcabin" -
"builtwall" -
Regular Body Part Parsers
Parser Description
[arms] (e.g., "scaly, clawed arms")
[armadj] returns the above, but without the word "arms" (e.g., "furry").
[bodytype] (e.g., "an average body and soft, unremarkable flesh")
[claws] returns a description of claws if you have them (e.g., "fingernail").
[ear] (e.g., "furry ear")
[ears] (same as above, but plural)
[eyes] (e.g., "human eyes")
[eyecount] returns the number of eyes you have (e.g., "two")
[face] (e.g., "face")
[facelong] (e.g., "a square chin, chiseled jawline, and beard")
[feet] (e.g., "clawed feet") returns "coils" for nagas.
[foot] ([...]; "coils"/"coiled tail" for nagas)
[furcolor] (e.g., "blue")
[hair] (e.g., "moderately long, black hair")
[haircolor] (e.g., "red")
[hairorfur] returns "fur" if you have it and "hair" otherwise.
[hairorfurcolor] returns fur color if you have it (or feathers or wool) and your hair color otherwise.
[hairorfurcolors] is for degenerates with multiple fur colors (e.g., on lowerbody vs on main body).
[hand] (e.g., "scaley, clawed hand")
[hands] (same as above, but with an "s")
[hips] (e.g., "pleasant thighs")
[horns] (e.g., "antlers")
[leg] (e.g., "leg")
[legcounttext] (e.g., "two")
[legs] (same as "leg" but plural)
[neck] (e.g., "draconic neck")
[neckcolor] returns the color of the skin/fur on your neck (e.g., "orange").
[rearbody] returns the name for your rear body type (e.g., "draconic mane").
[rearbodycolor] returns its color.
[tongue] (e.g., "draconic tongue")
[underbody.skinfurscales] describes the skin on your underbody (e.g., for taurs).
[underbody.skintone] (see above)
[underbody.furcolor] (see above)
[wings] (e.g., "dragon wings")
[wingcolor] (e.g., "black")
[wingcolor2] returns the secondary color (e.g., you know what fucking colors are).
[wingcolordesc] returns the description of what the first part is (e.g., "membranes").
[wingcolor2desc] returns the description of what the second part is (e.g., "bones").
[tail] (e.g., "trio of kitsune tails")

General PC Parsers

These return general information that varies from character to character.

Parser Description
[age] returns the player's age.
[armor] or [armorname] returns the name of your armor.
[bed] returns "bed" or "bedroll" depending on if you've built the bed.
[cabin] returns "cabin" or "tent" depending on if you've built the cabin.
[inv] or [pack] or [pouch] or [inventory] returns what you use for storage (e.g., "pouch").
[lowergarment] returns your lower garment (e.g., "silk panties").
[magic] returns the school of magic the player is using (e.g., "Black & White").
[name] returns your name.
[race] returns what race you are (e.g., "human").
[shield] returns the name of your shield.
[tallness] returns your height in inches.
[uppergarment] returns your upper garment (e.g., "silk bra").
[weapon] returns the name of your weapon.
[weaponname] (same as above)
[walk] returns an appropriate verb depending on your leg situation (e.g., "slither").
[walking] (same as above, but with an "ing")

Misc. Parsers

These don't fit into the above categories.

Parser Description
[pg] returns two newlines (i.e., it starts a new paragraph).
[day] returns "morning", "day", or "evening."
[sun] returns "sun" during the day and "moon" at night.
[say: x] puts quotes and around x and italicizes it (for dialogue).
//The following three can be combined (e.g., [bu: x])
[i:x] italicizes x.
[b:x] bolds x.
[u:x] underlines x.
[monster.short] returns the name of the monster (e.g., "goblin").
[monster.a] returns the article the monster uses (e.g., "the").
[themonster] returns the above two together (e.g., "the goblin").
[monster.he] should be self-explanatory.
[monster.him] -
[monster.his] -

I hope this guide has served as a solution to all of your writing-related problems.

.

Edit Report
Pub: 09 Oct 2024 08:47 UTC
Views: 1345