and all the addIncludeFile/setIncludeFile mentioning them in JsExtension.js files.
In GDJS: the GDJS/Runtime/Cocos2d folder and GDJS/Runtime/cocos-* folders.
the exporter code that copies cocos files.
We will continue to keep the architecture that separate the gdjs.RuntimeObject from their renderer. This is useful if we want to introduce a new rendering engine in the future, or if we want to make a "headless" version of games (for multiplayer servers for example).
Similar to https://github.com/4ian/GDevelop/issues/2708 (GDCpp/SFML that could be removed), we're not using or supporting properly Cocos2d-JS renderers anymore.
This means that we can remove:
*cocos-renderer*
files.GDJS/Runtime/Cocos2d
folder andGDJS/Runtime/cocos-*
folders.We will continue to keep the architecture that separate the
gdjs.RuntimeObject
from their renderer. This is useful if we want to introduce a new rendering engine in the future, or if we want to make a "headless" version of games (for multiplayer servers for example).