I like Construct 3 but I don't like where it's going. You need to decide or find a way forward. This is your problem. If you ignore it, it's the developers' problem too. We developers are already doing our best for Construct. No ad network will care about your arguments for a 30% size increase. They won't care about a few developers voicing it either.

Thanks for everything. We'll have to move to a different framework with our company or find a solution. I've done my best to represent Construct 3 in a good way for playable ads, but if the developer of c3 feels they can't continue, there's not much we can do. This situation will be clarified in your own way Ashley

Note: One solution might be to answer the open question about whether old engine versions and all their features will be kept alive or not, which you did not answer.

Thank you

Base64 generally speeds up ad load time (not to mention ad size) and reduces dependency on outsourcing. Outsourcing, even within the same directory, is not good for ad networks and is not supported. (only some ad networks support it and you still have clear limits for the assets (like using base64))

In summary, using base64 is accepted by all ad networks without exception, even if you are limited to a total limit of 5mb. Your own "zip" format is not supported by almost any ad network. Ad networks support the "zip" format, but there are still certain rules, and your zip format (almost) doesn't follow any of them.

So you either need to remove support for playable ads or produce a format that conforms to these rules. Your defense of "go talk to them" makes no sense to the ad networks, sorry to say that...

...

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.

Ashley

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

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.