Gergely "Bane of the Crawlers" Nagy<p>In other <a href="https://come-from.mad-scientist.club/tags/iocaine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iocaine</span></a> news, I'm doing some final polishing on <a href="https://come-from.mad-scientist.club/tags/lua" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lua</span></a> scripting support, to make it as convenient as <a href="https://come-from.mad-scientist.club/tags/roto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Roto</span></a>.</p><p>Right now, there's a differenc between how Lua and Roto scripts are loaded: with Roto, one needs to give a path to a directory, and <code>pkg.roto</code> will be loaded from there, and any <code>import</code>s will be relative to that directory.</p><p>With Lua, one gives iocaine a <em>file</em> path, and - currently - needs to set up the <code>package.path</code> search path manually.</p><p>So here's what I'll do: I'll make iocaine require a directory for Lua too, and it will add it to <code>package.path</code>, and will <code>require("main")</code>. The required module will also have to return a table with at least a <code>decide</code> key, and an optional <code>run_tests</code> key. This will simplify finding the functions to run, and will greatly reduce the number of special cases.</p>