Why does packaging cooks and includes tutorial content?

Development Platform & Builds
, , , , , ,
1

I am using a fresh blank C++ project without any starter content and yet when I press package I see the following in the logs

UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Foliage/Foliage_Intro_Tutorial 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Foliage/Foliage_Using_The_Tool_Tutorial 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Foliage/Foliage_Settings_Tutorial 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Basics/LevelEditorAttract 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Mobile/SettingUpAndroidTutorial 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/ContentIntroCurve 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Paper2D/SpriteEditorTutorial 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Mobile/TutorialAssets/android_Icon 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Paper2D/TutorialAssets/Paper2DSprite_TutorialIcon 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/Foliage/TutorialAssets/Foliage 
UATHelper: Packaging (Android (ETC1)): Cook: LogCook: Display: Cooking /Engine/Tutorial/SubEditors/ParticleSystemEditorTutorial

Why are these things even being cooked in the first place? I never used them anywhere in the project.

Not only do they take a long time to cook but also increase the size of final packaged build significantly.

2

I love to know an answer to this too. It’s annoying as hell…

3

Asking the real question here.

4

I would also like to exclude that stuff (although it is really no a lot and hardly makes a difference in my case), and I found this, which at first glance looks like it would be a solution:

look for “Package Black List” almost at the bottom.

However I have not been able to get this to work, the blacklist text files are never applied.

If you get this to work for a Windows64 build (Shipping or Development), please let me know how.