Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit) (+1)

Using non-game making frameworks for making games can be interesting, but it will throw up roadblocks that you don’t need (like your multiple sound issue). People who usually make a game in a non-game framework usually do it for those specific challenges, like remaking Doom in Excel.

IMO if you just want to make a game, I suggest using a made for purpose tool. Try Unreal (my tool of choice), Godot (really good open/free option), or Unity (if you must :P).

It’s usually easier to learn a new tool than fighting against a tool you’re familiar with, it will also open possibilities that you may not have thought of (just don’t go too far, feature creep is a beast).

Thank you! I like how Godot and Unity look. The problem is that as my game is mostly butons, fixed images or simple animations, and sounds, it can all be done with Maui and xaml. In Unity, Godot, and Unreal, maybe it's overkill to use them for this?

I mean, I don't have moving sprites or 3D, it's not needed to have a gamepad, or arcade features at all.

Do you think that in this particular case, it has sense to use them? Are those prepared for making a game that is mostly screens with UI and clickable parts?