Advertisement
ChroniclerCoC

Writing Tutorial

Oct 8th, 2018
86
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.77 KB | None | 0 0
  1. ==Writing Tutorial (version 0.6)==
  2. Originally written with CoC in mind, and adapted to fit text games more broadly.
  3. '''>Actual writing'''
  4. How do I start? What am I meant to do?
  5. Like many many things in writing: '''Start simple.'''
  6. 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.
  7. 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!
  8. '''>General writing tips'''
  9. For brevity's sake, I'm going to assume you know much of the fundamentals. Special mentions for game submissions are:
  10. You should never directly quote the player's thoughts or speech. Do not say You tell her ''"Succ my dick, faggot"'', instead say ''You demand she service you, eliciting nervous compliance from her.'' These are '''role-playing''' games, everyone's personality varies.
  11. 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. Why is adding it yourself a problem? In submitting to games, special characters can break things as you copy, merge, or transfer things around. Always use totally basic plain-text.
  12. '''>Parser How-To'''
  13. 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.
  14. 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.
  15. You don't need to be exact with the code. If you use [penis], that's okay, as long as you always use the same code. 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.
  16. '''>Pseudo-code'''
  17. 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!
  18. [if (((condition))) then {(((result)))} elseif (((different condition))) then {(((different result)))} else {(((no condition, just do this result if no other condition is met)))}]
  19. 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 system is NOT real code, nor is it important to emulate real code. This is solely about getting your intention across in an obvious and concise manner. The coders will do the actual work.
  20. '''>Tools'''
  21. Any text-editor will do for the writing phase; I personally recommend Notepad++ as it is what I use (with dark settings to stop my eyes from bleeding!)
  22. Recommended host for when you're ready to share: https://pastebin.com
  23. ————————————
  24. '''I still suck ass at writing, though!'''
  25. As a broad subject, you can find many resources for writing online. For more personal guidance, you can try sharing your work and seeking critique on >>>/writ/
  26. On a game-specific level, examples can be found in the threadly Chronicles posts, where new submissions are compiled, for CoC. It is likely any other game you wish to submit to has fans happy to read and review your work.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement