r269 introduces audio tracks to be played in timelines. There are a few caveats which are not obvious about them. Here they are:

1. The Audio plugin needs to be included in the project. Timelines playing audio use it under the hood, but they do not enforce it's existence in the project.
2. A timeline can not play audio until there has been any meaningful user input. A single click is enough, but if there is no user input, no audio will be played.
3. For better results, make sure the audio that is going to be played by a timeline is preloaded before the timeline starts playback.
4. If a timeline is played backwards by using a negative playback rate, audio will not be played. A timeline will only trigger audio playback when playing with a positive playback rate.
5. Audio tracks are created with the default audio source property track, but it is also possible to add an optional volume property track by right clicking on the track and selecting the Add properties context menu option.

I think those are all the less obvious details.

As far as I know, getting whitelisted is the only requirement. In my own testing that was the only thing I needed to do. I wasn't too clear in whether the process is fully automated or if there is some form of manual reviewing going on though.

I don't know if you strictly need to have existing traffic, but I think it weights in the review process, that is what I meant in the first post when I mention you need a "real" website. I am not sure what would happen in the case of submitting a brand new website that looks nice but has little to no exposure.

As for iframes, I tried this out myself to be sure what was going to happen. I did this by placing my whitelisted website in an iframe in another website I made which is not whitelisted.

The results where, interesting...

Initially it didn't work, as expected because the website iframing the original content was not whitelisted. But I found out that if I navigated in the iframe to other parts of the contained website, then ads started to work in it. I mentioned this to people at Google and they told me that shouldn't have worked. So I am thinking that at one point or another they will fix it.

As of r269 we are trying out a new advertising technology, Google's Ad Placement API.

Currently it is only possible to show ads in mobile exports. This new feature allows to show ads in web exports, so it opens up a new venue for monetization.

The current implementation is rolled up together with the mobile ads in the Mobile Adverts plugin, this is because the API's are very similar, the idea being that the same project can show ads whether it is exported for mobile or web.

The most important thing to remember is that web ads will not just work on any website. You will need to get the website that is going to host your game to be whitelisted. This means that ideally you should control this website, to be able to update it.

First let's go over the things you will need to set up before any of this works.

Adsense

1. Sign up for an Adsense account.
2. You will need a website which is whitelisted to show ads.
3. Fill in this form to indicate interest in using the Ad Placement API.

How do I whitelist my website?

1. Visit the Sites options in the left hand side menu of your Adsense account.
2. Find the Add site button and click it to start adding your website.
3. Follow the steps.
4. You will need to modify the root of your website by adding a small script to it.
5. Request a review.

After sometime, hopefully your website will be approved and your game will be able to show ads.

Plugin setup

The plugin properties have changed a little bit to accommodate for the new changes. There are two groups Mobile export and Web export, these are just cosmetic and highlight to which kind of export the properties are related to.

The Publisher ID property makes a return after being removed in a previous release. Now it only affects web adverts, so if you are just using the plugin for mobile, you don't need to add it.

If you need it, it can be found in the left hand side menu of your Adsense account in "Account" -> "Account information"

Differences between Mobile and Web

Ad units

If you only want to show web ads, it is not necessary to provide ad units in your actions, the field can be left blank. If you are planning to use the same project for web and mobile though, you will still need to provide them.

Supported ads

This new API only supports two types of ads: Interstitial ads and Rewarded ads. Banner ads are not supported, trying to show them in a web export will have no effect.

About Rewarded Ads

There is a slight difference between rewarded ads in mobile and rewarded ads in web that should be considered.

In mobile when the ad is viewed you can use the RewardType and RewardValue expression to get information about the reward and this information is set in your Admob account through the ad unit.

In a web export, because you don't use ad units, the rewarded ads will always return the value "Reward" for the RewardType expression and the value of "1" for the RewardValue expression.

For this reason it is recommended to use the Platform Info plugin to decide what to do after a rewarded ad is viewed, depending on what platform the game is running on.

GDPR related actions, conditions and expressions

Currently there is no support for consent gathering in a web export, so the Show user consent dialog action does nothing. This might change in the future.

ConsentStatus and IDFAStatus expressions will always return "UNKNOWN" and "not-determined" respectively.

The condition is in EEA or unknown will always evaluate to "true".

Set max advert content rating, Tag for child directed treatment, Tag for under age of consent and Request IDFA actions are not supported in a web export.

Ad blockers

Be aware that web adverts are treated just as any other advertising technology in web, so it will be blocked by ad blockers. Remember to configure your ad blocker to ommit preview.construct.net to see the test ads when developing in Construct and localhost if your are working on your own website.

This is all still in beta

This is not only true on our side at Scirra, but also on Google's side. What I am trying to say is that things might change in the future.

That should cover everything for now, let us know how this works out for you!

I just updated both plugins to the latest versions.

admob-plus-cordova to version 1.25.0 and cordova-plugin-consent to version 2.2.0.

The change will be available in the next beta release.

I find it impossible to tell if that will help in any way thought.

Instead of showing the text right away, you can try pushing values into an array when a message is shown.

Then at the end of the event sheet, you loop through the array showing all the messages neatly stacked, you would need multiple text instances to do this and a little calculation to figure out the position of each text instance.

If you want to keep everything in the same text instance, you can loop the array and combine all the messages.

Don't forget to clear the array after showing all the messages!

tarek2

I found two problems, the first one is that those files are malformed JSON.

	"frame-durations": [1, 2, 3, 4, ...]