Construct now supports using the WebP image format when exporting your projects. It can reduce the file size of images by 20-30% with few downsides, helping ens...
Why would you need base64?
In almost all my Games I use load from URL to have better control of the Memory Management, is that not possible?
That's a really important feature to have if you didn't add it yet as if it doesn't support it sadly is not gonna be really useful for users that heavily use load from URL like me.
Edit:
Just to make sure I explained it properly, what I meant is if we can convert a (WebP to Base64) at Run Time using Binary Data Plugin and after load it back any time From URL?
Is that supported or will it have any issues?
Construct already has memory management features built in, why aren't you using those?
The build-in Memory management is not useful in this case as all the Actions require that you have the images in a (Layout or inside the Project) which will bring me back to the big issue that C3 has which is that it preloads all the images in the project when it first runs the game so when you have thousands of frames images, C3 takes very long to load the game and this is especially killer on mobiles so that's why we have to balance it up with load from URL etc..... I explained this issue to you before on other threads.
Also, don't just look at the Memory issue as very often I saw on the forum threads asking how to convert this image to base64 to send it to Server, etc... so I think is a very common thing used not just for memory management.
Sorry, I had to split the message as it was very long:
To be honest we need one feature that you could tick on sprite sheets to prevent C3 from preloading them when it first loads the game this way we could have more control over what it loads when the game loads for the first time to avoid the long waiting loading screens but I don't see how this could work as it looks like a very complex feature and not sure if it's even possible to implement.