Defold Match 3 ideas

Hello all,

I am attempting to create a match 3 game in defold. I have built the editor pretty much and everything is GUI 100%. I am not sure that the game itself should be made using gui nodes, though I have the mechanics down already.

If you were to make a match 3 game, how would you handle the game pieces?

NOTE:

Currently, each board piece has 3 layers that each node can be transformed indepently. GO can to, but requires a collection for each prefab / GO.

None of that is an issue. What is the issue is maintaining the same scaled size for all screens. GUI is done without issue. GOs is where I have my concerns. Take for example ā€œemthreeā€ on github. Maximize the screen, game objects get elongated. I know, camera, right? I tried it and tested different screen sizes and the GOs would resize, but in some cases, outside of the screen.

Being an indie, I don’t want to waste too much time fighting the game and then have to make a major change. But on the other hand, isn’t GUI nodes more resource heavy?

1 Like

msg.post(ā€œ@render:ā€, ā€œuse_fixed_fit_projectionā€, { near = -1, far = 1 })

1 Like

Yes, thank you, and I think I may have gotten confused. I recall testing the grid using tilemaps and not GOs. Ugh!

I need more sleep.

hello I also remake match3 to learn defold developer(beginner)I am curiosity want to know why use gui to make match3(I also learn many method from enthree)

I used GUI only for the editor.

I will be using gameobjects for regular game play.

emthree is great and i will be customizing the engine to do all that I require..

My main concern was memory footprint. I suppose GUI would be heavier that a collection of 3 GOs with a sprite attached to each. No collisions.

1 Like