#Release Build Assets

2 messages · Page 1 of 1 (latest)

chilly cloud
#

I have just created my first release build following the bevy_github_ci_template (https://github.com/bevyengine/bevy_github_ci_template)

I want to discuss protecting the assets created along with the release build.

Right now, the release template bundles your assets folder and an executable of your game. All your game assets are just sitting there, available to anyone who downloaded your game.

I am currently making a game to be a commercial product in the future. I am worried about the assets being stolen.

What is a good way to protect my assets, at least legally? Is there a license or read me I can include in the assets folder to notify end-users that those assets are copyrighted and not permitted for reuse?

GitHub

Contribute to bevyengine/bevy_github_ci_template development by creating an account on GitHub.

stone ridge
#

For a technological "solution", there are a couple plugins that may help out with this here:
https://bevyengine.org/assets/#asset-loading ranging from encryption to obfuscation to just tossing the assets into the executable untouched. (Be sure to check the license, there's an interesting one in there)

But that's just adding a hurdle. If your game executable has the means of decrypting the assets, then a motivated-enough person can do the same.

Possibly, adding that sort of barrier is useful legally. No idea.