[{"data":1,"prerenderedAt":599},["ShallowReactive",2],{"help-\u002Fhelp\u002Fcamera-and-emotion":3,"help-index":409},{"id":4,"title":5,"body":6,"category":383,"description":384,"extension":385,"keywords":386,"meta":402,"navigation":403,"order":404,"path":405,"seo":406,"stem":407,"__hash__":408},"help\u002Fhelp\u002Fcamera-and-emotion.md","Set the camera and the emotion for every line",{"type":7,"value":8,"toc":373},"minimark",[9,13,21,32,54,61,66,69,132,138,149,153,197,203,207,233,239,246,250,271,277,281,300,323,329,335,339],[10,11,5],"h1",{"id":12},"set-the-camera-and-the-emotion-for-every-line",[14,15,16,20],"p",{},[17,18,19],"strong",{},"The case:"," you're making a 3D game, and every line of dialogue plays as a small cutscene. For each line your game\nneeds to know where the camera goes and how the speaking character feels. Writers choose both while they write, but\nthe game only has three camera setups and five face animations, so a writer should only be able to pick one of those.",[22,23,29],"pre",{"className":24,"code":26,"language":27,"meta":28},[25],"language-text","Captain Mara: So you're the stowaway.        camera: wide           emotion: neutral\nFinn:         I can explain!                 camera: close_up       emotion: surprised\nCaptain Mara: You have until we reach port.  camera: over_shoulder  emotion: angry\n","text","",[30,31,26],"code",{"__ignoreMap":28},[14,33,34,37,38,41,42,45,46,49,50,53],{},[17,35,36],{},"The short answer:"," add two ",[17,39,40],{},"text list"," fields to the game's meta schema, ",[30,43,44],{},"camera_position"," and ",[30,47,48],{},"emotion",", and\ntype the values your game supports as their options. Writers then pick a value for each line from a dropdown in the\nnode's ",[17,51,52],{},"Meta data"," card, and nothing else can be entered.",[14,55,56],{},[57,58],"img",{"alt":59,"src":60},"The Stowaway dialogue on the canvas: Captain Mara's line, Finn's answer and Mara's reply, linked one after another","\u002Fimages\u002Fhelp\u002Fcamera-and-emotion\u002Fcanvas.jpg",[62,63,65],"h2",{"id":64},"_1-add-the-camera_position-field","1. Add the camera_position field",[14,67,68],{},"You set this up once per game, and every dialogue in the game can use it.",[70,71,72,80,90,100,117],"ol",{},[73,74,75,76,79],"li",{},"Open the game and click the pencil next to ",[17,77,78],{},"Meta schema"," in the explorer on the left.",[73,81,82,83,86,87,89],{},"Click ",[17,84,85],{},"New field"," and name it ",[30,88,44],{},". Names use small Latin letters and underscores.",[73,91,92,93,96,97,99],{},"Set ",[17,94,95],{},"Type"," to ",[17,98,40],{},".",[73,101,102,103,106,107,110,111,110,114,99],{},"Under ",[17,104,105],{},"Options",", type the camera setups your game has, one per line: ",[30,108,109],{},"wide",", ",[30,112,113],{},"over_shoulder",[30,115,116],{},"close_up",[73,118,119,120,123,124,128,129,99],{},"Add a ",[17,121,122],{},"Comment"," like ",[125,126,127],"em",{},"Camera setup the game cuts to when the line starts",", so writers know what it does.\nClick ",[17,130,131],{},"Add field",[14,133,134],{},[57,135],{"alt":136,"src":137},"The meta schema editor: camera_position as a text list with the options wide, over_shoulder and close_up","\u002Fimages\u002Fhelp\u002Fcamera-and-emotion\u002Fcamera-field.jpg",[14,139,140,141,144,145,148],{},"The options are written exactly as your game expects them. A writer can't type ",[30,142,143],{},"closeup"," or ",[30,146,147],{},"Close Up"," by mistake,\nbecause they never type a value at all.",[62,150,152],{"id":151},"_2-add-the-emotion-field","2. Add the emotion field",[70,154,155,162,168,188],{},[73,156,82,157,159,160,99],{},[17,158,85],{}," again and name it ",[30,161,48],{},[73,163,92,164,96,166,99],{},[17,165,95],{},[17,167,40],{},[73,169,102,170,172,173,110,176,110,179,110,182,110,185,99],{},[17,171,105],{},", type one emotion per line: ",[30,174,175],{},"neutral",[30,177,178],{},"happy",[30,180,181],{},"sad",[30,183,184],{},"angry",[30,186,187],{},"surprised",[73,189,190,191,194,195,99],{},"Add a comment like ",[125,192,193],{},"Face animation the speaking character plays",", and click ",[17,196,131],{},[14,198,199],{},[57,200],{"alt":201,"src":202},"The meta schema with two text list fields: camera_position and emotion with their comments","\u002Fimages\u002Fhelp\u002Fcamera-and-emotion\u002Fschema.jpg",[62,204,206],{"id":205},"_3-pick-the-camera-and-the-emotion-on-each-line","3. Pick the camera and the emotion on each line",[70,208,209,215,226],{},[73,210,211,212],{},"Open the dialogue and select a node, here Finn's ",[125,213,214],{},"\"I can explain!\"",[73,216,217,218,220,221,223,224,99],{},"In the ",[17,219,52],{}," card, open the ",[30,222,44],{}," dropdown and pick ",[30,225,116],{},[73,227,228,229,223,231,99],{},"Open the ",[30,230,48],{},[30,232,187],{},[14,234,235],{},[57,236],{"alt":237,"src":238},"Finn's node selected: in the Meta data card, camera_position is close_up and emotion is surprised","\u002Fimages\u002Fhelp\u002Fcamera-and-emotion\u002Fnode-meta.jpg",[14,240,241,242,245],{},"The value is saved as soon as you pick it. Pick the empty choice (",[17,243,244],{},"—",") to clear it. Hover over a field to see its\ncomment and its options.",[62,247,249],{"id":248},"_4-test-it","4. Test it",[70,251,252,262,268],{},[73,253,82,254,257,258,261],{},[17,255,256],{},"Show player"," and turn on ",[17,259,260],{},"Show meta data"," at the top of the player.",[73,263,264,265,267],{},"Play the dialogue. Under every line the player shows its ",[17,266,52],{},": the camera and the emotion your game will\nuse for it.",[73,269,270],{},"Look for lines without a camera or an emotion and fill them in.",[14,272,273],{},[57,274],{"alt":275,"src":276},"The player with Show meta data on: each line shows its camera_position and emotion","\u002Fimages\u002Fhelp\u002Fcamera-and-emotion\u002Fplayer.jpg",[62,278,280],{"id":279},"variations","Variations",[14,282,283,286,287,290,291,293,294,296,297,299],{},[17,284,285],{},"One camera for a whole scene."," Draw a ",[17,288,289],{},"Meta Area"," around the nodes of a scene and set ",[30,292,44],{}," to\n",[30,295,109],{}," in its ",[17,298,52],{},". Every node inside gets the value, and the node shows which area it comes from.",[14,301,302,305,306,309,310,110,313,110,316,45,319,322],{},[17,303,304],{},"Numbers instead of names."," If your game reads a camera angle or an animation index, pick ",[17,307,308],{},"integer list"," and use\noptions like ",[30,311,312],{},"0",[30,314,315],{},"45",[30,317,318],{},"90",[30,320,321],{},"180",". Every node then holds one of those numbers.",[14,324,325,328],{},[17,326,327],{},"Change the options later."," Open the field again to add an option, reorder them or fix a typo. LoreHub won't let you\nremove an option that a node or a Meta Area still uses, and tells you which one.",[14,330,331,334],{},[17,332,333],{},"More per-line data."," The same works for anything your game needs per line: a voice-over take, a music cue, a\ncharacter's pose. Add a text list or integer list for each.",[62,336,338],{"id":337},"in-your-game","In your game",[14,340,341,342,345,346,349,350,353,354,359,360,364,365,369,370,99],{},"Each node exports its values in ",[30,343,344],{},"metaData",", as the field's id and the chosen option, and the export lists every field\nwith its type ",[30,347,348],{},"textList"," and its ",[30,351,352],{},"options",", so your game can check the values or build its own lookup from them. See\n",[355,356,358],"a",{"href":357},"\u002Fdocumentation\u002Fdialogue-schema-api\u002Fmeta-schema-v1","Meta Schema v1"," and\n",[355,361,363],{"href":362},"\u002Fdocumentation\u002Fdialogue-schema-api\u002Fdialogue-node-v2#metadata","MetaData",". In Godot, the\n",[355,366,368],{"href":367},"\u002Fdocumentation\u002Ftutorials\u002Fdialogue-system-for-godot","LoreHub Dialogue Player"," gives you the values by name on every\nline, for example ",[30,371,372],{},"line.meta[\"camera_position\"]",{"title":28,"searchDepth":374,"depth":374,"links":375},3,[376,378,379,380,381,382],{"id":64,"depth":377,"text":65},2,{"id":151,"depth":377,"text":152},{"id":205,"depth":377,"text":206},{"id":248,"depth":377,"text":249},{"id":279,"depth":377,"text":280},{"id":337,"depth":377,"text":338},"export","Give writers a fixed list of camera positions and emotions to pick from on each dialogue node, with text list fields in the meta schema.","md",[387,388,389,48,390,391,392,393,394,395,396,397,398,399,400,401],"camera","camera angle","shot","mood","facial expression","animation","cutscene","3d","cinematic","dropdown","allowed values","predefined","enum","meta data","meta schema",{},true,1,"\u002Fhelp\u002Fcamera-and-emotion",{"title":5,"description":384},"help\u002Fcamera-and-emotion","HLkXQxM5JRSqmGLwp_nkJXlZrdq3FOhqM0fusmIxlGA",{"articles":410,"sections":463},[411,433,447,449],{"path":412,"title":413,"description":414,"category":415,"order":404,"keywords":416},"\u002Fhelp\u002Fgold-coins","Give or take gold coins","Track the main character's gold with a number variable: add coins when they earn them, take coins when they pay, and offer an option only when they can afford it.","variables",[417,418,419,420,421,422,423,424,425,426,427,428,429,430,431,432],"gold","coins","money","currency","inventory","counter","add","remove","subtract","increase","decrease","number variable","buy","sell","pay","price",{"path":434,"title":435,"description":436,"category":437,"order":404,"keywords":438},"\u002Fhelp\u002Foption-only-once","Make an option the player can pick only once","Hide a dialogue option after the player picks it, with Ask once in the LoreHub Dialogue Builder. Step by step, with a list of questions as the example.","dialogue-builder",[439,440,441,442,443,444,445,446],"play once","one time","only once","ask once","hide option","already asked","repeat question","disappear",{"path":405,"title":5,"description":384,"category":383,"order":404,"keywords":448},[387,388,389,48,390,391,392,393,394,395,396,397,398,399,400,401],{"path":450,"title":451,"description":452,"category":437,"order":377,"keywords":453},"\u002Fhelp\u002Fquestion-hub","Bring the player back to a list of questions","Let the player ask questions in any order and return to the same list after each answer, with Return to options in the LoreHub Dialogue Builder.",[454,455,456,457,458,459,460,461,462],"hub","question hub","back to questions","return","loop","go back","ask again","menu","list of questions",[464,466,470,474,478,482,486,490,494,496,500,505,510,515,519,523,527,529,533,538,543,548,553,557,562,566,570,572,576,581,586,591,595],{"id":405,"title":5,"titles":465,"content":384,"level":404},[],{"id":467,"title":5,"titles":468,"content":469,"level":404},"\u002Fhelp\u002Fcamera-and-emotion#set-the-camera-and-the-emotion-for-every-line",[],"The case: you're making a 3D game, and every line of dialogue plays as a small cutscene. For each line your game\nneeds to know where the camera goes and how the speaking character feels. Writers choose both while they write, but\nthe game only has three camera setups and five face animations, so a writer should only be able to pick one of those. Captain Mara: So you're the stowaway.        camera: wide           emotion: neutral\nFinn:         I can explain!                 camera: close_up       emotion: surprised\nCaptain Mara: You have until we reach port.  camera: over_shoulder  emotion: angry The short answer: add two text list fields to the game's meta schema, camera_position and emotion, and\ntype the values your game supports as their options. Writers then pick a value for each line from a dropdown in the\nnode's Meta data card, and nothing else can be entered.",{"id":471,"title":65,"titles":472,"content":473,"level":377},"\u002Fhelp\u002Fcamera-and-emotion#_1-add-the-camera_position-field",[5],"You set this up once per game, and every dialogue in the game can use it. Open the game and click the pencil next to Meta schema in the explorer on the left. Click New field and name it camera_position. Names use small Latin letters and underscores. Set Type to text list. Under Options, type the camera setups your game has, one per line: wide, over_shoulder, close_up. Add a Comment like Camera setup the game cuts to when the line starts, so writers know what it does.\nClick Add field. The options are written exactly as your game expects them. A writer can't type closeup or Close Up by mistake,\nbecause they never type a value at all.",{"id":475,"title":152,"titles":476,"content":477,"level":377},"\u002Fhelp\u002Fcamera-and-emotion#_2-add-the-emotion-field",[5],"Click New field again and name it emotion. Set Type to text list. Under Options, type one emotion per line: neutral, happy, sad, angry, surprised. Add a comment like Face animation the speaking character plays, and click Add field.",{"id":479,"title":206,"titles":480,"content":481,"level":377},"\u002Fhelp\u002Fcamera-and-emotion#_3-pick-the-camera-and-the-emotion-on-each-line",[5],"Open the dialogue and select a node, here Finn's \"I can explain!\" In the Meta data card, open the camera_position dropdown and pick close_up. Open the emotion dropdown and pick surprised. The value is saved as soon as you pick it. Pick the empty choice (—) to clear it. Hover over a field to see its\ncomment and its options.",{"id":483,"title":249,"titles":484,"content":485,"level":377},"\u002Fhelp\u002Fcamera-and-emotion#_4-test-it",[5],"Click Show player and turn on Show meta data at the top of the player. Play the dialogue. Under every line the player shows its Meta data: the camera and the emotion your game will\nuse for it. Look for lines without a camera or an emotion and fill them in.",{"id":487,"title":280,"titles":488,"content":489,"level":377},"\u002Fhelp\u002Fcamera-and-emotion#variations",[5],"One camera for a whole scene. Draw a Meta Area around the nodes of a scene and set camera_position to\nwide in its Meta data. Every node inside gets the value, and the node shows which area it comes from. Numbers instead of names. If your game reads a camera angle or an animation index, pick integer list and use\noptions like 0, 45, 90 and 180. Every node then holds one of those numbers. Change the options later. Open the field again to add an option, reorder them or fix a typo. LoreHub won't let you\nremove an option that a node or a Meta Area still uses, and tells you which one. More per-line data. The same works for anything your game needs per line: a voice-over take, a music cue, a\ncharacter's pose. Add a text list or integer list for each.",{"id":491,"title":338,"titles":492,"content":493,"level":377},"\u002Fhelp\u002Fcamera-and-emotion#in-your-game",[5],"Each node exports its values in metaData, as the field's id and the chosen option, and the export lists every field\nwith its type textList and its options, so your game can check the values or build its own lookup from them. See\nMeta Schema v1 and\nMetaData. In Godot, the\nLoreHub Dialogue Player gives you the values by name on every\nline, for example line.meta[\"camera_position\"].",{"id":412,"title":413,"titles":495,"content":414,"level":404},[],{"id":497,"title":413,"titles":498,"content":499,"level":404},"\u002Fhelp\u002Fgold-coins#give-or-take-gold-coins",[],"The case: the main character carries gold. A merchant sells bread for three coins and buys their old sword for five. The player can only buy bread while they have at least three coins. Gold: 10\nMerchant: Fresh bread, three coins a loaf. Anything else?\n  1. Buy bread (3 coins)\n  2. Sell my old sword\n  3. Goodbye.\nPlayer picks 1.\nMerchant: Here you go, still warm.\nGold: 7 The short answer: create a number variable gold. On the node where the player pays, add Set variable with gold −= 3. On the node where they earn coins, gold += 5. Give the buy option the condition gold ≥ 3.",{"id":501,"title":502,"titles":503,"content":504,"level":377},"\u002Fhelp\u002Fgold-coins#_1-create-the-gold-variable","1. Create the gold variable",[413],"Click the pencil next to Variables in the explorer on the left. Click New variable and name it gold. Names use small Latin letters and underscores. Set its type to Unsigned number, a whole number that never goes below 0. Under Starts as, enter how many coins the player has at the start, for example 10. Add a comment like Coins the player carries, so everyone on the team knows what it means. Click Save. Pick Number instead if gold can go negative, for example to allow debt.",{"id":506,"title":507,"titles":508,"content":509,"level":377},"\u002Fhelp\u002Fgold-coins#_2-take-coins-when-the-player-pays","2. Take coins when the player pays",[413],"Select the node that plays after the player pays, here \"Here you go, still warm.\" Under On start, set, click Set variable and pick gold. Choose −= and enter 3. The coins change when the node plays. To give coins, do the same on the node where the player earns them, with +=: here \"Five coins for it\" gets gold += 5. Choose = to set an exact amount, for example gold = 0 when the player is robbed.",{"id":511,"title":512,"titles":513,"content":514,"level":377},"\u002Fhelp\u002Fgold-coins#_3-offer-the-option-only-when-the-player-can-pay","3. Offer the option only when the player can pay",[413],"Select the merchant's node. On Buy bread (3 coins), click + condition and pick gold. Choose ≥ and enter 3. Now the player only sees Buy bread while they have three coins or more. The option shows a filter badge with its number of conditions on the canvas. To let the player come back to the merchant's options after buying, link the answer back to the merchant's node with Return to options. See Bring the player back to a list of questions.",{"id":516,"title":249,"titles":517,"content":518,"level":377},"\u002Fhelp\u002Fgold-coins#_4-test-it",[413],"Click Show player and play the dialogue. Watch gold in the Variables column while you buy bread: 10, 7, 4, 1. With 1 coin left, Buy bread is faded with gold ≥ 3 next to it. In your game the player won't see it. You can change gold in the Variables column to test other amounts without playing up to them. Click Restart to start again with 10 coins.",{"id":520,"title":280,"titles":521,"content":522,"level":377},"\u002Fhelp\u002Fgold-coins#variations",[413],"Sell only once. Turn on Ask once on Sell my old sword, since the player has only one sword. See Make an option the player can pick only once. Branch on the amount. Give the links from a node conditions, like gold ≥ 100 to one line and no condition to another. The game follows the first link whose conditions are met.",{"id":524,"title":338,"titles":525,"content":526,"level":377},"\u002Fhelp\u002Fgold-coins#in-your-game",[413],"gold is exported with the dialogue's variables and its starting value. A node exports its change in setVariableOnStart with operation set to add or subtract, and the option's condition with operator >=. See Variable v1 and SetVariableOnStart.",{"id":434,"title":435,"titles":528,"content":436,"level":404},[],{"id":530,"title":435,"titles":531,"content":532,"level":404},"\u002Fhelp\u002Foption-only-once#make-an-option-the-player-can-pick-only-once",[],"The case: the player talks to an innkeeper and can ask several questions: Who are you?, What's this town called?, Any work for me?. After each answer the player is back at the list of questions, but a question they have already asked shouldn't be offered again. Goodbye is always there, so the player can leave. The short answer: select the node with the options and turn on Ask once on each question. Then link each answer back to the node's options with Return to options.",{"id":534,"title":535,"titles":536,"content":537,"level":377},"\u002Fhelp\u002Foption-only-once#before-you-start","Before you start",[435],"You need a dialogue with a node that has options, and a node for each answer. If you are starting from scratch: Open your dialogue in the Dialogue Builder. Write the innkeeper's greeting in a node, for example \"Welcome, traveller. What can I do for you?\" Add the questions as options: click + Option on the node, or select the node and click Add option in the inspector. Add a node for each answer, and drag from each option's dot to its answer node.",{"id":539,"title":540,"titles":541,"content":542,"level":377},"\u002Fhelp\u002Foption-only-once#_1-turn-on-ask-once","1. Turn on Ask once",[435],"Click the node with the options to open it in the inspector. Under Options, find the question and turn on Ask once below it. Do the same for every question that should be asked only once. Leave Ask once off on Goodbye. The option's Visible when now shows a once chip, and the option gets a once pill on the canvas, so you can see at a glance which options disappear.",{"id":544,"title":545,"titles":546,"content":547,"level":377},"\u002Fhelp\u002Foption-only-once#_2-bring-the-player-back-to-the-questions","2. Bring the player back to the questions",[435],"An option that is asked once only makes sense if the player comes back to the list. After each answer, link back to the node with the questions: Drag from the answer node's dot to the innkeeper's node. Select the answer node. Under Links, turn on Return to options for the new link. With Return to options, the player skips the innkeeper's greeting and sees the questions again, minus the ones already asked. Without it, the greeting would play again first. Return to options shows only when the link goes to a node that has options. You'll also find it in the inspector when you select the link itself, and on an option's link under Goes to, if an option leads straight back.",{"id":549,"title":550,"titles":551,"content":552,"level":377},"\u002Fhelp\u002Foption-only-once#_3-leave-a-way-out","3. Leave a way out",[435],"Keep at least one option without Ask once that leads on, like Goodbye. If every option is asked once and every one leads back, the player ends up with nothing to pick. The inspector warns you about this on the node: Every option is asked once and leads back here, so the player runs out of options. Add an option that leads on, or turn off Ask once on one of them.",{"id":554,"title":249,"titles":555,"content":556,"level":377},"\u002Fhelp\u002Foption-only-once#_4-test-it",[435],"Click Show player and play the dialogue. Pick Who are you?. After the answer you are back at the questions. Who are you? is now faded, with its condition next to it. Hover it to see Hidden in the game: its condition is not met. In your game the player won't see it at all. The test player still lets you click a faded option, so you can check the rest of the dialogue without starting over. Click Restart to play from the beginning with every question available again.",{"id":558,"title":559,"titles":560,"content":561,"level":377},"\u002Fhelp\u002Foption-only-once#turn-it-off","Turn it off",[435],"Turn off Ask once on the option, or click the cross on its once chip.",{"id":563,"title":280,"titles":564,"content":565,"level":377},"\u002Fhelp\u002Foption-only-once#variations",[435],"Unlock a question after another one. Say Any work for me? should appear only after the player asked Who are you?. On Any work for me?, click + condition, pick stateData.isOptionSelected under Predefined variables, then pick Who are you?. The condition starts as true: the option shows once Who are you? was picked. Click the value to switch it to false for the opposite. React to a line the player has already heard. stateData.isNodePlayed works the same way for nodes: it checks whether the player has already seen a node. Use it on an option, or on a link, to play a different line the second time round. Remember it in other dialogues. Ask once remembers what was picked in this dialogue. If another dialogue needs to know that the player asked the question, use a variable instead: set it on the answer node with Set variable, and check it with + condition wherever you need it.",{"id":567,"title":338,"titles":568,"content":569,"level":377},"\u002Fhelp\u002Foption-only-once#in-your-game",[435],"If you load LoreHub dialogues into your own engine, Ask once is exported as a condition on the option: the option's own stateData.selected must be false. Your game marks an option selected when the player picks it, and checks the conditions again each time it shows the options. The LoreHub Dialogue Player for Godot does this for you. For the JSON, see state data conditions and StateData.",{"id":450,"title":451,"titles":571,"content":452,"level":404},[],{"id":573,"title":451,"titles":574,"content":575,"level":404},"\u002Fhelp\u002Fquestion-hub#bring-the-player-back-to-a-list-of-questions",[],"The case: Sam asks the player if they have questions, and the player can ask them in any order. After each answer, Sam shows the same questions again, until the player says That's all. Sam: Do you have questions?\n  1. Who are you?\n  2. Where are we?\n  3. What time is it now?\n  4. That's all.\nPlayer picks 2.\nSam: Eastbrook, by the old mill.\n  1. Who are you?\n  2. Where are we?\n  3. What time is it now?\n  4. That's all. The short answer: link each answer back to Sam's node and turn on Return to options on that link.",{"id":577,"title":578,"titles":579,"content":580,"level":377},"\u002Fhelp\u002Fquestion-hub#_1-write-the-questions-and-the-answers","1. Write the questions and the answers",[451],"Open your dialogue in the Dialogue Builder. Write Sam's line in a node: \"Do you have questions?\" Add the questions as options: click + Option on the node, or select it and click Add option in the inspector. Add That's all. as the last option. Add a node for each answer, and drag from each question's dot to its answer. Drag from That's all. to the node where the conversation goes on, or to a goodbye line.",{"id":582,"title":583,"titles":584,"content":585,"level":377},"\u002Fhelp\u002Fquestion-hub#_2-link-each-answer-back-to-the-questions","2. Link each answer back to the questions",[451],"Drag from the answer node's dot back to Sam's node. Select the answer node. Under Links, turn on Return to options. Do the same for every answer. With Return to options, the player skips \"Do you have questions?\" and goes straight back to the list. Without it, Sam would say the line again before every list. Return to options shows only when the link goes to a node that has options.",{"id":587,"title":588,"titles":589,"content":590,"level":377},"\u002Fhelp\u002Fquestion-hub#_3-test-it","3. Test it",[451],"Click Show player and play the dialogue. Pick Where are we? and click Continue after the answer. The player shows Back to the options of node_01 and the same four questions again.",{"id":592,"title":280,"titles":593,"content":594,"level":377},"\u002Fhelp\u002Fquestion-hub#variations",[451],"Hide a question once it's asked. Turn on Ask once on the question. See Make an option the player can pick only once. Unlock a question after another one. On the new question, click + condition, pick stateData.isOptionSelected and then the question it depends on.",{"id":596,"title":338,"titles":597,"content":598,"level":377},"\u002Fhelp\u002Fquestion-hub#in-your-game",[451],"A link with Return to options is exported with \"entry\": \"options\". When your game follows it, show the node's options again without its lines, and check each option's conditions again. The LoreHub Dialogue Player for Godot does this for you. See Link v1.1 for the JSON.",1794849527931]