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

Updates for ink version 0.6.1 #33

Closed
joethephish opened this issue Oct 11, 2016 · 5 comments
Closed

Updates for ink version 0.6.1 #33

joethephish opened this issue Oct 11, 2016 · 5 comments

Comments

@joethephish
Copy link
Contributor

See: https://github.com/inkle/ink/releases/tag/0.6.1

Apologies, there are a few more runtime changes this time! Mostly refactoring.

I realise I still haven't release a version of Inky with 0.6.0 and tags included, unfortunately I got caught up in these improvements! I thought I may as well hold off until these fixes are in.

@y-lohse
Copy link
Owner

y-lohse commented Oct 11, 2016

Ok cool, I'll probably have this done tomorrow night or by the end of the week :-)

@erkyrath
Copy link

I see this change bumped inkVersionMinimumCompatible to 15. Is the json format still changing that fast?

(Dragging @joethephish into this...)

@joethephish
Copy link
Contributor Author

Yeah, we still consider ourselves at alpha, I guess meaning that features/functionality/compatibility is still subject to change. All the while we're still in the early-ish stages of development on our current game, that is likely to continue.

Having said that, any change I make to the runtime format right now is only because we absolutely have to. I'm doing my best to find compiler side implementations of features wherever possible.

It's perhaps a particularly active phase right now as @joningold works out exactly what constructs will allow him to write most efficiently and effectively. Hopefully it'll settle down a bit soonish!

@joethephish
Copy link
Contributor Author

Also I should say, unfortunately having a stable format spec is unlikely to ever be a top priority for us :-/ we're always going to prioritise whatever's important to whatever game we're currently working on. I realise that's probably in stark contrast to other well established IF tools out there!

@erkyrath
Copy link

I realize that shipping playable, archivable ink.json files is way down your list of expected use cases. (I was hoping we'd see a couple in this year's IFComp, but that didn't happen.)

At some point I'll want to retool Lectrote to include several versions of inkjs and fire up whichever one fits the current game file. But, okay, problem for another day.

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

3 participants