📜 [Feedback] EOS Script Parser

[MetalLife]

Hey all,

Since the EOS editor can sometimes be quite cumbersome due to the lack of quality of life features I've started experimenting with writing a parser (similar to RenPy) that can convert text files like these:

Code: Select all

image
say custom 10 skip "This is a test"
timer secret 5
prompt someVariable
notification_create notification_id "NotificationTitle"
audio audio_id "some.mp3"

into a JSON equivalent that can then be added to an exisiting tease:

Code: Select all

{
  "image": {
    "locator": ""
  }
},
{
  "say": {
    "label": "<p>This is a test</p>",
    "mode": "custom",
    "duration": "10s",
    "allowSkip": true
  }
},
{
  "timer": {
    "duration": "5s",
    "style": "secret"
  }
},
{
  "prompt": {
    "variable": "someVariable"
  }
},
{
  "notification.create": {
    "title": "NotificationTitle",
    "id": "notification_id"
  }
},
{
  "audio.play": {
    "locator": "file:some.mp3",
    "id": "audio_id"
  }
}

This way you can write pages more efficiently by simply feeding the parser with your text files.

Obviously, this is a very very simple example and the parser has to be a lot more sophisticated than that but before spending too much time on it I was wondering if this is something that creators are actually interested in?

I appreciate your feedback!

[PlayfulGuy]

It's an interesting idea. I do most of my creating offline for GuideMe so can't really comment, but it seems like it could be a useful tool. It will be interesting to see if any of the more regular creators chime in.

That said, if it's something that you would use, why not go ahead and develop it for yourself, and share it for any who might be interested?

PG

[Yo_Boy_123]

I can confidently say I'd get at least some use out of this. It would be most helpful to me for simple, semi repetitive uses within a larger tease project, but considering how much of a nuisance those can be to write out by hand, this sounds great!