I’ve had some problems like the d-Pad UP and DOWN are in the wrong spots and WASD isn’t working on my keyboard no textures or sprites its AI some of the code is probably in spots it shouldn’t be. As a beginner debugging with Print() should be peoples first steps I would have never made something like this if I didn’t know about Print(),if for debugging. Tell the AI “Use Print() to find errors in the code” then copy and paste errors from terminal when you play code so the AI fix’s itself. I’d love any tips
I tried to make it use class’s to help make the code more edit friendly can’t let the AI do everything I had to fix the hud myself but it kept saying can’t find files so the AI end up using the main page making one page over 700 lines of code? Any tips I’d like to split the features like the map, player, sprit/animations and texture editor?
Just run this on my Mac and the directional buttons clash with the prompt for flipping to the editor - suggest reciting in the bottom left or bottom right.
Also on the directions the forward and backward buttons are not in the traditional positions, which keeps catching me out. Inverting them would be great but it’s just a matter of getting used to them.
Also - I’m a little puzzled about the walls - they seem to be made of multiple retables as you can see the lines between them. I’ll be looking at your code but you would expect large single rectangles to be more efficient and need less cpu time.
I’d put the fire button near the(or in centre of the direction buttons - as your game expands and you are involved in more interactions dragging over to the fire button would be much quicker.
Great post - will keep an eye on it, hope you are intending to expand it. I’d just add a few objects (treasures/weapons to start with) and expand your map.
I’ll do this before breaking the code into classes. I’m gonna try to make the code easy to edit as well so anyone can use it to make a game with the code maybe make a level designer. Ik Codea isn’t a strong 3d engine so I thought Fake 3D would run alot smoother on the software and if someone with real coding experience also pick up my idea they could probably make a really good Duke/DOOM engine so Codea has a big 3D boom. I’m not really good at coding I’m really just debugging. Thanks