General Thoughts

Today was pretty productive it feels like, even if I didn’t do many exciting things.

Godot Game

Things Done

  • Organized all game files. Player files with player files, level files with level files. The game feels much cleaner now.

  • Began setting up the text capturing for the game. I am using a LineEdit 2D to capture the node (even though it’s a 3D) game, and have simply placed it out of the viewport. I grab its focus everytime a keyboard input is pressed (I should validate this at some point…), even though come to think of it I’m not actually using it for anything now (I should remove this bit of code). Just while I get things working, I am reduced the objective to just having text you input compared to a Label3D. I wanted to make it so that when you got the letter correct, the letter changed color, but it turns out Label3D does not support text color changing. Which leaves me with two choices:

  • Somehow daisy-chain a bunch of Label3D’s together to form a word. I can think of lots of pros and cons here.

  • Use RichText, so I have access to the indiviual letter coloring. I think this would look bad, and require me to change some of the game design ideas I had.

I think I’m going to have to try to make the Label3D’s chain together to be a word. Should actually be sort of fun! I feel like a got a lot done, considering today was a workday. I am feeling pretty excited about working on this game, I’m happy to get back in the groove again. As for a little twist, as my AI obssession ever grows, I’ve decided that after every devlog, I’ll instruct an AI using a prompt I made to give me tips on what I should do next.

Today, I used Chat GPT 4. I will not alter any of the text, so don’t blame any typos of nonsensical advice on me!

Notes from AI

Based on the text provided, here are the next steps for the developer to take:

  1. Continue Text Capture Setup: Continue working on setting up the text capturing for the game. The developer mentioned using a LineEdit 2D to capture the node and placing it out of the viewport. While it has been set up, it is not being used for anything at the moment, so it should be either utilized or removed from the code.

  2. Validate Keyboard Input: The developer noted that they grab focus every time a keyboard input is pressed, but mentioned that they should validate this. The next step here would be to validate the keyboard input for the text capturing system.

  3. Experiment with Label3D: The developer mentioned the idea of daisy-chaining a bunch of Label3D’s together to form a word, as an alternative to using RichText. They should try to implement this and see how it works in the game.

  4. Coloring Individual Letters: The initial plan was to change the color of individual letters in a Label3D when they are entered correctly. Since this feature is not supported by Label3D, the developer could try using the daisy-chaining method mentioned in the previous step and update the colors of individual Label3D’s.

  5. Evaluate Game Design Changes: The developer mentioned that using RichText might require changes to some of the game design ideas they had. They should evaluate these changes and determine whether they are necessary or if there are alternative solutions.

  6. Continue Organization: The developer organized game files into separate categories (player files, level files, etc.). They should continue with this organization to make sure that the game development process remains organized and efficient.

  7. Maintain Enthusiasm: The developer mentioned feeling excited and happy about working on the game. They should continue with this enthusiasm and keep making progress, even if it’s on a workday or during their spare time.

Here’s a motivating quote for the developer to keep in mind:

“Success is not the key to happiness. Happiness is the key to success. If you love what you are doing, you will be successful.” - Albert Schweitzer