I asked Chat GPT how to learn game engines...

Gamedev Dairy #86

TL;DR

1. Intro

2. ChatGPT on learning Godot

3. ChatGPT on learning Unreal Engine

4. Summary

5. Recommendations

Intro

I participated in some interesting presentations on the topic of ChatGPT recently. That and some other resources inspired me to check what ChatGPT has to say regarding learning a game engine. I’ll share the prompts I used, but I’m not a prompt engineer (yet), so I might still work for them to be more… valuable.

ChatGPT on learning Godot

So I tried this prompt:

You are an experienced indie game developer, and I am a wannabe. Give me directions for learning game development as a solo developer using Godot 4 game engine with a plan for 30-60-90 days.

And learned that I omitted important info, so…

Now modify what you wrote, taking into consideration that I already have some experience in C# and OOP and want to make games using C# (not GDScript)

And received the following response:

Certainly! If you already have experience in C# and object-oriented programming (OOP) and prefer to develop games using C# instead of GDScript in the Godot 4 game engine, here's an adjusted plan for your first 30-60-90 days:

First 30 days:

1. Get familiar with the Godot engine: Download and install Godot 4 and explore the interface and workflow. Focus on understanding how to use C# as the scripting language in Godot.

2. Learn Godot's C# API: Familiarize yourself with Godot's C# API documentation. Study how to use C# to interact with the engine's systems, including nodes, scenes, input, physics, and audio.

3. Translate existing knowledge: Leverage your previous experience in C# and OOP principles to understand how they apply to game development in the Godot engine. Study the differences and similarities between C# in Godot and other frameworks or engines you have worked with.

4. Create simple projects in C#: Start by developing small games or prototypes in C#. Focus on implementing basic mechanics, such as player movement, collision detection, and simple interactions. Use Godot's C# scripting capabilities to build these features.

Next 30 days (Days 31-60):

1. Deepen your C# knowledge: Dive deeper into C# game development concepts. Learn about advanced topics like coroutines, delegates, events, and serialization. Explore design patterns commonly used in game development, such as the component-based architecture or the state pattern.

2. Work on more complex projects: Challenge yourself by creating more sophisticated games that require multiple systems and interactions. Implement more intricate gameplay mechanics, UI elements, and audiovisual effects using C# scripting.

3. Explore C# frameworks and libraries: Investigate C# frameworks and libraries that can complement your game development process. Examples include MonoGame, Unity's Addressables system, or open-source libraries for specific functionalities like pathfinding or animation.

4. Connect with the Godot community: Engage with the Godot community, particularly those using C#. Participate in relevant forums, Discord channels, or social media groups. Share your projects, ask questions, and learn from other C# developers using Godot.

Final 30 days (Days 61-90):

1. Optimize and polish your games: Focus on optimizing the performance of your games. Implement techniques such as object pooling, efficient memory management, or asynchronous loading to enhance performance. Polish your games by refining the user interface, improving game feel, and adding visual/audio effects using C#.

2. Publish a C# game: Aim to complete and publish a C# game project during this period. It can be a small-scale game, but focus on delivering a polished and enjoyable experience. Publish your game on platforms such as itch.io or the Godot Showcase.

3. Continued learning and iteration: Reflect on your game projects, gather feedback, and identify areas for improvement. Iterate on your games or start new projects to further enhance your skills in C# game development. Explore additional game development concepts or frameworks to expand your knowledge.

4. Explore advanced topics: Once you feel comfortable with C# game development in Godot, consider exploring more advanced topics such as networking, procedural generation, AI, or integrating external libraries and APIs. These areas can provide new challenges and broaden your game development capabilities.

Remember to adapt this plan to your learning pace and preferences. Leveraging your existing C# and OOP knowledge will give you a head start in game development with Godot 4. Enjoy the journey, keep coding, and have fun creating your own games!

Not bad! I admire the fact that he it wants me to learn more C# 😉 But it’s funny that he it wants to make me learn theory, and after that, at point 4 he it wants me to create a simple game. Because this is the exact procrastination-oriented approach to learning I usually take 😂 I mean, sure, you have to learn. But it’s either not a big believer in tutorials, or it’s just prolonging the moment you sit down at the keyboard to write that game.

Not entirely sure what’s the point in learning MonoGame or Unity’s features, instead of deepening your knowledge in Godot?

One thing I actually liked about the advice is that only after making a simple game, and some more complex it advises to join a community. But still - before publishing the game… It also advises optimizing the performance before publishing it. Okay, I guess. But then again, wouldn’t it be better to just publish it? It’s your first (or almost first) game. It’s gonna suck anyway, right?

If you’re wondering what’s with the 30-60-90 days plan, then I got inspired by Jeff Su for that. I guess it works great for structuring a plan.

ChatGPT on learning Unreal Engine

Well, I had to refine the skill, right? Still have some Choo-Choo Charles success story hangover, so…

You are an experienced indie game developer, and I am a C# developer not programming games. Give me directions for learning game development as a solo developer using Unreal Engine 5 and making 2D games using BluePrint and Paper2D with a plan for 30-60-90 days.


Certainly! If you're a C# developer and interested in learning game development as a solo developer using Unreal Engine 5 to create 2D games using Blueprints and Paper2D, here's a suggested plan for your first 30-60-90 days:

First 30 days:

1. Get familiar with Unreal Engine 5: Download and install Unreal Engine 5, and spend time exploring the interface and basic workflows. Familiarize yourself with the key components of the engine, such as the editor, content browser, and blueprint system.

2. Learn the basics of Blueprints: Blueprints in Unreal Engine provide a visual scripting system. Study the fundamentals of Blueprints, including variables, events, functions, and basic flow control. Follow tutorials and documentation to create simple interactions and gameplay mechanics using Blueprints.

3. Understand Paper2D: Dive into the Paper2D system within Unreal Engine, which is specifically designed for 2D game development. Learn how to create and import 2D assets, set up sprite animations, and implement basic 2D physics and collision.

4. Start with small projects: Begin by creating small, simple 2D games or prototypes using Blueprints and Paper2D. Focus on implementing core mechanics such as player movement, object interaction, and basic enemy AI. Start with a single level or scene to keep your scope manageable.

Next 30 days (Days 31-60):

1. Expand your Blueprint knowledge: Dive deeper into Blueprint scripting. Explore more advanced topics like complex event graphs, custom functions, and blueprint interfaces. Learn how to create reusable Blueprints and modular systems to streamline your development process.

2. Experiment with Paper2D features: Explore the various features and tools within Paper2D. Practice creating more complex animations, implementing tilesets, and managing sprite sheets efficiently. Experiment with lighting and post-processing effects to enhance the visual quality of your 2D games.

3. Work on larger projects: Challenge yourself by working on slightly more complex 2D games. This could involve designing levels with multiple scenes, implementing progression systems, and refining gameplay mechanics. Break down larger projects into manageable tasks and iterate on your designs based on player feedback.

4. Join the Unreal community: Engage with the Unreal community through forums, Discord channels, and social media platforms. Seek feedback on your projects, ask questions, and learn from experienced developers. Participate in game jams or showcase your work in progress to receive valuable insights and networking opportunities.

Final 30 days (Days 61-90):

1. Optimize and polish your games: Focus on optimizing the performance of your 2D games. Explore techniques like sprite atlasing, level streaming, and efficient memory management to improve runtime performance. Polish your games by refining the user interface, improving game feel, and adding visual/audio effects.

2. Publish a 2D game: Aim to complete and publish a 2D game project during this period. It doesn't have to be a large-scale game, but focus on delivering a polished and enjoyable experience. Consider publishing on platforms like Steam, itch.io, or mobile app stores to reach a wider audience.

3. Continued learning and iteration: Reflect on your game projects, gather feedback, and identify areas for improvement. Continue learning and expanding your knowledge of Unreal Engine by exploring more advanced topics, such as AI, networking, or level design. Iterate on your games or start new projects to further enhance your skills.

4. Explore additional tools and frameworks: Consider exploring additional tools and frameworks that complement Unreal Engine. For example, you can explore external 2D art software like Aseprite or dedicated animation tools like Spine to enhance your visual assets and animations

And… it’s almost exactly the same. So I guess, not much to learn this time.

Summary

Nothing original, to be honest, but I blame it on my beginner skill in prompts. Perhaps, a different approach is needed. More detailed maybe? More technical, less coachy? Time will tell.

Recommendations

• No matter how meh it sounds when shortened to just the activity, hearing a guy talking about his passion and knowing his stuff is always fascinating.

See you next week ;-)

PS. Have you ever used Chat GPT for similar purposes? Know any interesting prompts I might use? Mail me ;-)