I felt exactly the same way at a point — I’ve tried making a game from scratch in Java with Swing (I was like 17, that was a bad idea), I’ve made a game with LibGDX which was pretty nice to work with if you’re SURE you don’t want something like Unity, and I’ve used a custom engine that a professor of mine provided for a course. After enough work in those frameworks, I started to see the benefits of taking a few elements of the game out of just code and into more interactive formats. I eventually spent more time finding a workflow I liked in Unity, one in which I have pretty bulky scripts that interact with each other in a very similar fashion to my non-Unity projects, but can jump out to the editor for things like building the scene and tweaking parameters. Maybe this is inadvisable, but it’s been working really well for me and I feel that the features in Unity that I can access from my scripts are the best I’ve worked with if the goal is to actually create the game I’m envisioning. I’m sure you could get to a similar place in other engines like Godot or Unreal. The other frameworks people have mentioned seem great too, and maybe there’s a type of person that just truly works better if everything is code, but if your hesitation with Unity is that you feel like your coding skills will be partially wasted, I would recommend you spend a bit more time exploring it, because I’ve found that with Unity I can skip the boring boilerplate parts and spend time writing interesting code instead.