Hi,

not sure, but try to cast webstorage.localValue to int..

Then you checks will be

HighScore < int(WebStorage.LocalValue())..

Bump

ekajuan : price depends on the quality of the app/game too.

Sell a flappy bird 1$ w/ adds, and 10$ w/o.. you'll get 0 dowloads ^^

You can do the Sprite.setColor only when you change the values of instance variables to avoid the update at each tick

Hi,

you can try by creating a joystick : https://www.scirra.com/tutorials/398/to ... ontrollers

Hi,

with the effect "set color", you can change the params progressively in the event sheet.

3 instances variables : R, G and B. Play with that. And every tick, set the parameter of the effect to those values.

Something like :

[attachment=0:168seya8][/attachment:168seya8]

Gearworkdragon

You can test by adding the effect "Sphere" to the layer of the map.

Nevertheless, I never used this, but with some tests, I think you can make something ^^

I don't know if you can, I always make an apk to test.

If official IAP doesn't work (but it's strange), you can try with cranberrygame phonegap IAP plugin (http://shatter-box.com/downloads/phonegap-admob/).

It's pretty simple to use it, and it works for me <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

That's right.

You can check it at each checkpoint (and not every tick to not waste memory). With previous example, if the user is touching "C", the variable string should be "ABC", if not, you can alert the user, or game over (or whatever)

This work if y1 and y2 are the same.

Otherwise, it will be :

x_middle = (x1+x2)/2

y_middle = (y1+y2)/2

If you want to use physics, give the behavior physics to the ground too, and set the parameter immovable to true.

It should do the trick.

If the user touch the screen all along the movement, the string will be correct. If the user get off the screen, the string will be reinitialised, then it wont be correct at the end.

Example : your checkpoints are A B C D E F.

Correct case : The user starts touching the screen, go through A (=> string = A), trhough B (=> string = AB)... through F => string = ABCDEF ==> correct

Incorrect case : The user starts touching the screen, go through A (=> string = A), trhough B (=> string = AB), then dont touch the screen between B & C (==> string = ""), then touch again and go through C (=> string = C) ... through F ==> string = CDEF ==> incorrect