jschomay/ene-editor

Online editor for Elm Narrative Engine

Hi, I'm Jeff. I like to explore that special place where games, narrative, and AI intersect. I made the Elm Narrative Engine for making non-linear story games and lately I've been experimenting with generative AI in games.

Play Deadline Escape the subway before it is too late	Adding Inworld AI Characters to an Existing Game, Part 3: Reflections, Trust, and Pigeons What I learned from my players and my characters	Adding Inworld AI Characters to an Existing Game, Part 4: Going Deeper Getting the most out of AI chat bots	Getting Lost in the Forest Postmortem on Using AI Generative Tools to Create a Forest Maze Game

Follow on LinkedIn

Follow on Twitter

ene-editor's Issues

Autocomplete for the ENE query syntax in data tables

I want autocomplete when editing data in the tables that will complete manifest ids, and properties. The tricky part is matching multiple mid-line completion triggers, along with storing the correct indexed data to back it. This will only apply for certain fields, notably the rule matchers, but possibly also the manifest ids.

I suggest using https://leaverou.github.io/awesomplete/.

For example, if the id "bob" and "garden" exists, and the tag "character" and the link "location" exist, the autocomplete would work as follows:

Type "bo" -"bob" suggested
Continue to type "bob." - "character" and "location->" suggested.
Continue to type "bob.character.lo" - "location->" suggested.
Continue to type "bob.character.location->" - "bob" and "garden" suggested.

• note, ENE syntax is a work in progress, it will ge solidified and documented as it comes together

Tables

A database/excel-like way to add and manage content.

Needs full CRUD, sort, filter, search, paginate functionality.

Consider using http://tabulator.info/ as a drop-in solution. https://editor.datatables.net/ is also nice (I particularly like the pop-up edit modal), but it is expensive.

All data in table needs to be stored in a way that can be saved (probably in the browser's Index DB or something) and exported (probably as JSON).

We need the following tables:

1. Manifest - id+props|name|description
2. Rules - id|trigger matcher|additional conditions|changes|narrative

Basic layout

Should have 2 tabs/pages

1. Preview/Debug
   Most of the screen will have the embeded game

2. Editor
   Has 2 tabs (?) - A table for the manifest, and a table for the rules. When the rules are active, half of the screen has a place for a visual graph of the rules

Somewhere will be some ui to export/get help/etc