[{"data":1,"prerenderedAt":211},["ShallowReactive",2],{"news-\u002Fnews\u002Fpredefined-meta-lists":3},{"id":4,"title":5,"author":6,"body":7,"date":198,"description":199,"draft":200,"extension":201,"image":202,"imageAlt":203,"imageCredit":6,"meta":204,"navigation":205,"path":206,"seo":207,"seoTitle":6,"stem":208,"tag":209,"__hash__":210},"news\u002Fnews\u002Fpredefined-meta-lists.md","Meta fields with a fixed list of values",null,{"type":8,"value":9,"toc":189},"minimark",[10,14,36,41,121,125,128,145,149,165,169],[11,12,5],"h1",{"id":13},"meta-fields-with-a-fixed-list-of-values",[15,16,17,18,22,23,26,27,31,32,35],"p",{},"A text field takes anything. One writer types ",[19,20,21],"code",{},"close_up",", the next types ",[19,24,25],{},"closeup",", and the game, the voice script or a render script has to guess what each one means. Two new meta schema types fix that: a ",[28,29,30],"strong",{},"text list"," and an ",[28,33,34],{},"integer list",". You write the values once in the meta schema, and every node picks one of them.",[37,38,40],"h2",{"id":39},"whats-new","What's new",[42,43,44,89,99,109,115],"ul",{},[45,46,47,50,51,53,54,56,57,60,61,64,65,64,68,71,72,75,76,60,79,64,82,71,85,88],"li",{},[28,48,49],{},"Text list and integer list."," When you add a field to the meta schema, pick ",[28,52,30],{}," or ",[28,55,34],{}," next to text and integer, then type the options one per line. A ",[19,58,59],{},"camera_angle"," field could take ",[19,62,63],{},"0",", ",[19,66,67],{},"45",[19,69,70],{},"90"," and ",[19,73,74],{},"180",", and a ",[19,77,78],{},"mood",[19,80,81],{},"calm",[19,83,84],{},"tense",[19,86,87],{},"angry",".",[45,90,91,94,95,98],{},[28,92,93],{},"Pick, don't type."," In the node inspector's ",[28,96,97],{},"Meta data"," card, a list field is a dropdown of its options. The empty choice clears the value.",[45,100,101,104,105,108],{},[28,102,103],{},"Meta Areas too."," A Meta Area rule on a list field picks its value from the same options, so a whole scene gets ",[19,106,107],{},"camera_angle = 45"," in one go.",[45,110,111,114],{},[28,112,113],{},"Options you can change."," Add options, reorder them or fix a typo later. LoreHub won't let you remove an option a node or a Meta Area still uses, and it tells you which one, so no node is left holding a value that no longer exists.",[45,116,117,120],{},[28,118,119],{},"Checked everywhere."," The API and the LoreHub MCP refuse a value that isn't an option, and the error lists the options. The dialogue export includes each list field's options, so your game can read them too.",[37,122,124],{"id":123},"why-integers","Why integers",[15,126,127],{},"Some meta data is read by code, not by people. A camera angle, a portrait index or a text speed goes straight into the engine. With an integer list, the value on every node is a number the engine already knows how to handle.",[15,129,130,131,136,137,139,140,144],{},"It also works for AI tools. With the ",[132,133,135],"a",{"href":134},"\u002Fmcp","LoreHub MCP"," and the Blender MCP, an AI assistant can read a dialogue's Storyboard, take each shot's ",[19,138,59],{},", turn the camera in your Blender scene and render a reference image for the shot. Because the angle is one of a few fixed numbers, every render matches what the director chose. The ",[132,141,143],{"href":142},"\u002Fstoryboard-guide#render-shots-with-blender","Storyboard guide"," shows how.",[37,146,148],{"id":147},"how-to-use-it","How to use it",[15,150,151,152,155,156,159,160,53,162,164],{},"Open a game, click the pencil next to ",[28,153,154],{},"Meta schema"," in the explorer, and click ",[28,157,158],{},"New field",". Pick ",[28,161,34],{},[28,163,30],{},", type one option per line, and save. Then select a node, or a Meta Area, and pick a value.",[37,166,168],{"id":167},"try-it","Try it",[15,170,171,172,178,179,53,184,88],{},"Text lists and integer lists are available on every plan. Open a game in ",[132,173,177],{"href":174,"rel":175},"https:\u002F\u002Florehub.app",[176],"nofollow","LoreHub"," and give it a try. If something feels off, tell us on ",[132,180,183],{"href":181,"rel":182},"https:\u002F\u002Fdiscord.com\u002Fchannels\u002F663035283419168808\u002F976393281615306772\u002F976393527468634143",[176],"Discord",[132,185,188],{"href":186,"rel":187},"https:\u002F\u002Fwww.reddit.com\u002Fr\u002Florehub",[176],"Reddit",{"title":190,"searchDepth":191,"depth":191,"links":192},"",3,[193,195,196,197],{"id":39,"depth":194,"text":40},2,{"id":123,"depth":194,"text":124},{"id":147,"depth":194,"text":148},{"id":167,"depth":194,"text":168},"2026-11-11","A meta schema field can now be a list of predefined text or integers, like camera angles 0, 45 and 90. Nodes and Meta Areas pick one, so every value is one your game and your tools understand.",false,"md","\u002Fimages\u002Fnews\u002Fpredefined-meta-lists\u002Fcover.png","The meta schema editor adding lens_mm as an integer list with the options 18, 35, 50 and 85, next to a node whose Meta data card shows camera_angle and mood as dropdowns",{},true,"\u002Fnews\u002Fpredefined-meta-lists",{"title":5,"description":199},"news\u002Fpredefined-meta-lists","Release","bXb-0qDc_ueh-iQrKSW-Dwp7VP2F18cXuUqofBVSTAk",1794392336461]