Cocos Creator supports exporting scenes and prefabs in the current project for use in another project:
1, select the scene or prefab to be exported;
2, select the target to export to Folder location and possible renaming;
3, export a compressed file .zip.
4, decompress the compressed file .zip, and then drag the content to the designated location of the target project for use.
But there are also some small problems:
1, the various resources in the target project have generally been planned with names and levels, and it is likely that they need to be divided into categories when dragging them. Drag each resource file (including script file) to the new corresponding folder location;
2, according to needs, it is possible to rename necessary-this is a bit troublesome, may cause some resource references in the system The naming is wrong.
[Special Reminder] When using Creator, please rename it carefully. Once you are sure, try not to change it again.
3. Naturally, after importing, the corresponding reference of the node to the script must be re-referenced.
The above situation, I feel that there is no good way to simplify (so as to avoid modification as much as possible, and easily export to the current project), this is a componentized component design of Cocos Creator Decided. The small face is just a preliminary summary, and we will continue to discuss other operating techniques to simplify the reuse after export-this is a problem that must be faced in project development!