Skip to content

Conversation

@Repiteo
Copy link
Contributor

@Repiteo Repiteo commented Nov 4, 2025

No description provided.

@Repiteo Repiteo added topic:releases Issues and PRs related to new engine releases topic:blog New blogposts and corrections labels Nov 4, 2025

<div markdown=1 class="card card-info" style="margin-top: 1em;">
We still love our original theme, henceforth known as the "Classic Theme," and will continue to support it in tandem. It can be accessed through the `interface/theme/style` and `interface/theme/preset` settings.
</div>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realise this blog post PR is probably not the best place to say this, but I'm not sure "Classic Theme" and "Modern Theme" are the best names. What will a theme in 5 years time be called - the Really Modern Theme? It's a bit like the New Nintendo 3DS - it's only New for a while and then you've painted yourself into a corner.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was hinted before that "Modern theme" is not a good name. We should probably discuss this properly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Classic Theme" is fine imo, but I can absolutely see "Modern Theme" changing in the later snapshots. It's certainly out of the scope of this blog post

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like "Modern Theme" for the rest of 4.x releases and "Default Theme" in 5.x and above?


<div markdown=1 class="card card-info" style="margin-top: 1em;">
We still love our original theme, henceforth known as the "Classic Theme," and will continue to support it in tandem. It can be accessed through the `interface/theme/style` and `interface/theme/preset` settings.
</div>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was hinted before that "Modern theme" is not a good name. We should probably discuss this properly.


There are too many exciting changes to list them all here, but here's a curated selection:

- Animation: Remove default skeleton path in `MeshInstance3D` ([GH-112267](https://github.com/godotengine/godot/pull/112267)).*
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a proper way to do footnotes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there is, I don't know how 🤷

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this I usually put a second level bullet point:

  • Animation: Remove default skeleton path in MeshInstance3D (GH-112267).
    • If relying on the default skeleton_path in some scenes, users should manually re-specify the parent node as the NodePath, or they can enable the animation/compatibility/default_parent_skeleton_in_mesh_instance_3d project setting to restore the pre-4.6 behavior.

This keeps the information close to where it's relevant, and is still visually distinct from the rest of the list.

This would also prevent this bug with the current card (which looks nice otherwise):

image

@YeldhamDev
Copy link
Member

If it's not asking much, could the article tell where the project being used to exhibit the new theme comes from? It's this one: https://codeberg.org/Librerama/librerama

@Repiteo Repiteo merged commit 79b4677 into godotengine:master Nov 4, 2025
1 check passed
@Repiteo Repiteo deleted the 4.6-dev3 branch November 4, 2025 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic:blog New blogposts and corrections topic:releases Issues and PRs related to new engine releases

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants