douira / island-tiles Goto Github PK

When the really small tile mode is active, it seems the tiles horizontally overlap a little bit although they have plenty of space.

List possible things below controls. Vertical is different objects, horizontally is different subtypes or terrain types. Or group all together in one auto–broken line and group subtypes with rounded borders. Get subtype data from level type abbrev map. (Then also add terrain item) also make level list, export function for created level and option to add them to the list of levels.

Maybe an extension to the level editor #1. An algorithm to check for solvability. Simulation capability requires the level to be able to copy itself and animations to be completed immediately and visuals to be ignored altogether.

After finishing a level I can only proceed with the next one if I'm in debug mode. In normal mode neither clicking next nor hitting Enter works.

I started making some floor tile pixel art. They can be found in "tiles-new" and there is a simple switch that can be made in the displayable code to enable the new tiles as the primary tile source. The theme is space/scifi but I haven't had time (and the skills actually) to make a full set of tile art. There are 132 tiles in the game of which I've drawn 21 floor tiles. There are also 4 additional new tiles that I made but are optional and not present in the old tileset.

If images are only available other tile sets then tiles they won't be preloaded. Preloading from other tile sets would involve using an error handler like in getImgElem of Displayable.

I've been trying this level for days now, but couldn't find a solution. I'm wondering if there is any solution or if there is a bug which makes it unsolvable.

The "Next" button is clickable in debug mode on last level and produces error when clicked in the last level. The "Previous" button throws an error when clicked after "Next" button threw and error.

After a tablet object is deactivated (meaning its number is hidden again) after another tablet is moved that is not the next one, it can't be moved. This probably happens because the movement inactivation that is applied to visible tablets is not deactivated by the tablet that is pushed out of order that deactivates all tablets.