Agree with this. Sounds like you want to prototype game designs more than code/utilize final implementations. The standard advice you'd get in game dev is to us

Agree with this. Sounds like you want to prototype game designs more than code/utilize final implementations. The standard advice you'd get in game dev is to use super low production value assets to prototype. People even often "paper prototype" or use other completely non-digital media. I agree with the sister comment to parent that suggested something like Game Maker. Those tools are simpler and more usable out the box than game engines. If you want the feeling of completing a simple game as you go, and seeing your (near-)final implementations of elements as you hammer them out -- that's fine as a learning exercise. It will probably be inefficient (as you may change you mind about things later on that you already spent a bunch of time implementing/polishing), but it can be a cool way to learn. However, for that, you may run into what some other comments are saying: you'll have to figure a lot of custom stuff out as you go. Edit: There's a good series[0] where a game critic / indie game dev makes 12 games in 12 months. He uses Game Maker Studio 2 and the episodes go back and forth between concept/design and execution. [0] https://www.escapistmagazine.com/v2/category/v2/yahtzees-dev-diary/ https://www.escapistmagazine.com/v2/category/v2/yahtzees-dev...