Fix compile error, add assets and unified readme #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First take on an unified readme format used accross every O3DE samples (and checked that the project still runs correctly on the release of 23.10.3)
The goal being to make the samples more accessible to the users. Both by updating the project's readme, adding a version check and linking them in O3DE showcase and doc pages. Task tracked via this issue : o3de/o3de.org#2549
As kenney's assets are CC0 license, I think its best to include them directly in the repository to reduce the number of steps to be done to run the game. The same logic was applied concerning O3Tanks. I can still mention it in the readme if you prefer it this way.
I believe it is one of the best O3DE usage out there, you C++ scripting is well done and it should be a good guide for O3DE newcommers. Adding it in the "official" samples list and later on in the O3DE launcher would greatly improve the accesibility of the engine