Great with a small example that reproduces the bug
One thing I noticed is the path in game.project is /main/localization.json and the call to load_resource tried to load a file at path /main/resources/localization.json. Unfortunately changing the path still produces the same result.
I am able to load the custom resource if the prefix ‘/’ is removed from the path in game.project. E.g. replace
custom_resources = /main/localization.json
with
custom_resources = main/localization.json
and the resource seems to load fine. Be sure to do a rebuild & launch after modifying game.project. Hopefully this will resolve your issue as well.
The latest release contained two big new features LiveUpdate and Native Extensions. Both features have touched the resource system so this might be a regression that was missed.
I have investigated it a bit further this morning, and it seems that we previously supported both /a/b.json and a/b.json as paths for custom_resources. With the release of 1.2.97 it looks like we accidentally broke the “absolute” version of specifying custom resources in the game.project file. I have created a ticket for this and I’m working on a fix for it: DEF-2513
Sorry about this, and thanks for reporting! (In the meantime, as a workaround, you can still specify custom resources without a leading slash.)