You can find it on your Updates page. The new builds should be up on Humble soon too (check the version numbers on the files).
This is a quick bug-fixing update. Due to a rogue dev-debug-mode flag being mistakenly switched on in 0.1.2, much of the standard Lua library was accessible. So if you've started using PICO-8 recently, not knowing the library is not supposed to be there and tried to use it, sorry about the confusion!
v0.1.3 Changes:
Added: paste into commandline
Fixed: lua standard libraries accessible
Fixed: command-line loading doesn't work
Fixed: music pattern finished too early when all tracks set to looping
Fixed: peek()ing odd bytes in sfx address space masks bit 7
Fixed: cstore and reload from code space should have no effect
I made my own tostring (quite simple) and have removed the type calls. So BLD is now full compliant with pico 0.1.3 (and CC BY-NC-SA too). I'm near the final release : have to add levels and may be make my butterfly explode.
function str(n)
return ""..n
end
I like the polymorphic functions so adding type() is a good point for me.
Thanks for the good work :)
any thoughts on adding setmetatable?
obviously an advanced thing, but adds a lot of power to lua that's hard to do otherwise since it lets you implement different types of containers and do operator overloading.
certainly not something everyone needs to use, but i think as people grow with pico8 and lua it'd be a great addition.
Yeah, you can do ""..n for tostring and flr(n) for tonumber, but there's no way to do type() in the current API, which makes mixed type arrays impossible..
And I love metatables, but I'm slowly learning to do without them since Pico-8's tokenizing is super harsh whenever any weird symbols are involved...
Aargh, type() and getmetatable('') no longer work? I think I'll stick with 0.1.2 and hope this stuff gets added back into 0.1.4.
getmetatable('').__index = function(str,i) return sub(str,i,i) end |
I wrote this code to reduce tokens and add string indexing (string[1] == sub(string,1,1)). I also used the type of table entry to determine cutscene actions for cheap 2-5 token entries. MGN is basically maxing out the token space without these optimizations, but if you guys have suggestions I'm all ears.
[Please log in to post a comment]