spy84 actually he's been doing a lot of work updating the plugin, and odds are what he's doing will greatly change the method of working with the object for the better (I believe in-plugin-in-editor object placement was planned?)

The best way to learn new or experimental things like this is to play around with it. I know that's not a great option, but it's definitely one of the most advanced Construct 2 plugins I've ever seen and will take time to learn (almost like a whole new engine )

The Browser plugin has the ability to run Javascript: https://www.scirra.com/manual/110/browser

Try storing the results of this Javascript: "new Date()" to a text variable and see if that gives the info you're looking for <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

You can try storing the global variables into the array on save and then when loading set them from array

I think it's actually running both of those: http://www.php.net/manual/en/language.o ... arison.php

PHP is kinda like C languages, you need to use == when doing a check (= sets a value) <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

Still, I'd love if every language was a quick and simple as BASIC <img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz">

I think Pin is dependent on timescale, so if you stop time then the player will no longer position to the playerbox, the second method should work whether timescale is 0 (stopped) or not. I think performance-wise it's not a huge difference either way though

Nope, usually for variables/expressions there should never be quotes I think, and awesome glad to hear it's working!

Remove the quotes from "SaveArray.AsJSON" so it's just SaveArray.AsJSON should do it (otherwise the only thing saved is the literal text: "SaveArray.AsJSON"

Hope that helps

He's using the latest beta, you can grab that from: https://www.scirra.com/construct2/releases/r174

you could try:

Create at:

X = choose(random(5, 630), random(650, 1270))

Y = choose(random(5, 350), random(370, 710))

I don't know how well that will work, but what it's basically doing is:

Choose () = pick a random option from list of options

so for X: spawn on left side of player, or right side of player (assuming player is at center 640, 360) and about 10 pixels away from exact center

then for Y: spawn on top or bottom side of player

brunopalermo Ahh, I can see that reading of it now looking back at his request. I was thinking he was reporting what currently happens rather than what he'd like to happen. Thanks!

brunopalermo ahh okay, also I was suggesting he instead adds to MAX_PV, as it sounds like he wants players to get a health bonus that auto-regenerating can go back to, but they lose that bonus on death. Either way works though

The pixel rounding at render? I don't believe so, all it does is stop things from rendering at sub-pixel amounts by rounding to nearest whole pixel.