MyComponent 3.1 Sub packages not installed/moved

I tried to use MyComponent 3.1 and add a sub-package to my fresh build.
I followed the guide here: http://bobsguides.com/mycomponent-tutorial.html

What I did:

• Created a MODX DEV Cloud
• Installed MyComponent 3.1 via package manager
• Cleared cache
• Opened MyComponent in the front-end
• Created a new Project called 'flexibility4'
• Downloaded the flexibility4.config.php file via SSH
• Changed the top settings
• Uploaded the flexibility4.config.php file via SSH
• Cleared cache
• Created folders like: assets/components/flexibility4/_build/subpackages/
• Uploaded the 'ace-1.4.0-pl.transport' zip file to assets/components/flexibility4/_build/subpackages/
• Cleared cache
• Ran 'Bootstrap' in MyComponent
• Ran 'ExportObjects' in MyComponent
• Ran 'Build' in MyComponent

The result is a nice package with all default settings, but no sub package... What am I doing wrong?

(this is a copy of the issue here: https://github.com/BobRay/MyComponent/issues/17 [ed. note: ThaClown last edited this post 13 years, 2 months ago.]

I gave Menno this answer (and modified the Mycompopnent docs), but for others who find this:

First, the subpackages go in assets/mycomponents/yourcomponent/_build/subpackages, not assets/components ...

Second, for safety, MyComponent won't overwrite an existing project's build.transport.php file because the user might have made important mods there. If a new version makes changes to that file (like 3.1's new subpackage code) you need to update it manually. If you haven't made any mods to it, you can simply delete it and run Bootstrap (or copy the file from the core/components/mycomponent/elements/chunks/ directory).

If you have modified it, you'll have to either merge the new code into your existing file, or vice versa.

Any new projects will get the new build.transport.php file automatically, so this only applies to existing ones (in this case, only to existing projects with subpackages).

Sorry for any confusion.