Workprint – December 2018

Time for another workprint and I’m afraid this one is pretty much going to be a case of me saying “watch this space” in various different ways because, whilst there are things ongoing for amongst other things the CSDb Intro Creation Competition, I’m keeping the entire deck of cards close to my chest for the moment to allow for random rewrites or complete changes of project priority. There are at least two more intros being prodded at right now and one uses an FLD routine, but that’s about as specific as I’m willing to get for the moment.

But one of the sillier ideas I came up with a few weeks back but ultimately decided not to pursue – one of the down sides to the CSDb ICC is that you can only enter three intros, I usually have twice as many ideas – was by total coincidence realised by ROLE a few days back, although my version was going to be a bit more involved technically, pushing into the side borders and stretching the sprite. Perhaps I’ll do my interpretation and release it alongside the competition if I can find some free time?

There’s going to be a couple of releases on t’other label now that December is under way; it’s game code that’s been loitering around my hard disks for an age that was essentially put aside but not quite forgotten entirely when I switched to “demo mode”. You could consider those to be a “festive season bonus” but, since I dislike said annual event with a passion and am nowhere near organised enough to arrange something like that anyway, it’s really just me “clearing the decks.

4 thoughts on “Workprint – December 2018

  1. I’m envious! I have some spare GFX and music, just wish I had some code skills to knock something up myself… 🙁

  2. OK…
    Already have Crimson Editor installed, have downloaded ACME and grabbed some of your code from Git.
    Have some simple code examples to share?

  3. I’ve got ridiculous amouts of simple examples, prototypes and so on, bung me an email and we’ll talk about it further. =-)

Leave a Reply

Your email address will not be published. Required fields are marked *