bevy_game_template VS bevy-kajiya-playground

Thanks also to bevy_game_template, without which Foxtrot would not be possible in the first place :) And thanks to /u/PhaestusFox, who made a video about the template

Seems like you are right - it really is a build.rs problem. I'm using the build.rs from this template, which only sets the icon, and when I remove it it really know not to rebuild when I touch a non-source file, but apparently even if I replace it with a build.rs that only containers an empty main function it still rebuilds when I touch the assets.

Should starting from bevy_game_template and not adding any weird dependencies be enough to ensure that?

From my own experience, I've walked through the Bevy tutorial a few times without getting a ton of traction. On this iteration I'm working harder to explore the examples, of which there are many. I'm playing with this bevy game template to learn more about how a full project might be implemented. I'm learning to approach gamedev with ECS entities as a first-class citizen, which is a concept I haven't really explored before.

Have you seen NiklasEi's template? It's more focused on the assorted project setup (like CI), but it may help you still <3

What do you think of the Kajiya renderer from Embark Studios. Is there a desire from the core developers to improve the plugin and maybe use as a default renderer?