UE to Godot

[Kjølig Bris]

Hello, I've recently moved from UE5 to Godot due to UE having very limited 2D tools. I've been using UE for about 7 years, and due to that I've only ever used Visual coding with blueprints. Kinda a bummer but with the limitations I've decided to end it 2D development in UE as I can't see it working out too well.

I've heard Godot is great for 2D, and I'm wanting to start work on a farming Sim. But coding via text is quite daunting and I'm not exactly sure where to start or how to learn. Even the formatting of it is confusing to me.

Appreciate all your help!

[umop-apisdn]

https://docs.godotengine.org/en/stable/getting_started/step_by_step/index.html

[Thomastronaut]

This app can teach you how to code in gdscript (godot's native scripting language)
https://www.gdquest.com/news/2022/12/learn-gdscript-app/

[jagholin]

There are plugins that allow you to do visual scripting in Godot, like https://github.com/CraterCrash/godot-orchestrator?tab=readme-ov-file , but I haven't used them.

[Zarathustra]

Originally posted by Blip:

Hello, I've recently moved from UE5 to Godot due to UE having very limited 2D tools.

Just use the plugin PaperZD instead of moving to Godot after using Unreal Engine ... 7 years. Otherwise it would a horrible time investement

[Zarathustra]

https://www.youtube.com/watch?v=S2olUc9zcB8&ab_channel=UnrealEngine
14:32 - ...
Explanaition for you

Also check out my curator page. There are 2D games made with Unreal Engine
https://store.steampowered.com/curator/42811258-Made-with-Unreal-Engine/

[Kjølig Bris]

Originally posted by Zarathustra:

https://www.youtube.com/watch?v=S2olUc9zcB8&ab_channel=UnrealEngine
14:32 - ...
Explanaition for you

Also check out my curator page. There are 2D games made with Unreal Engine
https://store.steampowered.com/curator/42811258-Made-with-Unreal-Engine/

I'll give it another go then, I'm having trouble more with the landscape in a topdown view. But cheers, honestly interesting video in general.

[umop-apisdn]

Originally posted by Zarathustra:

Just use the plugin PaperZD instead of moving to Godot after using Unreal Engine ... 7 years. Otherwise it would a horrible time investement

Many of the things one might learn from working with UE will translate just fine into other IDEs, and even other fields. Maya knowledge is still useful when one switches to Blender, and knowing how to sling C++ doesn't mean you can't learn Python. I started with TI-BASIC in 1986, and here we are nearly 40 years later... I can sling code in pretty much anything you can give me a syntax and function reference for (and if I'm being honest, I keep the appropriate "cheat sheets" close to hand for nearly every project).

A lot of us "greybeard" coders have forgotten more "languages" than newbie coders will ever know... especially if the newbie learns one thing and then quits. It's more about learning to think than learning specific thoughts; knowing a specific language is less important than understanding the whys and wherefores.

In the end, even the "puzzle pieces" of any engine's visual scripting aren't that different from text-based scripting; it's simply a matter of being able to see the "shape" of the thing you want to do, rather than which particular shape the "words" will need to take (for more information, see "Plato"). In other words, it all boils down to "I need to do X... how does this particular language/engine want me to tell it to do that?"

TL;DR: Learning is almost never a horrible time investment.

[Femboy Stein]

Originally posted by umop-apisdn:

Originally posted by Zarathustra:

Just use the plugin PaperZD instead of moving to Godot after using Unreal Engine ... 7 years. Otherwise it would a horrible time investement

Many of the things one might learn from working with UE will translate just fine into other IDEs, and even other fields. Maya knowledge is still useful when one switches to Blender, and knowing how to sling C++ doesn't mean you can't learn Python. I started with TI-BASIC in 1986, and here we are nearly 40 years later... I can sling code in pretty much anything you can give me a syntax and function reference for (and if I'm being honest, I keep the appropriate "cheat sheets" close to hand for nearly every project).

A lot of us "greybeard" coders have forgotten more "languages" than newbie coders will ever know... especially if the newbie learns one thing and then quits. It's more about learning to think than learning specific thoughts; knowing a specific language is less important than understanding the whys and wherefores.

In the end, even the "puzzle pieces" of any engine's visual scripting aren't that different from text-based scripting; it's simply a matter of being able to see the "shape" of the thing you want to do, rather than which particular shape the "words" will need to take (for more information, see "Plato"). In other words, it all boils down to "I need to do X... how does this particular language/engine want me to tell it to do that?"

TL;DR: Learning is almost never a horrible time investment.

Bit off topic but wow, great to hear you have a lot of experience. I have tried to learn coding for a few years now but failed every time, though now I am the furthest I have ever been because of Godot being so user friendly and intuitive. I started about 4 days ago and thats the longest I've ever stuck with it lol, but I feel inspired to keep going on. (Thanks to people like you and other factors reminding me of what can be achieved)

[Ridden]

I am familiar with other tools that use block coding and have heared about current development for Godot 4.x. The Link is just an example, it is adviseable to use my reference as a guide. It's purpose, merely to give a hint to a topic which could lead to a solution for your (our) problems.

Dropping this link here: https://www.endlessos.org/post/block-coding-for-godot-lowering-the-bar-of-entry-for-a-powerful-tool