Difference between revisions of "Dialogue Tutorial"
Jump to navigation
Jump to search
Added pics and a few subheadings
imported>Elessar VPR (new tutorial focussing on dialogue) |
imported>Elessar VPR (Added pics and a few subheadings) |
||
|
For example, if your user-name is MrOblivion and you are working on a mod to add new quests to the Fighters Guild you could prefix each thing in your mod with ''MObFG'' followed by something more descriptive for the quest. In this tutorial we'll have a bash at good old rat killing, so we could call our quest ''MObFGCrabKill''. The advantage of doing things like this, is that it makes all your quests etc. easy to find.
Also before we go much farther, save! (doing so regularly is a good idea)
Ok, so now we have a nice new quest we need to give it a good name. In the Quest Name box name it something exciting as this is what appears in the player's journal ('''''Note:''' If you are adding dialogue to things that don't appear in the journal,
it isn't strictly necessary to fill this in)''.
[[Image:DialogTute-Data_tab.jpg|thumb|right|Outline of the Quest Data Tab]]
==I want you to
This is where the majority of dialogue creation takes place and at first glance can be a bit overwhelming, but don't worry it's not as bad as it looks! There are four main sections to the Topics Tab:
[[Image:DialogTute-topics_tab.jpg|thumb|right|Outline of the Topics Tab]]
*The Topics List (to the right of the quest list)
*The Info List (the grid at the top third of the right hand side)
===The Greeting===
Topics are the things that appear as clickable options when speaking to an NPC. Each topic can have several lines of 'Info' assigned, depending on who you're speaking to, the stage of the game/quest etc. One very important topic is the GREETING topic. This is the topic that NPCs say when you first activate them to greet you! Let's add the GREETING topic to our quest now. Right click on the Topics List and select 'Add Topic', then scroll down until you find GREETING select it then click Ok.
Right now the topic is added let's add a line to say. To do this right click (bet you never saw that one coming!) on the Info List grid and select new. This will bring up a new window called the 'Response Window'. The top bit of this is where you want to add the line of greeting you want your NPC to say. Enter in the greeting now and hit enter (don't worry about the other sections for now). If you make a mistake and want to change what the line says just double click on the relevant line.
[[Image:DialogTute-Response.jpg|thumb|120px|right|Our new line in the response window, don't worry about the bottom bit for now]]
Now we have a line of greeting! Unfortunately as it is now, everyone in Tamriel will say this greeting, so we turn again to those conditions. You'll notice the bottom third of the Topics Tab is very similar to the conditions bit we looked at earlier. Make sure the line is selected then create a new condition. This time we are looking for the ''GetIsID'' condition (remember the ''GetIsPlayableRace'' condition is already being applied to every line we add in this quest). For the 'function parameter' of the ''GetIsID'' condition click the button (will be labelled INVALID) then find the NPC you want to say the line and select it. Now only that specific NPC will say the line. By playing around with the various conditions used you can specify who says what and when.▼
▲Now we have a line of greeting! Unfortunately as it is now everyone in Tamriel will say this greeting, so we turn again to those conditions. You'll notice the bottom third of the Topics Tab is very similar to the conditions bit we looked at earlier. Make sure the line is selected then create a new condition. This time we are looking for the ''GetIsID'' condition (remember the ''GetIsPlayableRace'' condition is already being applied to every line we add in this quest). For the 'function parameter' of the ''GetIsID'' condition click the button (will be labelled INVALID) then find the NPC you want to say the line and select it. Now only that specific NPC will say the line. By playing around with the various conditions used you can specify who says what and when.
===A new topic of conversation!===
Now we have the NPC greeting sorted, but what about other lines and topics we want to speak to them about? For that we need to create a new topic. To do this go back to the Add Topic window (where you found GREETING), then right click in there and select new. Name your topic (I'll use MObFGAboutCrabs), select it and hit OK and we have a nice new topic. Now, let's add a few bits of info in there, eg. say we have a topics about 'Mudcrabs' you could have one line saying how they had some for dinner earlier and another about how irritating they are when you are sunbathing on the beach.
[[Image:DialogTute-New_topics.jpg|thumb|right|Making our new topic]]
===Stages of the quest===
First things first let's make another new topic to ask about that will start us off on our crustacean killing spree, eg ''MObFGCrabSpree'', and set the topic text to something more sensible, like 'Crab culling'. Now let's head off somewhere new, the 'Quest Stages' tab! This is where you can control how a quest progresses and what happens as each stage is done. In the empty grid, right click and create six new stages. Each stage should be a number, eg. 0, 10, 20, 25, 30 and 100. Conventionally, quests start of at a low stage and progress up to the higher stages, usually being completed at 100 (However if required you can have stages 0-255 inclusive!).
Now we have our stages made, we want to now which stage means what in the scheme of the quest. For the purposes of this tutorial the stages made will have the following relevance:
Not every stage has to be used as the quest progresses, so if the player accepts the quest straight off, stages 20 and 25 will never be required.
[[Image:DialogTute-Quest_Stages.jpg|thumb|right|The Stages Tab outlined]]
===Decisions, Decisions===
Go back to the Topics tab and we'll start creating the dialogue to match the relevant stages of the quest. We've already created a topic about the culling, so let's create a new line of info in there. If we want our NPC to fully explain why she wants us to go around skewering crabs it may take us more characters than the response will let us have. However this isn't a problem, as we can have lots of lines flow into each other. To do this create the first bit of want you want the NPC to say as normal. Once you have done that select the line, then in the 'Response Text' grid part of the Response details outline, right click and create new lines as necessary such that the player is given the option of helping or not. You'll not that the number of lines you have flowing into each other is noted in the column
===As the plot progresses===
Now we need to take care of progressing the quest in light of the player's response. To do that we'll use the Result Script box and the [[SetStage]] function. In the result script box for the negative reply add the line:
SetStage MObFGCrabKill 10
For the positive response set the stage to 20 instead of 10. This will add the relevant entries to the players journal. Now we should give the player the option of reconsidering if they decided not to help. To do this go back to the topic MObFGCrabSpree (if you are following what I'm doing). Create a new line, something like "Have you reconsidered, will you help me reclaim my bathing spot?" Set the ''GetIsID'' condition, then create another condition. This time find the ''GetStage'' condition, set it to your quest and enter the value as 10 to indicate that this line will be said only if the player has declined the mission previously. While we're here, it would be sensible to add the same condition but set to 0, for the line we made in this topic earlier (with careful ordering of the lines, this isn't necessary but better safe than sorry!). Add the yes/no options into the choices box as before.
*The player returns without enough crab meat.
*The player returns with enough crab meat.
Head back to the MObFGCrabSpree topic and create a new line about the player having enough meat. This time we are going to utilise the OR checkbox in our conditions. Set the ''GetIsID'' condition as normal and then create two ''GetStage'' conditions, one with a value of 20 and the other 25. Now obviously the quest stage can't be both 20 and 25 at the same time so we need to use the OR checkbox. Move your ''GetIsID'' condition to the top of the list, either using the cursor keys or the arrow buttons. Now on the 2nd condition down (doesn't matter which ''GetStage'' it is) check the OR box.
GetIsID MyNPC AND (GetStage is 20 OR GetStage is 25)
However we still need to check if the player has enough crab meat! So create another condition and set it as ''GetItemCount'' and set the parameter to 'CrabMeat'. Now we want to check how much meat the player has, not the NPC, so check the 'Run On Target' box. I presume you had the NPC tell the player how much meat she wants as proof you've killed enough crabs (if not go back now and say so, unless you want the player to find out by trial and error!). Let's say the NPC wants 7 pieces of meat, so set the value of ''GetItemCount'' to 7. However by default this is an equals comparison, but what if the player has hunted down every crab in Tamriel and has 1000's of crab meat! Let's change the comparison to 'Is Greater Than' (>=, for an explanation of the other comparisons see the last section). I'll let you figure out where in the list the condition can be using the logic above. Now create the corresponding response for if the player doesn't have enough crab meat, but use the less than condition instead.
===Finishing it off===
So we have one happy NPC, but what about the reward and such like!? Go back to the response for if the player has enough crab meat. Firstly we have to advance the stage to give the player the journal entry, then we should give the player a reward such as 100 gold, then remove the crab meat asked for. To do this we'll use the result script box:
==My NPC's are mute!==
===The silent type===
So your NPC's can translate their facial into text, but what if it flies by to fast to read? I recommend using ScripterRon's excellent utility found [[TES4_Plugin_Utility|here]], to solve this problem. It has the ability to create silent mp3 files for each of your lines so you have time to read them.
===The vocal type===
Of course you may decide you want to have your NPC's fully vocal and screaming about there love of crab meat in your ears. To do this first you need a voice file. If you have a mic and fancy voicing the NPC youself, I recommend [[Audacity]] as a good
free program with which to record with. Once you have the voice done, save it as a .wav file (chose 'Export as wav' if using Audacity). Now comes the tedious bit. You need to place each voice file in exactly the right place, with the right name. To find out where and what the file should be, go to your line and double click on it to bring the Response window back up. Now we are interested in the bottom section. Firstly rename the file to whatever it says the 'Voice Filename' should be (remember
to keep the extension as it is!).
[[Image:DialogTute-Response.jpg|thumb|100px|right|Finding The path and name for our file]]
Ok, so far so good. Now we need to convert the .wav files into .mp3 files, which are the ones the game actually plays. This can be a little tricky as the .mp3 file needs to have specific settings, however this [[MP3_Conversion_Batch-File|handy utility]] will take care of all that for you. That's it, you can discard the .wav files now as they are no longer needed. If you want to know the settings required for the mp3 see [[Audio_Settings_For_Dialogue_Video_Tutorial|this page]], which also contains a little video about getting voices into the game if you need more help.
==Common Errors==
===I only see rumours!/My topics aren't showing===
Ensure that you have added your topics properly and remember not to use the add topics box if you want to add them via a default line!
===NPCs won't say my stuff===
Check your quest priority is high, else everything will be said before your stuff!
===Everyone is saying my stuff===
Tut tut! You didn't specify who was to say your line did you, so everyone is. Go set GetIsID or a similar condition!
| |||