Haha, this is super cool. What about a "randomize" button? Utilities like this could really use them.

On that slope discussion earlier, wouldn't it be simplest from a "collision checks on the fly" perspective for the map to 'know' its surface vectors, and have character movement plot along them? As in, in any of the examples earlier, the ground may be several dozen separate tiles with sepa...

A quick google search resulted in this and I can only assume you converted it to RGB values for your personal use - but whatever the case, the list is still hard to peruse, particularly for comparing different shades of the same color choice. I'm not very color-savvy in general, but what would it ta...

Well this is for my interface code -- as you might have guessed from the above snippets, the purpose is to test if a interface function is active (such as: the confirm button) when that function has multiple possible buttons to activate it (such as, spacebar or return). This is called once per updat...

Are you sure you need numbered indices? You can iterate over string indices: self.controls = { confirm = {keys = {"enter", " "},isDown = false,}, back ={keys = {"escape", "backspace"},isDown = false,}, } for index, value in pairs(self.controls) do -- index no...

So I want to be able to iterate through a table of tables (see code below) using #table, yet also access those same members using string indices -- assigning them with string indices doesn't seem to give them numbered indices. So the best I could come up with is as follows: function interface:load()...

both options can work. either "1 world per slice" or "everything in one world, and filter by slice". the former will probably be slightly more efficient, but also probably more difficult to work with. also, please use the following thread to talk about bump, this one is about a ...

I'm trying to think about how one would utilize multiple bump worlds to create background and foreground collision layers, and a player that can move between them. Would it be best to have a player hitbox in each layer and just control the one in the active layer, making the appropriate changes with...

Oh jeez. I love this game so much. This is like "megahard" platformers boiled down to hitboxes.

Hm. I wonder what the original purpose of the 0-255 was, then. Either way, my problem's been solved, and I've already begun to convert my RGB to HSL unilaterally across my game. Thanks again.