Advice for Running a Quest: Difference between revisions

From questden
Jump to navigationJump to search
(Adding Rynh's style of suggestion parsing)
 
(31 intermediate revisions by 13 users not shown)
Line 1: Line 1:
[[File:Let me explain.png|thumb|right]]
[[File:Let me explain.png|thumb|right]]
A basic guide on how to do run a [[Quest]] correctly, with advice written by various <s>successful</s> [[Quest Authors]]. These are all rules of thumb, and as such, can be broken when necessary, but following these is a good start.
This page offers tips and advice for running a quest! These aren't hard rules, but you may find the information here helpful for making something you and your readers enjoy.


Important Note: If you feel like you have any advice to give, go right ahead and add it! We are all ears.
==What even is a Quest?==
A quest is an interactive storytelling medium, akin to a 'choose your own adventure' book being played out as your choices are made. A character is placed in a world, and it is the job of the suggesters to guide them forward on their journey.


=Starting A Quest=
Part of their charm is that they aren't linear in the way a webcomic is, nor are they a single person's story. The authors and suggesters work together to weave a tale either from whole cloth, or in a world the author has built around the character(s) ahead of time.
Advice for preparing to make a quest.


==Cooperative Story Telling==
==Getting Started==
The first thing you need to know about a quest is that it isn't something you tell to others. It's cooperative story telling. You may be laying the groundwork for the story, but it's the observers that influence how it goes. How much you let them have a say is up to you, but without any, you will not be doing a quest, but writing a story. As the author, you have the final say in what actually goes, but remember - you're not working alone. The players are working with you to create something unique.
Quests are a lot of work, and take a lot of dedication to run to completion. Unless the scope is very small, a quest can run for months or even years. You may have an amazing, grand idea for your quest, but it's important to not run it for your first time. Put it aside for now, and think up something small, simple, and fun to test the waters and make sure this is something for you. If you don't end up enjoying it, better to lose a small story than see a grand scheme go half-finished.


'Input' from the readers can come in many shapes or forms. Sometimes, it's like [[RubyQuest|commands in a Sierra-like adventure game]]. Usually it involves the readers describing courses of action for a given situation. In the instances where the players are made a character ([[Orb of Infinite Psyche|in some shape or form]]), usually input comes as conversations with the characters inside the quest.
Running a 'test quest' can help you know if you're ready to put in that kind of time, or if you'd prefer to tell smaller stories that are much easier to finish.


I'm sure there are thousands of other ways for the readers to interact with a quest -- one uses [[The Icon|bi-monthly development schedules]]. We just gotta find them out.
Being an artist isn't required to run a quest, but this site has a very strong artist lean, and quests with only text or GIS images don't tend to do as well, and generally have fewer participants. Keep this in mind as you plan out your story.


==Character Creation==
===Creating a setting===
Do you want to let your suggesters create the main protagonist, or do you want to have a completely pre-made protagonist?  Either way works.  Both ways can provide an entertaining time for all.
----
====The protagonist====
The protagonist is the eyes through which your suggesters see the world. They are the ones we'll get to know the best and form the deepest bonds with.


====Make Your Characters More Than Stereotypes====
There's many ways an author can create a quest protagonist. Some already have a character in mind, while others prefer to let the suggesters make a new character from scratch. Both methods are perfectly fine, and it's completely up to your tastes as a storywriter. The important thing is that you remain flexible. The character should be able to learn and grow as the story goes, and the suggesters will often add to their depth over time.
Sometimes it's fine to have a villain who is pure, unmotivated evil, or a hero with a 100% pure soul and a [[Dong_Quest|raging hard-on for justice]], or a girl whose one personality trait is LOLRANDUMB or a love of cheese (okay, that's never fine). Usually, though, it's good to fill your characters out a little more. Start with their driving inner objective. It has to be something broad and general, not "Get a cake" or "fuck that chick" unless you want them to be shallow (which, of course, can work. [[NicQuest]] started with a quest for lolcats). Make it something more like "Make a lasting difference on the planet", "ensure those who wrong me pay for it", or "Be accepted by my comrades". Something to drive them forward, like "[[DiveQuest|Become the Devil]]" or "[[Kara Quest|Purify the World]]". I think it was [[Reka]] who gave the advice that every character begins with one driving objective, which gives them, well, character. Build them up from that to flesh them out.


Once you've got that down you can move on to their stated objective, or how they present themselves to the world, whether that's in contrast to or bolstering their inner objective. It's the personality they put on for the benefit of others. [[Dive Quest|Muschio]] pretends he’s a gentleman, [[MudyQuest|Mudy]] uses flowery language, [[Kara Quest|Hope]] disguises herself as a sweet little girl, [[Journey|Demesi]] steadfastly maintains a blissful naiveté even as he beats the shit out of his enemies with his sword feet ([[Nedynvor|SWORD FEET]]).
If you're letting the suggesters design your protagonist, in whole or in part, be sure not to include options you don't like. If you're set on a male protagonist, don't offer the choice of gender, for example.


After that, work on their flaws. Even good people aren't ever perfect. It could be anything from [[Quest With No Name|a hot temper that arises at unfortunate times]] to [[MudyQuest|a penchant for screwing your own sister]], but without it people will have less to identify your characters as people rather than ideals. They can be paragons of good while [[Apocalyption|still having a crippling fear of rats.]]
====The world your protagonist inhabits====
Creating a world for a quest is not too unlike creating one for a tabletop RPG. Some prefer to make a finely crafted world full of lore and things to see. Others like to play it by ear, or even leave the world up to the suggesters to create as they desire.  


The exterior, interior, and flaws are the three biggest fish to fry. Now focus on your character in the now. What’s their status in the world they live in? How aware are they of their surroundings, and what others think about them? Do they care about that? What was the last thing they had to eat? When did they last sleep? Laugh? Screw? If they’re interacting with someone, how do they feel about them?
Think about what setup works for you, but be prepared for people to go places you don't expect them to go. No matter how fleshed out your world is, you'll likely have to make some things up as you go! Winging it is part of the challenge and fun of running a quest.


OK so some of those questions were sort of bullshit, and at any time there’s really no need to answer them all every fucking update. But you’d be surprised how much the minutiae can affect actions and words. Remember that every time someone opens their mouth to speak, they’re censoring themselves. Picking their words. What’s on their mind right now, and how do they translate that into how they are speaking?
If you're going for a deep, lore-filled world, It can help a place feel fleshed out to have events happen that the protagonist isn't directly related to. Maybe an NPC got married since we saw them last. Maybe a city has elected a new mayor. Little things like this can help a world feel 'alive'.


====But Stereotypes Are Sometimes Okay====
===Making your first thread===
----
This is where you put it all together and present your world to the suggesters at large. In general, quests start out by setting the scene and then asking the suggesters to guide the protagonist through whatever situation they face, be it danger or asking a cute girl/boy/eldritch horror on a date. That last one actually comes up sometimes.


* [[Farmer]]'s Bad Advice Corner:  
If the suggesters are making a character, it's usually best to start by asking them to define such things as sex (a fair warning: female wins almost every time, so if you prefer a male or other, don't leave it up for others to decide!), race (if applicable), body type, personality, skills, etc. How little or how much they decide on is up to you, and don't worry about making too many options for character generation.


You don't need the character ready from day one. Starting with a simple archetype or stereotype and letting the story shape and develop the character is perfectly acceptable. Everything, from quirks to background to motivations can be fleshed out as the story goes on. Sometimes, this procedure is mistaken as character growth.
====Some rules of thumb for making a title post (Also known as an OP)====
* <b>Always write the name of the quest in the subject field.</b> This helps people find it in the archive. <b>Please don't write "????" here.</b>
* Most authors write the protagonist's name (if it exists) in the name field, but this is up to your tastes. You can type a space to have it appear blank.
** It is also acceptable to use the name field for your author name or handle, if you prefer.
** Tripcodes are not necessary.
* <b>The title post should have an eye-catching image.</b> This will help it stand out among the others.
* <b>The title post image should not be all black or darkness.</b> Kind of as a corollary of the previous.
* <b>Don't use RubyQuest's start.</b> Unless you're specifically going for a parody, you probably shouldn't be starting in a black room with 3 glowing buttons; it's been done to death.
* <b>Nobody uses the e-mail field for e-mails.</b> In general you want to leave it blank.
* If you're starting a new thread for an existing quest '''link the old thread(s) or the wiki article in the OP'''. Make it easy on readers who'd like to get caught up!


* [[BiteQuest]]'s Disagreeance:
==Methods for collecting suggestions==
Once your first update is up, it's time for people to suggest ideas for how the story or character should progress! But how do you go about asking for those suggestions?


I'm not so sure this 'no stereotype' nonsense is really good advice. It depends on what kind of quest you want to run. If the quest is more about exploring and interacting with the world, it's better for the protagonist to be more of a blank slate. They'll develop personalities over time on their own for the most part. I will say it's a pretty bad idea to make the protagonist completely beholden to the majority suggestion unless you're doing something interesting like [[Narus Quest]], or something plot-light and fun. If the quest is more about the main character's personal issue, then of course they need to have a strong personality that is merely influenced by what the suggesters recommend.  
Some prefer to have the character or narrator ask directly. "What do I do next?" "What do I say to them?" Others leave it implied, simply pausing the story where it is to wait for input.


Still, for main characters, I'd say don't develop them too deeply. You want the players to feel like their input matters, and the story is always better when it actually does. The players will also feel rewarded when their suggestions begin to actively shape how the character views the world. That being said, the above advice is great for NPCs and other characters not directly controlled through suggestions.  
Regardless of the method you choose, remember that you do have some sway to avoid options you really don't want to happen. Your protagonist can simply refuse to consider it, or you can leave it out of the vote options. Be careful, though, as doing this too often is against the spirit of quests.


I think [[Farmer]] is more on point even regarding NPCs, though; start them out as stereotypes with a couple of quirks, and they'll sort of develop on their own. Just think from the perspective of the NPCs: Instead of moving them around like chess pieces to make your story go where you want, the whole thing will be better if you just consider what each character would reasonably do in the situation. That, plus the usually random input from the suggesters will make the entire quest more organic, realistic, and unpredictable.
===Freeform Questing===
Freeform questing is when you let the suggesters post with whatever action, idea, or question they have in mind, with no effort on your part to limit their options. This method allows for great creativity, but can be hard to handle if you have too many suggestions. It also makes it a little harder to guide the story in the direction you might want it to go.


* [[Bromeliad|Brom]]'s corollary:
Freeform is good for NPC conversations, and for putting someone in a setting and letting them explore. It also helps the narrative flow for those who read a finished quest, as each update flows into the next without pausing to list a bunch of options.


Yeah, this advice is for NPCs and to make your dialogue a bit more snappy, not to railroad your characters. Make your main protagonists a bit more freeform off the bat and let 'em get fleshed out. By no means plan everything for yourself. That's a comic book, not a quest.
===Vote-based Questing===
Vote-based questing means giving a list of options, and holding a vote on which option should win. This lets you guide the story more easily at the cost of suggestor freedom and creativity. This method is much easier to handle for large amounts of suggestions, and in some cases can increase the amount of suggestions you receive as it's easier for them to pick an option than it is to come up with something from whole cloth.


==Opening Exposition==
Vote-based is good for overall pacing, and giving you a rough idea of what the next piece of story might entail. It also helps prevent suggesters going for something you don't want to do, as you can simply leave it off as an option. Or, you can be flexible and let a good custom suggestion or one with a lot of support win in spite of the vote limitations. It's up to you if and where you'd want to do this.
If you have a good idea of the world and/or the characters, you have a couple of choices. Instant Immersion, or Opening Exposition. Instant Immersion lets you get right into the action and explain the world and/or characters as you go along. Opening Exposition lets you introduce a few concepts about the world and/or characters before you get into the fun ''The World is in Danger'' bits of the quest. Both have their cons to go along with their pros.  With Instant Immersion, if you aren't careful, you can miss out on explaining a key element of the quest that might have been important or even helpful in prior situations. With Opening Exposition, you stand the risk of dragging the exposition on for too long, letting things get dull and stale.


==Have Events Planned==
===Parsing Suggestions===
Have a few different things planned that will happen to the protagonist, and think of a few ways he might react to them. Come up with a general idea of the order in which these things will happen, and a reason for them to happen.
Once you have some suggestions submitted, it's time to figure out how to use them and generate your next update. It should be noted '''there are no hard rules on how you use suggestions'''.  The following list are all examples of strategies employed in various quests:


====Events Happen That The Protagonist Has Nothing To Do With====
* '''Majority Rule.'''  Whatever the most people wants, goes.
The rest of the world is still happening. Maybe some small time NPC we met 5 chapters ago got married since the last time we saw him. Or while we are out adventuring, we come home to find the city has a new mayor because the old one was caught cheating on his wife. Life still happens, and having a few things like this will help add realism to the world, and make the players think that more is out there than what we see.
* '''Best Idea Wins.'''  There's a correct answer or solution, and if even one person suggests it, it'll be used.
* '''Everything Wins.'''  Your protagonist tries to follow, or react to, every suggestion!  Results may vary from disaster to comedy to wonderful.
* '''Most In-Character Wins.'''  Your protagonist treats the suggestions as a brainstorming session, and then runs with the idea(s) they like best.  Or perhaps there's an idea so true to who the protagonist is that they can't ''not'' use it.
* '''Pick and Choose.'''  Construct a gestalt, using pieces of different suggestions and ideas to make a better (or more interesting) whole.
* '''Minority Wins.'''  Yes, really, it's been done. Probably not something you want to overuse, and it risks blowback, but subverting a vote in the right circumstances can be powerful or interesting.
* '''Like I'd listen to you!''' Just have your character just argue with the suggesters and/or insult them while they do whatever.
* '''Quota.'''  Sometimes an option requires a minimum numbers of suggesters to support it.  (Ie, "X requires 5 or more votes").
* '''Stall or Clarify.'''  Sometimes the suggesters will misunderstand the situation (or you'll present it wrong) and you'll feel the need to give them more information before a final decision is reached.  Sometimes the suggesters will come up with a really good question that affects the outcome of the vote and you'll want to answer it.
* '''Railroad.'''  Sometimes the suggesters only have the appearance of choice.  Employ carefully.  As discussed in more detail below, it's hard to do right.


*[[Vyt]]'s Arguing Insight:
There's also no rule you have to stick with a single strategy.  Different decisions can be made in different ways.  You're also not limited to stick to this list if you think of other ways to use suggestions!


It does help that you do not overload the quest with too many "off-screen" events that might greatly affect the quest in some way. For example, if one of your character's main goals is to find her father and there have been a lot of hints pointing towards the general direction of her goal, it might be fruitful that the father stay in that place instead of moving around due to some event (it will look as if the quest is being prolonged unnecessarily, otherwise). Quest authors are expected to make events as realistic as possible, and that also means not adding too much unnecessary events.
==Running your quest: Tips and tricks==
===General tips===
* <b>Don't push yourself! Know your limits and take breaks!</b>
* <b>Back up your data!</b> This is good advice in general.
** Don't write your posts on the site.  Write them in a text editor so you can save, and so you don't lose everything if you close a tab or your browser crashes.
* <b>A useful way to post multi-frame updates is to make several tabs, each filled with part of the update.</b> Then you can go from tab to tab posting the entire update in seconds.
* <b>Try to avoid situations where there's only one option.</b> If there's a path going left or right, don't have one lead to a dead-end. This kind of ruins the nature of letting things be up to the suggesters. If you do make a dead end, be sure to put something interesting there so there's more to do than backtrack!
* <b>Keep it interesting.</b> Stopping in front of a door and asking if it should be opened isn't very interesting, unless you offer some insight about what might be behind the door.
* <b>Make sure each update accomplishes something,</b> be it moving to a new location, advancing the combat, or building on characters. If a switch is pulled, it's best not to have the result be that nothing happens. If the current location or scene has no real options, go ahead and move the plot forward automatically.
* <b>It's against the spirit of quests to keep the story on rails.</b> 'Railroading' is when the character does something that the suggesters either didn't suggest, or actively suggested against. It's extremely frowned upon. There are a few situations where this can be effective in giving a feeling of powerlessness, but it should be used very, very sparingly. It's very hard to do right, and much safer to avoid outright.
* <b>Sometimes the suggesters simply can't choose what they want.</b> If you have votes that tie, or freeform where nobody has a consensus, then it's fine to go ahead and pick the option you feel makes for the best story (or that the protagonist is most likely to choose in a vacuum).
* <b>A lot of people never expand the thumbnail.</b> Keep this in mind when planning how much detail and information goes into the artwork. If you set a precedent for hiding things in the art, people are more likely to expand images after getting burned once.
* <b>Be mindful of how severe the punishment is for a 'wrong' action.</b> Trap options and bad ideas can often land the character in a poor situation. Once the character has suffered a consequence, the suggesters will be a lot more cautious, which could help or hurt depending on the mood of your quest.
* <b>Because there's a number of people seeing your story unfold, people will often try to guess what happens next, and they might be right.</b> It's up to you if you want to reward them, or change your story to keep them guessing. Be mindful that doing this too much can lead to an incomprehensible story!
* Sometimes the suggesters will come up with something better than you have. <b>Roll with it!</b>
* Remember the number of people reading and enjoying a quest is generally larger than the number of people suggesting and actively contributing. And that's ok!


==Have an Ending Planned==
===Suggestor tendencies===
This may sound like railroading to some, but knowing how you want to end it will help you have a goal in mind, and help you keep going and (hopefully) help you finish.
There are some ways in which suggesters can be predicted. None of these are a guarantee, but keeping them in mind can be helpful for planning your adventure.


=Running A Quest=
* They almost always pick 'female' for character generation.
Advice for once you have it off the ground.
* They often prefer to make friends rather than fight.
 
* They often try to flirt with any NPC you introduce.
==Always Present Options==
* They often react disproportionately to betrayal, or perceived betrayal, by NPCs.  
This is most important. There always needs to be something for the players to suggest, or else nothing can happen. So, do your best to give them something to work with. If they don't bite and do something entirely different, that's fine too, but at least they had options. There are a few guidelines to help ensure you are doing this, which can be tl;dr'd as follows:
* Loud minorities will sometimes complain about a chosen action. <b>Don't let them distract or discourage you!</b>
 
* <b>They are often paranoid.</b> Even if you're running something lighthearted, people will sometimes be afraid to do something that might lead to consequences.
* [[TestPattern]]
* <b>They are easily distracted.</b> If no effort is taken to guide the story, they will happily have the character faff about getting nothing done until they eventually lose interest in the quest. Having a quest about faffing about is fine, but make sure there's something interesting to do and that they are guided to it!
 
* <b>They love to be teased.</b> Having the romantic interest confess right away will bore them, but having the romantic tension last a long time will keep them very much hooked.
Yelling at PCs < Faffing about < Boring exposition < Interesting exposition < Stuff that reveals new options
* <b>They love matchmaking in general.</b> Seriously they love the romantic tension like a lot.
 
* No really, <b>be very careful about how you handle romantic/sexual tension!!!</b>
[[Vyt]]: But what constitutes an interesting exposition, Test? There are tons of views on a certain perspective that makes normally boring stuff interesting, and also the inverse. How would we know?
* Suggesters often want what they can't have, or to attempt to derail things.  In a lot of quests, that might mean pursuing romance and sex.  In a porn quest, that might mean ignoring the smut you're offering and pursuing something else entirely!
 
[[Gnome]]: If you can't tell what counts as exposition, there is a more serious problem going on here. Exposition is anything that gives the PCs more information to work with, be it a scroll of power or a rumor that some kids are being bullied at the local school. "Interesting" exposition is information that is directly relevant to what we are doing right now, or to what we (think we) will be doing sometime soon. Boring exposition is telling us stuff we already know.
 
* [[Farmer|Farmer's Corollary]]
 
Cutscene your way to hell if you have to; do not stop to wait for a choice until there is a choice to be made.
* [[Nahkh]]'s handy little suggestion suggestions
 
If you want to be quick and dirty, throw a bunch of small reminders at the bottom of a post to tell the posters of possible actions.  
 
* <s>ALWAYS END WITH A QUESTION!</s> End with a question whenever the character is legitimately confused about something.
 
====Don't Present Options That Are Not Actually Options====
*There is a path going left or right.
*>Go left
*The left passage ends in a locked door! Nothing else is here.
*>...Go right I guess
 
Don't do this. If you present options to them that don't actually affect anything if they are taken, don't present them. The locked door above could have easily been right at the intersection, and it would have worked just as well. Making people waste time doing things that aren't actually doing things directly relates to the guideline below this one.
 
However, in the above example, if we already happen to have the key for the door on the left, then it's not a false option. We could then use the key and proceed. If the key is actually down the right path, however, then the left door was never an option, and going right first was the only choice.
 
====Present Options That Matter====
On a similar note, the options presented should always be at least marginally important. If you have a long hallway with doors all along the length, don't have the character stop in front of each door and ask the suggesters if they want to go in. If any of them are different or interesting, then point that out in the text (unless its a secret hidden in the image or something) and just generally posit or inquire about inspecting any of them.
 
If you get bogged down with describing every action independently, or you wait for suggesters to just make the single, obvious suggestion, your quest will become boring pretty fast. For instance, if the character is a kid and has to go to school, you could have them getting dressed in the morning (pervert), but don't sit around waiting for the suggesters to say "get breakfast" "brush teeth" "wait for the bus" "get on the bus" "Take a seat" "get off the bus" "go to class" unless there are other legitimate options. This isn't to say that the character couldn't go through these motions. The story can start with the bedroom and end with the classroom, but it's probably more interesting and involving if you just have the character do these things automatically and have the suggesters' decisions bear on other interactions in each scene.
 
====Don't Waste Updates====
Don't have an update not actually update anything. If it doesn't present new information, new choices, or new stuff to work with, then it isn't really an update. For example, yelling at the players for being stupid is a waste of an update. Yelling at the players for being stupid and then pointing out information that they seem to have overlooked is not great, but it's okay. Working with their stupid and showing them why it was a dumb idea is even better.
 
====Don't Wait For Suggestions When There is Nothing to Do====
One of the problems that people seem to have when they start running Quests is that they feel the need to wait for suggestions between every frame, even when this isn't reasonable. If there is no decision to make that will impact the story or reveal information, skip ahead until there is. There are several ways to do this.
 
The first would be [[Dungeon Game|to use "cutscenes"]] and continue to update without waiting for input. This method should only be used sparingly, as it doesn't fully take advantage of the medium that the Author is operating in, and can sometimes lead to cries of railroading. However, there are definitely times when you want to show a lot of things happening all in rapid succession. This is when cutscenes shine.
 
Another way, and one that takes time to get right, is just to make sure that the next frame will give a choice, option, or lead to the something that will make a difference in their decisions or require their input. The main advantage to this method is it cuts down on cutscene drawing. Done poorly, however, this can make the narrative too choppy or difficult to follow, but some good writing and a bit of pacing can avoid this.
 
==Always Have Ideas (But Don't Get Too Attached To Them)==
Even when your options are left open and possibly vague, it's good to still have a few 'correct decisions' thought of beforehand. This helps you plan ahead, prods the players towards possible courses of action when stuck, and gives you an idea of what might happen in your ''next'' update.
 
But if the players come up with something different, consider just rolling with it. Part of the fun of questing is the effect players have on it, and you might be surprised with the results.
 
====Know When to Yield (AKA Listen To Their Theories)====
Admit it: you can't think of every possible thing. And the players will, sometimes, invariably, think of stuff that would never cross your mind. So, steal their ideas. Show no shame!
 
How often you'll do this depends on how crazy / random your players are, and how fast-and-loose you are handling your own plot. And when done well, they'll never notice you cheated. Hell, they might even think they 'guessed your plan', and that tends to make them happy. If you need examples, ask your favorite quest writers.
 
==TGchan is always a cupid==
It's been said, often by posters themselves, that they will always seek to pair up as many people as possible. It's up to you whether to encourage or discourage this, but remember to remain consistent about it! If you don't mind and want to encourage pairing off, offer multiple options of equal viability. If not, you can either set up a girl/boy to be there already, or you can make the situation not possible (the character doesn't care, the situation doesn't allow for it, etc.).
*[[Driblis]]' Addendum: 
 
While it's nice to allow some [[Romanticar|romance]] if you like, be wary of making your quest that was supposed to be about adventuring veer towards being about [[MudyQuest|Sex]] or [[Gobbo Quest|breeding]]. [[Reaver|Some]] [[Gnoll|authors]] are rather prone to this.  It's a thin line to walk, including romance or sex in a quest, and while it has been done [[The Protagonist Dies|correctly]] in the past, it's a razor's edge.
*[[BiteQuest]]'s Two Cents:
 
This is something that is totally in the hands of you, the Quest author. If you don't want the players to constantly try to pair up characters and focus on romance or sex, just shut those types of suggestions down EARLY. Have the main character state in unequivocal terms that they aren't interested in either that person or sex in general. You will still get ''some'' suggestions like that no matter what, but it won't derail the quest unless you, as author, let it. Even if the character is mostly a vessel for the players to use exploring the world, you can and should make them have a few strong characteristics or sticking points to keep the quest from going places you don't want it to go. Even Ruby wasn't ''that kind of girl''. If you are serious about keeping the romance to a minimum, you can also create a protagonist that is physically incapable of doing the sorts of things you don't want to draw them doing, although even this will only minimize suggestions, not eliminate them.
 
==[[BiteQuest]]'s 'Arc' Method==
I basically run quests the same way I've run my tabletop games for the most part (Lahamu being the exception). Essentially, you determine three goals, one extremely long term (which could be the quest goal), one moderate long term (whatever the protagonist is working towards - you can have more than one going on at a time, too) and a session or immediate goal. The goal doesn't have to be something you accomplish or that the character has to do before the session ends, it just needs to be what is generally going to happen in that session. I think this keeps the story focused, and minimizes confusion about what is going on and where the characters are headed. As a for-instance: BiteQuest is divided into three big 'arcs,' essentially. The first 'arc' was supposed to end with him going into the Sea of Oblivion (or deciding never to go there, whatever), and has just finished. The multi-session mini-arcs are pretty obvious - each 'delivery' in the beginning of the quest, like going from Suri to Radia's tower. Each session or immediate arc would be whatever is going to happen during those six or eight hours when I update: Spikesby's going to find Glory all crucified up in the first session for the 'Radia' miniarc.
 
This doesn't have anything to do with railroading or anything like that - as a matter of fact, I tell stories by writing up situations and just seeing what the players do. I, of course, think of a few ''likely'' outcomes, but I'm very open ended with what actually occurs. It's more of just thinking long term, and dividing big goals up into steps so things dont happen too fast and the players have something to look forward to. Your whole quest will seem a lot more tight story-wise if you keep this advice in mind, and you can even generate all three 'arcs' based on suggestions. Even Lahamu, which is essentially a sandbox game, falls into this pattern. It looks like the 'longest term' arc is to create some kind of unified multi-racial nation out of the local area, which is something the players absolutely decided to do on their own. I'd say the middle arc is probably to explore each of the cities or whatever, which is also totally something the players decided on. The current short arc is to try to bribe the goblins into working for Lahamu, which will probably finish in 3 or 4 frames. I don't even know where they'll go next, or what the next middle arc will be, but the story still falls into this rough format.
 
If you'll notice, there's been very little faffing about in Bite Quest, and I think this is the reason why.
 
I'm not attempting to imply that this is the only way to run a quest, but I think a lot of good authors seem kinda unfocused or scattered in their storytelling, and maybe they could find this advice useful.
 
=Ending a Quest=
Advice on how to actually finish one of these things. (Finish? A [[Quest]]? HAH.)
 
==Plan Some Potential Conclusions Before You Start==
 
DO NOT start a quest unless you at least have a vague idea of where you want it to go. I would strongly discourage you from actually planning out *the* ending beforehand, but have some potential conclusions planned. Know what the main conflict is going to be, and have some potential resolutions thought out in your head, even if you don't end up using any of them. I'd say this is good advice for the story arcs in the quest as well, actually. I don't plan out stories, I just set up situations and see what the players do. I won't say that this is the only way to plan for a Quest, but I think it's the best.
 
==End it with a Bang==
People like a good show. Give it to them, and make them remember it forever. You should try to really outdo yourself here, even if the quest is ridiculous or silly (some would say *especially* if it is!) Do animations, sprawling pictures, whatever. The longer you've been moving toward this moment, the greater the payoff should be, both for you and for the players. I know that drawing those last chapters and those last few frames gave me an exhausting feeling of completion, like I'd made something worthwhile.
 
* This does not mean the players/protagonist necessarily has to win. Something can be awesome and epic and still end sadly or poignantly. Even if the actions themselves aren't "epic," they can be done in an epic style.
 
==Where Are They Now?==
Be sure to 'reward' the players with a look of where the characters are, maybe five years later or ten or whatever you feel is appropriate. Make sure you include who ended up in a relationship with whom. (see point: tgchan is always a cupid.)
 
==Bad Ends==
If for whatever reason you decide that your quest must have a bad end, you should do it very, '''''very''''' carefully. Quests are pretty much one-chance things, so failure is a much bigger deal than it may seem to be at first glance. If it is a frequent bad end kind of quest, show that measurable progress is being made, no matter how small or gradual. For everything else, show that even though the ultimate goal is out of reach, impossible, or otherwise unaccomplishable, the character, with the help of the board, has made significant and lasting changes to the world around them. Nothing frustrates like spending time on what is ultimately a complete failure, especially if there is no way to reattempt.
 
==Accepting Defeat==
Sometimes... rarely... through no fault of the author... a quest just doesn't take off.  Like so many early experimental aircraft... it launches in a moment of spectacular promise... then promptly doesn't go anywhere and crashes to a standstill.  You try to do an autoupdate... and there is still no response.  You try another.  Still nothing.  You try some drastic fanservice!  No effect.
 
You must ask yourself... do you want to continue doing autoupdates like that? If you're going to be telling a story with no input from the readers... is a quest really the right form for this story?  Maybe the story just isn't interesting enough.
 
Sometimes, the hardest part about something is knowing when to let it go.  Will you just let it slide into obscurity, or give it a brief ending for euthanasia?  (Goodnight, sweet prince.)
 
*[[Vyt]]'s Arguing Insight:
 
However, you also have to dig deeper and see what it is that makes your quest not take off. Are you leaving your readers with situations where they're not able to do something? Are things taking off too fast that it makes the quest hard to understand? Or maybe it's more technical: have you updated too fast and expect multitudes of suggestions upon your feet? Accepting real "defeat" is just as tedious as trying to start one, and you don't want it to look as if you just deserted it without any planned thoughts.
 
*[[Farmer]]'s Rule of thumb
If it isn't fun anymore, its time to stop. (I do have more to say on this, but in the end, it all sums up to this)

Latest revision as of 15:35, 30 June 2018

Let me explain.png

This page offers tips and advice for running a quest! These aren't hard rules, but you may find the information here helpful for making something you and your readers enjoy.

What even is a Quest?

A quest is an interactive storytelling medium, akin to a 'choose your own adventure' book being played out as your choices are made. A character is placed in a world, and it is the job of the suggesters to guide them forward on their journey.

Part of their charm is that they aren't linear in the way a webcomic is, nor are they a single person's story. The authors and suggesters work together to weave a tale either from whole cloth, or in a world the author has built around the character(s) ahead of time.

Getting Started

Quests are a lot of work, and take a lot of dedication to run to completion. Unless the scope is very small, a quest can run for months or even years. You may have an amazing, grand idea for your quest, but it's important to not run it for your first time. Put it aside for now, and think up something small, simple, and fun to test the waters and make sure this is something for you. If you don't end up enjoying it, better to lose a small story than see a grand scheme go half-finished.

Running a 'test quest' can help you know if you're ready to put in that kind of time, or if you'd prefer to tell smaller stories that are much easier to finish.

Being an artist isn't required to run a quest, but this site has a very strong artist lean, and quests with only text or GIS images don't tend to do as well, and generally have fewer participants. Keep this in mind as you plan out your story.

Creating a setting

The protagonist

The protagonist is the eyes through which your suggesters see the world. They are the ones we'll get to know the best and form the deepest bonds with.

There's many ways an author can create a quest protagonist. Some already have a character in mind, while others prefer to let the suggesters make a new character from scratch. Both methods are perfectly fine, and it's completely up to your tastes as a storywriter. The important thing is that you remain flexible. The character should be able to learn and grow as the story goes, and the suggesters will often add to their depth over time.

If you're letting the suggesters design your protagonist, in whole or in part, be sure not to include options you don't like. If you're set on a male protagonist, don't offer the choice of gender, for example.

The world your protagonist inhabits

Creating a world for a quest is not too unlike creating one for a tabletop RPG. Some prefer to make a finely crafted world full of lore and things to see. Others like to play it by ear, or even leave the world up to the suggesters to create as they desire.

Think about what setup works for you, but be prepared for people to go places you don't expect them to go. No matter how fleshed out your world is, you'll likely have to make some things up as you go! Winging it is part of the challenge and fun of running a quest.

If you're going for a deep, lore-filled world, It can help a place feel fleshed out to have events happen that the protagonist isn't directly related to. Maybe an NPC got married since we saw them last. Maybe a city has elected a new mayor. Little things like this can help a world feel 'alive'.

Making your first thread

This is where you put it all together and present your world to the suggesters at large. In general, quests start out by setting the scene and then asking the suggesters to guide the protagonist through whatever situation they face, be it danger or asking a cute girl/boy/eldritch horror on a date. That last one actually comes up sometimes.

If the suggesters are making a character, it's usually best to start by asking them to define such things as sex (a fair warning: female wins almost every time, so if you prefer a male or other, don't leave it up for others to decide!), race (if applicable), body type, personality, skills, etc. How little or how much they decide on is up to you, and don't worry about making too many options for character generation.

Some rules of thumb for making a title post (Also known as an OP)

  • Always write the name of the quest in the subject field. This helps people find it in the archive. Please don't write "????" here.
  • Most authors write the protagonist's name (if it exists) in the name field, but this is up to your tastes. You can type a space to have it appear blank.
    • It is also acceptable to use the name field for your author name or handle, if you prefer.
    • Tripcodes are not necessary.
  • The title post should have an eye-catching image. This will help it stand out among the others.
  • The title post image should not be all black or darkness. Kind of as a corollary of the previous.
  • Don't use RubyQuest's start. Unless you're specifically going for a parody, you probably shouldn't be starting in a black room with 3 glowing buttons; it's been done to death.
  • Nobody uses the e-mail field for e-mails. In general you want to leave it blank.
  • If you're starting a new thread for an existing quest link the old thread(s) or the wiki article in the OP. Make it easy on readers who'd like to get caught up!

Methods for collecting suggestions

Once your first update is up, it's time for people to suggest ideas for how the story or character should progress! But how do you go about asking for those suggestions?

Some prefer to have the character or narrator ask directly. "What do I do next?" "What do I say to them?" Others leave it implied, simply pausing the story where it is to wait for input.

Regardless of the method you choose, remember that you do have some sway to avoid options you really don't want to happen. Your protagonist can simply refuse to consider it, or you can leave it out of the vote options. Be careful, though, as doing this too often is against the spirit of quests.

Freeform Questing

Freeform questing is when you let the suggesters post with whatever action, idea, or question they have in mind, with no effort on your part to limit their options. This method allows for great creativity, but can be hard to handle if you have too many suggestions. It also makes it a little harder to guide the story in the direction you might want it to go.

Freeform is good for NPC conversations, and for putting someone in a setting and letting them explore. It also helps the narrative flow for those who read a finished quest, as each update flows into the next without pausing to list a bunch of options.

Vote-based Questing

Vote-based questing means giving a list of options, and holding a vote on which option should win. This lets you guide the story more easily at the cost of suggestor freedom and creativity. This method is much easier to handle for large amounts of suggestions, and in some cases can increase the amount of suggestions you receive as it's easier for them to pick an option than it is to come up with something from whole cloth.

Vote-based is good for overall pacing, and giving you a rough idea of what the next piece of story might entail. It also helps prevent suggesters going for something you don't want to do, as you can simply leave it off as an option. Or, you can be flexible and let a good custom suggestion or one with a lot of support win in spite of the vote limitations. It's up to you if and where you'd want to do this.

Parsing Suggestions

Once you have some suggestions submitted, it's time to figure out how to use them and generate your next update. It should be noted there are no hard rules on how you use suggestions. The following list are all examples of strategies employed in various quests:

  • Majority Rule. Whatever the most people wants, goes.
  • Best Idea Wins. There's a correct answer or solution, and if even one person suggests it, it'll be used.
  • Everything Wins. Your protagonist tries to follow, or react to, every suggestion! Results may vary from disaster to comedy to wonderful.
  • Most In-Character Wins. Your protagonist treats the suggestions as a brainstorming session, and then runs with the idea(s) they like best. Or perhaps there's an idea so true to who the protagonist is that they can't not use it.
  • Pick and Choose. Construct a gestalt, using pieces of different suggestions and ideas to make a better (or more interesting) whole.
  • Minority Wins. Yes, really, it's been done. Probably not something you want to overuse, and it risks blowback, but subverting a vote in the right circumstances can be powerful or interesting.
  • Like I'd listen to you! Just have your character just argue with the suggesters and/or insult them while they do whatever.
  • Quota. Sometimes an option requires a minimum numbers of suggesters to support it. (Ie, "X requires 5 or more votes").
  • Stall or Clarify. Sometimes the suggesters will misunderstand the situation (or you'll present it wrong) and you'll feel the need to give them more information before a final decision is reached. Sometimes the suggesters will come up with a really good question that affects the outcome of the vote and you'll want to answer it.
  • Railroad. Sometimes the suggesters only have the appearance of choice. Employ carefully. As discussed in more detail below, it's hard to do right.

There's also no rule you have to stick with a single strategy. Different decisions can be made in different ways. You're also not limited to stick to this list if you think of other ways to use suggestions!

Running your quest: Tips and tricks

General tips

  • Don't push yourself! Know your limits and take breaks!
  • Back up your data! This is good advice in general.
    • Don't write your posts on the site. Write them in a text editor so you can save, and so you don't lose everything if you close a tab or your browser crashes.
  • A useful way to post multi-frame updates is to make several tabs, each filled with part of the update. Then you can go from tab to tab posting the entire update in seconds.
  • Try to avoid situations where there's only one option. If there's a path going left or right, don't have one lead to a dead-end. This kind of ruins the nature of letting things be up to the suggesters. If you do make a dead end, be sure to put something interesting there so there's more to do than backtrack!
  • Keep it interesting. Stopping in front of a door and asking if it should be opened isn't very interesting, unless you offer some insight about what might be behind the door.
  • Make sure each update accomplishes something, be it moving to a new location, advancing the combat, or building on characters. If a switch is pulled, it's best not to have the result be that nothing happens. If the current location or scene has no real options, go ahead and move the plot forward automatically.
  • It's against the spirit of quests to keep the story on rails. 'Railroading' is when the character does something that the suggesters either didn't suggest, or actively suggested against. It's extremely frowned upon. There are a few situations where this can be effective in giving a feeling of powerlessness, but it should be used very, very sparingly. It's very hard to do right, and much safer to avoid outright.
  • Sometimes the suggesters simply can't choose what they want. If you have votes that tie, or freeform where nobody has a consensus, then it's fine to go ahead and pick the option you feel makes for the best story (or that the protagonist is most likely to choose in a vacuum).
  • A lot of people never expand the thumbnail. Keep this in mind when planning how much detail and information goes into the artwork. If you set a precedent for hiding things in the art, people are more likely to expand images after getting burned once.
  • Be mindful of how severe the punishment is for a 'wrong' action. Trap options and bad ideas can often land the character in a poor situation. Once the character has suffered a consequence, the suggesters will be a lot more cautious, which could help or hurt depending on the mood of your quest.
  • Because there's a number of people seeing your story unfold, people will often try to guess what happens next, and they might be right. It's up to you if you want to reward them, or change your story to keep them guessing. Be mindful that doing this too much can lead to an incomprehensible story!
  • Sometimes the suggesters will come up with something better than you have. Roll with it!
  • Remember the number of people reading and enjoying a quest is generally larger than the number of people suggesting and actively contributing. And that's ok!

Suggestor tendencies

There are some ways in which suggesters can be predicted. None of these are a guarantee, but keeping them in mind can be helpful for planning your adventure.

  • They almost always pick 'female' for character generation.
  • They often prefer to make friends rather than fight.
  • They often try to flirt with any NPC you introduce.
  • They often react disproportionately to betrayal, or perceived betrayal, by NPCs.
  • Loud minorities will sometimes complain about a chosen action. Don't let them distract or discourage you!
  • They are often paranoid. Even if you're running something lighthearted, people will sometimes be afraid to do something that might lead to consequences.
  • They are easily distracted. If no effort is taken to guide the story, they will happily have the character faff about getting nothing done until they eventually lose interest in the quest. Having a quest about faffing about is fine, but make sure there's something interesting to do and that they are guided to it!
  • They love to be teased. Having the romantic interest confess right away will bore them, but having the romantic tension last a long time will keep them very much hooked.
  • They love matchmaking in general. Seriously they love the romantic tension like a lot.
  • No really, be very careful about how you handle romantic/sexual tension!!!
  • Suggesters often want what they can't have, or to attempt to derail things. In a lot of quests, that might mean pursuing romance and sex. In a porn quest, that might mean ignoring the smut you're offering and pursuing something else entirely!
Retrieved from "https://questden.org/w/index.php?title=Advice_for_Running_a_Quest&oldid=29597"