Can u support the engine 'Cocos Creator'

[ahhhyp]

Cocos Creator Web-mobile build doc

[peter-hutsul]

Will check.
Can you make and provide a quick build from Cocos ? I want to see the build folders structure, files, organization.
Also maybe there are pre-built versions, and not the production one, so something can be done here ?

But in overall the chance is very low - because it's 2 so competing tools.
You can still use https://github.com/smoudjs/playable-sdk. But for infrastructure - seem like should be done with a separate package, something like Cocos Creator plugin.

[ahhhyp]

If build with wasm, engine source code will from cc.js to _virtual_cc-xxxx.js file. Resource file, like .fbxwill
compiler to .bin file, .png to .png ,and all use their uuid to rename

Folder structure tree like:

├── application.js                     # Main application entry point
├── index.html                         # HTML entry file for web deployment
├── index.js                          # JavaScript entry point and initialization
├── style.css                         # Global CSS styles for the web application
│
├── assets/                               # Game assets and resources directory
│   ├── Bundle_FBX/                # FBX model bundle containing 3D models and animations
│   ├── internal/                     # Internal engine assets and system resources
│   └── main/                         # Main game assets bundle (textures, models, configs)
│
├── cocos-js/                                  # Cocos Creator engine runtime and modules
│   ├── _virtual_cc-Bf4I9aK_.js       # Virtual module mapping for Cocos Creator
│   ├── cc.js                                 # Core Cocos Creator engine runtime
│   ├── bullet.release.asm-DxRECbrD.js # Bullet physics engine ASM.js fallback version
│   ├── bullet.release.wasm-DFFTnNvB.js # Bullet physics WASM loader and interface
│   ├── bullet.release.wasm-mT4aJDLq.js # Alternative Bullet physics WASM implementation
│   └── assets/
│       └── bullet.release.wasm-BIzkn7bF.wasm # Bullet physics engine WebAssembly binary
│
└── src/                              # Source code and compiled bundles
    ├── chunks/
    │   └── bundle.js                 # Main application code bundle
    ├── effect.bin                    # Compiled shader effects binary
    ├── import-map.json               # ES modules import mapping configuration
    ├── polyfills.bundle.js           # Browser compatibility polyfills
    ├── settings.json                 # Game and engine configuration settings
    └── system.bundle.js              # System-level code bundle

web-mobile build package

You can still use https://github.com/smoudjs/playable-sdk. But for infrastructure - seem like should be done with a separate package, something like Cocos Creator plugin.

Yes. It seems that your source code is packaged with the ts code, and cocos will be compiled into js code through babel during construction, etc. I'm sorry I may have said something wrong, and I didn't read it carefully. For cocos creator, you can call your tool function in the hook function during construction to repackage the built web-mobile as the target file. And i don't know much about the port monitoring and debugging in your tool how to integrate it

(mathine translation, maybe let u confuse,sry :) tks for ur response

[ahhhyp]

Also maybe there are pre-built versions

does u mean the project? all res in assets folder, res file's uuid in the .meta file. this proj use the engine version 3.8.7
test-proj.zip

[peter-hutsul]

Checked Cocos build in details. It looks like something is possible to do. Need to find a way to bundle all files into one .html, and that's it. Also i saw many playable ads done in Cocos, so it's definitely possible.

Maybe, if you will find or develop some quick solution - how to bundle all files into one .html, via NodeJS - let me know - so i can integrate it faster.

[ahhhyp]

cocos-pnp-playable This is a open-source package tool for cocos.

Need to find a way to bundle all files into one .html

path /packages/playable-adapter-core is bundle file core, bundle file main logic in src/exporter/base.ts

this tool use cheerio to operate DOM, and all res turn to base64. Maybe u should care for cocos asset downloader and parser. This tool overwrite cocos assetManager.downloader to load res from base64-data, check /injects/3x/init.js.

path /packages/playable-adapter is a cocos build plugin...

[ahhhyp]

via NodeJS - let me know

Sorry about this, i don't know mush about this. CocosCreator-Editor write by electron, check cocos extension guide

Capabilities of extensions
With a full Node.js environment inside the extension, it is easy to use the large number of tools available on the npm marketplace for the functionality you want.
If you need to interact with other features, you need to open up the corresponding operation messages for the corresponding features, and we do this within our own extension, via Message System to trigger, query and process functions or data in the editor.

here said nodejs env, this info may helps u?

The following docs may help you:

• cocos-build-guide
• cocos assetManager.downloader API, cocos assetManager.parser API

Sorry for my limited knowledge, if you have any questions about cocos, please email me, I will do my best to help you with what I know