Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Export quests #80

Open
MrDienns opened this issue Jan 2, 2022 · 3 comments
Open

Feature request: Export quests #80

MrDienns opened this issue Jan 2, 2022 · 3 comments
Assignees

Comments

@MrDienns
Copy link

MrDienns commented Jan 2, 2022

Happy new year!

It seems that GoNorth has a set of export features, combined with a scripting language, which can allow anyone to create a smoother end-to-end integration from design into actual game implementation. This is very awesome. What we did notice is that quests are currently excluded from this, as we do not see the same functionality being available there.

We would like the export & scripting capabilities to be extended into quests, so that we can create our own export script and optimize our design to implementation flow. Is there any possibility in getting this added?

@steffendx
Copy link
Owner

Thanks! Happy new year!

You are right. Quests are currently only supported to be exported in JSON format since this is quite a bit of work and I am not sure yet how to export the text nodes for example. Since the idea behind these was to describe what is going on in the quest.

Are you mainly looking to export the action and conditions nodes of the quests to script? That might be possible to implement. But I dont yet have a fixed timeline for the next release so it might take a bit of time until I am able to get this ready.

@MrDienns
Copy link
Author

MrDienns commented Jan 5, 2022

Basically, quests are defined as a series of JSON files in our engine, each specifying the objective message and rule engine triggers. What we'd love to achieve is that we can tweak GoNorth into exporting straight into these JSON files. If we have a custom exporter which supports Kotlin (our preference), such as with the other features, we can likely get quite far already. We'll have to see if we can implement this export from start to finish, or we have GoNorth only roll out a skeleton and have manual work to do the final touches.

@steffendx
Copy link
Owner

Alright. Thanks for the insight. I will include support for this export feature in the next release.

@steffendx steffendx self-assigned this Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants