I’m touched that you feel so!
Hmm… Very odd indeed. That should work. And indeed, a quick test on my end by re-downloading the environment file and some of the textures indicates that it does–at least on my machine, and under Linux.
Actually, there’s a thought: I’m not sure that I’ve tried the “.blend” files under Windows. Perhaps Blender doesn’t convert file-paths for its current operating system.
If so, try the following:
- Select an object and go to one of its texture-entries, as described above.
- Now scroll down to the text-entry that’s labelled “Source”.
- You should see a file-path along the lines of “//tex/<file-name>.png”–e.g. “//tex/bricks.png”. In this file-path, remove the first two forward-slashes, and replace any others with back-slashes.
- So “//tex/bricks.png” would become “tex\bricks.png”.
Does that fix the appearance of that one texture?
This brings me to my next point: while exporting the models via YABEE might be useful as practice, it shouldn’t be required in order to follow the tutorial–the asset-repository should include “.egg” versions of the files as well as the “.blend” versions.
So, turning to what you see when you import your “.egg” file, what happens if you replace your exported version with the version from the repository?
 Another thought: When you exported the model from Blender, did you select all of the part of the model? The various elements–walls, sand, etc.–are separate objects, so in order to export them all together, they should all be selected when performing the export.