Articy Draft 3 Notes

<h2>Contents</h2>
<ul>
  <li><a href="#foreword">Foreword</a></li>
  <li><a href="#notes">Notes</a></li>
  <li><a href="#flow_editor">Flow Editor</a>
    <ul class="a">
      <li><a href="#fe_keyterms">Key Terms</a></li>
    </ul>
  </li>
  <li><a href="#scripting">Scripting</a></li>
  <li><a href="#templates">Templates</a>
    <ul class="a">
      <li><a href="#temp_best">Best Practices</a></li>
    </ul>
  </li>
  <li><a href="#docview">Document View</a>
    <ul class="a">
      <li><a href="#doc_notes">Notes</a></li>
    </ul>  
  </li>
</ul>
<h2 id="foreword">Foreword</h2>
<p><a href="https://www.articy.com/" target="_blank">Articy:Draft</a> is an expensive-ish tool for what it does. It's a visualizer for narrative content, whether that's in-game text, dialogue, locations, lore, or various metadata for prose writing. I tried really hard to use it for my creative writing. According to Steam, I've put over 1,043 hours into the software. This is at least as much time as I've spent drafting my published work, as I always had the program open alongside whatever word processor I was using. The thing was, I never felt like I made full use of the tool. I'm documenting my re-discovery here in an effort to gain a more complete understanding of its capabilities. I hope you learn something, too.</p>
    <p></p>
<h2 id="notes">Notes</h2>
<ul>
  <li>The workspace can be expanded by adding extra tabs, mousing to the edge and dragging out new panes, and opening further instances of articy.</li>
  <li>Expanding a pane to monitor Property Inspector while clicking through Nodes is a good practice.</li>
  <li><strong>Query</strong> is the built-in, SQL-like search language. It can be used to find any object within a project. <a href="https://www.articy.com/download/documentation/ArticyDraft%20-%20Query%20Language.pdf" target="_blank">Link to documentation</a>.</li>
  <li>Export to Unreal Engine is imported via articy's plugin. <a href="https://github.com/ArticySoftware/ArticyImporterForUnreal" target="_blank">Link to documentation</a>.</li>
</ul>
<h2 id="flow_editor">Flow Editor</h2>

Key Terms

Scripting

Templates

Best Practices

Workflow

  1. Create Feature(s).
  2. Create Template.
  3. Add Feature(s) to Template.
  4. Create Entity.
  5. Apply Template to Entity.
  6. Construct narrative.
  7. </ol>
    <h2 id="docview">Document View</h2>

    Notes

    • Ctrl+Enter adds a new Dialogue Fragment.
    • Dragging and dropping from the left side of a Document title into the Flow will convert the Document into a Node. Note: this creates an unlinked copy of the content.

    2021.01.11


    Previous: Substance Tools Notes
    Home
    Next: Unreal Engine Notes