Ancestors

Toot

Written by afreytes 🇵🇷 :godot: ☭ on 2025-01-18 at 23:58

I know there's more important things. But this change, man, OCD is getting the best of me here because I can't get over it.

The worst thing is that I'm thinking of pausing monthly support because it's hard to support something that does not bring joy. And since the change is aimed at large projects/big teams then surely they really don't need my support, right?

I admit I'm having a weird hang up and I'm trying to process it/think about it more objectively.

=> More informations about this toot | More toots from afreytes@mastodon.gamedev.place

Descendants

Written by dbat :godot: on 2025-01-19 at 07:32

@afreytes Keep your hope up. Here's a quote from the article*:

"For the time being we prefer to focus on the problem at hand (the need of UIDs for better refactoring possibility) and not future-proof things. If we ever change our mind, it would be easy enough to migrate information from .uid files to whichever new container we decide to use."

I read it as they are not 100% happy with uid files either.

• https://godotengine.org/article/uid-changes-coming-to-godot-4-4/#why-not-use-replace-import-files-with-meta-files-and-use-them-for-all-resources-that-have-an-uid

=> More informations about this toot | More toots from dbat@mastodon.gamedev.place

Written by afreytes 🇵🇷 :godot: ☭ on 2025-01-19 at 14:46

@dbat Thanks for your concern. I had read that. And about having meta files instead. And about making the editor automagically handle all that in the background so that paths are displayed where uids go and then switch back when the file is saved and...

Yeah ... I still feel unsure about it.

The only thing I know for sure is that my project is now littered with magic files that shouldn't be touched or touched in a special way. And it makes my workflow brittle, not better.

=> More informations about this toot | More toots from afreytes@mastodon.gamedev.place