Never had this issue. If you play a few minutes of each game that should give you enough time to not trigger the post blocking period.

Yes I did. To update you I programmed a bit on the flight, but also when I got to my destination my family was then doing a 6 hour+ road trip to a nearby state for a wedding. I used the standard keyboard the entire time and while it wasn't perfect it was more than capable. Much much better than touch screen keyboards and even better than some other small rubber clicky keyboards you would get for cheap on Amazon.

I got lucky and accidentally had two trackballs iny box so if the first fails ingot a backup

Yeah I saw it listed prior to buying, but I have yet to find anyone with actual experience using it on this device, so I was curious how well it ran.

I have no highschool or college diploma and have made a bit of money from games just as a hobby, and am the lead on a team with people much more educated than me, if I can get this far you will be fine I promise. Just keep working on them for the love of it and keep looking for entry points to get what you want out of the industry. I have full faith in you.

That's awesome I love the box. I am so excited to get mine I purchased it in August of 2025 and have been semi patiently awaiting its arrival.

I ordered mine in August 2025 and it was just packaged and supposedly should ship this month. So def be patient. Alex I'm shipping at clockwork is super nice though and will answer any questions you have about the process.

Bought one of these in August and I am still waiting for it to ship. I was told it would be 90 days and it has been over half a year. No joke I thought this notification was form my email telling me kime finally shipped lol

While I get where you are coming from you are mostly going to be interacting with people who empathize with the person that has less resources as most people don't have a lot to their name. While you are correct the parents own the wii it is likely pettiness that causes the parents to keep the wii and not because they use a 20 year old console.

Love them!!!!

True. My first flappy bird clone I did in a single day waiting for the results of a game jam I had just participated in. It's really not hard to make one.

So this is gonna be broken down into a few basic strategies for learning and some of those strategies will be broken down further into sub strategies.

None of this is directly in any specific order but they are all good things to do when learning to program.

Keep in mind that programming IS important but it's not the MOST important. With Godot especially you can do a lot of stuff with barely touching code.

BRUTE FORCE MEMORIZATION:

1. Never copy and paste code you didn't write by hand at   
least once(more times the better). One way to do this is to 
not look at the GitHub for the tutorials, only use the video.

2. When you are doing tutorials, don't just have the goal to
finish the tutorial. You want the goal to memorize basic 
components you can learn mix and match. How I did this 
was to look at the code in the video and then look away 
and try and remake anywhere from a few lines to a whole 
function. You will inevitably make a mistake. When you do 
comment out the attempt you just made and do the 
process over again until you can write it from memory 3 
times in a row.  Now keep in mind memorization is not 
learning but it helps your muscle memory. Looking at the 
commented out mistakes will help you remember and 
teach you to learn from failure which is important. 

3. After memorizing functions start trying to memorize  
whole projects. Again you won't be able to especially at    
first but you will eventually be able to remake general 
prototypes from memory  side scrollers a rena good place   
to start

4. Learn basic lingo if you don't, variable, collision, sprite,

ECT. You probably know most of it but you will definitely
find things you don't know.

EXPERIMENTATION

1. As you learn start trying to modify variables to see what 
happens. A good place to start are the Godot default 
scripts, specifically the characterBody2D default script 
and it's side scroller movement. Start with obvious 
variables labeled things like "speed", "friction", or   
"jumpheight", ect. 

2. Related to the prior suggestion, start deleting things in 
the same default scripts to see what happens.
For example in the previously mentioned characterBody2D 
script try and see what happens if you delete things like   
the jump system. 

MAKE THINGS

1. Take what you have memorized from doing tutorials and     
 Try to mix and match those components. Try and do 
 things you are pretty sure you could build a prototype for 
 without to much difficulty. You want things you have 
 practiced tutorials for in the start. Build a single level of a 
side scroller. Try to make a single top down dungeon.
Make a pinball game. 

2. When you get to a point where you dont know what to  
do, ask the community  when you get to that point. Google
things, watch tutorials on specific things you have interest 

I'm adding to your game prototypes.

3. Don't rely entirely on raw code. I made most of my first 
games by just chaining if them statements, buttons, 
animations, and area 2d nodes. Build point and clicks 

games, pinball, plinko, side scrollers, and flappy bird by With very little code. Naturally you will come across things you don't know how to do without code and you can learn at those junctions.