Tracker: Port the app to Godot 4

[NathanLovato]

This issue tracks the work in progress remake of Learn GDScript in Godot 4. It lists issues as they were found by testers.

[AcTePuKc]

I'm doing it - and will add Bulgarian i18n/bg in the Language Repo as well - when I'm done > Expected time > After 01.01.26 :)
Oh shoot saw you're already doing it as well ... and reformating the lessons, ok will scrap my idea and will wait for you

[NathanLovato]

I'm not actively in the process of porting to Godot 4 just so you know, this is an issue opened for much later. What I'm doing now is working toward making maintenance and edits easier, refactoring, but otherwise keeping the app under Godot 3.

A Godot 4 port is something I'd like to get to, for all the improvements outlined above, but it'll need care and extensive testing before publishing so it's not something I was planning to work on for several more months at least.

Thanks for looking into it. If you get to work on this, don't hesitate to open a PR early if you'd like to collab. There'll likely be many snags/issues that pop up along the way.

As for translating to Bulgarian, thanks also for considering helping. If you haven't seen it already, here's the repository where we build the source translations: https://github.com/GDQuest/learn-gdscript-translations/

It has the most up to date source translation templates. The files in this repository are only the published languages. Let me know if you have questions or need anything!

[AcTePuKc]

Thanks for clarifying — makes total sense to keep it on Godot 3 for now and focus on refactors/maintainability first.

I think I’ll be done earlier than I expected, but I still need to test things properly. If all goes well, I’ll push a cleaned-up branch in the next few days — I just need to clean up some temporary test strings I used while verifying things.

Also noted on translations: I only noticed a bit late that the source templates live in the separate repo, so I’ll treat learn-gdscript-translations as the source of truth going forward.

Once I have something reviewable, I’ll open PR so it’s easy to iterate together - if needed.

[AcTePuKc]

Quick update: I have a Godot 4 migration pass in my fork now (scripts + project.godot, plus selected .tscn/.tres updates where needed). I also removed obsolete Godot 3 Tween nodes where I found them.

Current state:

• The port is close, but it still hits a couple of errors and warnings on startup.
• Some warnings are structural (e.g. WindowDialog, ScrollContainer) and likely need UI/layout decisions rather than mechanical fixes.
• I didn’t open every scene, so there may still be leftover Tween-related data in some .tscn files.
• Some comments may have been removed or adjusted during the migration and may need review or restoration.

Question before I open the PR: which target branch would you prefer for the Godot 4 work? I can open the PR against whichever branch you want (or against main as a WIP PR and retarget later).

If you’d like, I can also split it into smaller PRs (e.g. “scripts + project.godot” first, then scenes/resources fixes).

WindowDialog → Godot 4 MissingNode workaround

When a scene root is a WindowDialog, Godot 4 loads it as a MissingNode. Instead of rebuilding the whole hierarchy, this worked reliably:

1. Create a new Godot 4 dialog/window node (Window / AcceptDialog) under the old WindowDialog.
2. Cut the existing content subtree and paste it under the new node (preserves the subtree structure/properties).
3. Delete the old WindowDialog (now empty).

This avoids manually recreating nodes, but window sizing/layout may still need adjustment due to Godot 4’s different sizing/container behavior.

[NathanLovato]

Thank you very much for your help!

No need to bother splitting it into smaller pull requests for a port like this. The entire port itself is the right scope/unit of change for review and testing. It's going to involve more testing and iteration generally speaking than review of files' data/content.

You can target this branch for now: https://github.com/GDQuest/learn-gdscript/tree/godot4

It's a copy of the main branch. It will allow merging into the repository sooner and publishing a testing copy at some point.

I'll be doing at least one stable content update with Godot 3 (possibly several) before shifting the repository to Godot 4. For now the main branch remains the source of truth for releases or release candidates.

Besides UI node changes, the Godot 4 version is likely to have subtle bugs or regressions due to the engine being different, html5 support being different, etc. and it could take substantially more work as a result before making it the main released version. We'll have to see.

Using the new window, dialog, and popup classes sounds great for replacing the old window dialogs!

[AcTePuKc]

PR opened against the godot4 branch. Thanks for the guidance — happy to iterate from there.

I’ll keep working on the Bulgarian translation separately. I noticed there’s a leftover reference in res://autoload/TranslationManager.gd, but no Bulgarian files are included in this repo, as discussed earlier. 😄