New Playable Ad zip export; Updated preview & export code; Bug fixes & improvements.
Will you stop supporting playable ads in single HTML format? If you do this, Construct 3 will be removed from many advertising networks with this update. Many ad networks don't support the ‘zip’ format. Even if they do, they still expect assets to be encoded in base64.
This shows that Construct 3 is not suitable to develop playable ads anymore (soon or in the future). I've analysed your 'zip' format. Some ad networks allow it (1 or 2 ad network), but the most popular ones don't. They won't ignore the 'general' rules and add new ones just because you post an update for C3!
AppLovin only supports "single HTML" format. Mintegral ad network supports the ‘zip’ format, but your ‘zip’ format does not comply with the rules.
Remove single HTML format export = remove playable ad export.
I would like to suggest that you find the most reasonable way to maintain the single HTML format, given that AppLovin is an important advertising network in the market. Additionally, the incorrectly packaged "zip" format should be managed according to the following guidelines (see heading 12):
mindworks-creative.com/review/doc
Choosing this method for packaging, similar to the one seen in the related thread and used by the single html format, makes a zipped playable ad work on all ad networks that “support the zip format”. Otherwise it will be a supported format for a few ad networks that no one else chooses to use. This is not enough to say that "we support playable ad export".
Ashley
As we have said we will keep supporting it so long as it is feasible to do so, but in future it may well become infeasible. If continuing to support single-file playable ads blocks us from making significant improvements to the rest of the engine, then we will probably be forced to drop support for single-file playable ads in order to be able to continue improving Construct for everyone else. This is why we have asked everyone affected to contact their ad networks and ask them to support the zip format - we can likely support that forever with minimal maintenance required. We can't allow the difficulty of supporting single-file playable ads to hold back the entire engine.
Thanks for your interest and reply. Good to hear you'll keep the single HTML format for a while. You need to fix the way you store assets in your zip format. Many ad networks support zip, but all assets must be encoded as base64. Check the link I sent you under point 12. To make your zip format work on most ad networks, we need that.
I understand your concerns and trust you'll find a solution.
However, your existing single HTML format can be converted to zip in just 1 minute. We've even developed an automation for this. I hope this new zip format can be adapted to the single HTML format easly by users. In summary, your ‘zip’ format is currently unusable.
The point of the zip format is you have normal files and don't have to base64 encode anything. I was talking about a zip of web assets - just all the normal files you'd otherwise use on a web server, but zipped. If some particular network has a format that uses a zip file but still requires base64 encoding files within that, I'd say that's a pretty weird format and I don't think we'd want to support that for the same reasons as the single-file format. Nothing should need base64 encoding at all. So please ask them as well to support normal zip files.