To add to this, I work alone on my game currently, but often on two different machines.
I upgraded to Godot 4.4, did the auto convert thing for the new UIDs, pushed that change to git, pulled on my other machine, and I've had no issues.
fum
joined 4 months ago
There was a big change regarding UIDs in Godot 4.4.
You should have seen a warning popup about this when you first updated your project to 4.4. You would have been given the option to convert all files to the new UID format.
As far as I understand, this should have been done by one developer as the only change. An "upgrade to Godot 4.4" commit if you will. Then all other devs should have pulled that, then continued work.
Ideally this would be done on a branch to test the effect on the project. Engine updates should never be taken lightly during a project. This applies to any game engine.
I thought the whole point of the new UID feature is 4.4 was to help with git workflows?
This is my eternal struggle, with any type of biscuit.
I try to not eat the whole pack in one day, so eat some then close the pack. But inevitability I go back later and finish the rest!
According to the video it's MIT licence, and they discuss the risk of such a licence vs coreutils usage of the GPL
Tea bag first, then freshly boiled hot water.
Yeah that was the thing that alerted me.
I believe this would require agreement from all contributors, or for them to sign some kind of contributor licence agreement.
Interesting excerpt from Steamworks docs:
Which Open Source licenses are compatible with the Steamworks SDK?
In general, permissive licenses that do not put any requirements on you to redistribute your modifications under an open source license work fine. Common permissive and acceptable licenses includes MIT License, BSD 3-clause and 4-clause, Apache 2.0 and WTFPL.
Which Open Source Licenses are problematic for shipping on Steam?
Generally, any license that has a so-called “copyleft” element will be problematic when combining code with the Steamworks SDK. The best-known example is GPL.
But I saw a GPL-licensed application on Steam!
This can happen if the author of the code that is GPL-licensed has given the permission to do so. The author can of course always (a) decide to grant Valve a different license than the author grants everyone else or (b) decide that what the Steamworks SDK does is just a communication with a service that does not invoke the copyleft requirement of the GPL.
Sounds like (b) above could apply to you?
view more: next ›
Perfect