Reply to Re: YeOldeDink 0.9 Release: Valentine's Edition
If you don't have an account, just leave the password field blank.
By that I mean that all the various bugs introduced by me copying and pasting in your scripting abstractor have most likely been resolved to the point where it's invisible to the user unless otherwise specified, and under normal circumstances it should run as 0.8 did when it was just DinkC, except for a few debug log entries I should sort out.
>The "downside" of course being that it'll only work with your engine. ?
And of course your old source tree
. Although if you went really nuts you could double-up with *.c scripts.
I gotta admit though, after using DinkLua for a few minutes, I never want to go back to DinkC except for the most minor of operations. Having loops and proper vars really is a different world.
The source release should be pretty easy to compile compared to previously, although please do indicate if you get stuck or would like an AppImage of it.
>The "downside" of course being that it'll only work with your engine. ?
And of course your old source tree
. Although if you went really nuts you could double-up with *.c scripts.I gotta admit though, after using DinkLua for a few minutes, I never want to go back to DinkC except for the most minor of operations. Having loops and proper vars really is a different world.
The source release should be pretty easy to compile compared to previously, although please do indicate if you get stuck or would like an AppImage of it.
