Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

It's a nice puzzle game. The code does show the idea of the game and how it could be implemented.

However, the way it's been coded (a different variable, cell and image for each tile) means it's not best practice or easily extended. To add more rows or cells means adding more events and objects for each new tile.

 I think this would be ideal as an example program if you'd consider a refactor using arrays and instance variables on the cells, tiles and possibly select object. It would reduce the project down to a dozen objects and a lot less code. 

After all, your game is simple in concept and events, yet fun to play. Great qualities for an example GDevelop game to learn from.

I tried something similar to what you suggest, but it turned out to be a bit more difficult task than I seem to have done in 2 days. I will probably try to perfect this concept over time to make it easier to upgrade with fewer copy-past repetitions.

Yeah, I understand that one. If you're not familiar with a new way of coding, it's not a great idea to try it with such a tight time constraint.

If you do go ahead with refactoring it to make it easier to upgrade and come across any issues, drop a post on the forum. I'd be happy to help with it (I go by MrMen on the forum).