![\"Minifurnace\"](\"\/data\/posts\/2014\/03\/e224b597df5f747f19e74e8a3213b9da.png\"\/)
<\/p>\n<\/p>\n
LINK to engine<\/a> Last MiniLD (#49) I used\u2026 the furnace engine!!! \u2026and it was great \u2013 it was the first time that I did not have to code and I could focus on the content entirely*. I managed to create a fairly complex and decent Minecraft-like adventure-y game.<\/p>\n Unfortunately, I also discovered the most annoying aspect of this sort of language \u2013 it\u2019s horrendous at defining sprites! Encoding images as letters is NOT a good idea (yes, I\u2019m looking at you, PuzzleScript); it requires enormous patience. So that\u2019s why I made a sprite sheet importer! What does it do? You just and drop your sprite sheet (an IMAGE made in an image-editing software), then you adjust the grid\/sprite slicer and BAM! \u2013 you get them encoded as text in furnace-engine-format. Exporting images to the PuzzleScript-format is on its way.<\/p>\n *Digressing: I find it a blessing to not care\/know about the underlying details of what you\u2019re working with: I can\u2019t see the pixels on my tablet \u2013 therefore images on it must be made out of magic! I also don\u2019t have access to its file system \u2013 therefore files, if they exist at all, must be stored in a magical way and I love that I don\u2019t know how! Same thing goes for Haskell \u2013 it\u2019s sooo high level you can never know what the machine you\u2019re running your program on is doing.<\/p>","time":"March 10th, 2014 11:50 pm","title":"Eat your own dog food","title_was_empty":false}