exporting as 'node-webkit' is for desktop

edit: whoops it isn't available on free

are you aware of the tokenat() and tokencount() expressions? they might be all you need

you could store your dialogue in a string variable.. whether global/local or private as an instance variable on a character.

storing the dialogue like this:

Good morning, Commander./Today, you have an appointment with Alex 9 AM/Please proceed to the meeting room immediately

means that you can return parts of it (tokens) using tokenat(text,index,separator)

indexes start from 0 so it goes like this:

tokenat(Dialogue,0,"/")

returns the first part

tokenat(Dialogue,1,"/")

returns the second part

etc

tokencount(Dialogue,"/") as you've probably guessed returns the amount of tokens.. it'd be useful for automating the dialogue without having to do an event for each line.

a few ways to do 'is within 20px' along just the X axis would be:

system compare two values | abs(platform.x-platform2.x) is less than 20

or

system is inbetween values | platform2.x-20 < platform.x > platform2.x+20

but like i said, filtering could be a little awkward depending on your context.

also if you use username itll notify them directly! i only saw this reply by chance

you should probably accommodate for any changes an update makes, it can be a little annoying sometimes but it'll be easier in the long run

but anyway, if you multiply your force by 1-(distance/radius)

so it looks something like:

Force*(1-(distance/radius))

(where radius is the maximum distance)

It means the force will be less the further away the object is.

you know, so it won't be weird when an object is 1px outside of the radius and isnt affected at all, but then may be just touching the radius and suddenly will be blasted away at full force.

dooley did you check my cap before posting?

it takes into account distance etc

preview

There is a second method in this .capx, which applies a force to the 4 corners of the box instead of just the centre.

This is so that even if the explosion centre only has a direct line to one of the corners, it will still push it.

.capx

are you talking about an explosive box splitting into parts first? or just the objects around it getting pushed away?

A way to differentiate between two instances of the same object would be to use a family with just that one object in.. i like to do it so that if the object is called 'platform', create a family called 'platform2'

that way you can do

+if platform is within 20px of platform2

destroy platform 2.. or move or whatever

You'll probably need to fiddle with other filtering of instances.. so that it only applies to the platforms just created for example. but im not sure the context its in so i cant give a definite asnwer

click to drag boxes

preview

seesaw returns to its normal position with 'apply torque towards angle', with a torque force that is proportional to the angle difference (otherwise it will vibrate back and forth)

i dont think you need to make the force proportional though.. you could just try setting the angular damping very high

capx

sounds cool,

there is an expression called 'loopindex' which returns the index of the current loop.

Indexes begin on zero.. so the first index of the loop is 0, the second is 1 and the third is 2 etc

so to do something different on the third repetition of a loop, you can do:

+system, compare two values | loopindex is equal to 2

->create turret etc

to do this thing *every* three repetitions, (starting on the first) you can use the % operator:

+system, compare two values | loopindex%3 is equal to 0

->create turret etc

the '%3' makes it go back to zero on every multiple of 3

so for example '107 % 100' will return 7

and '541 % 100' will return 41

and '6 % 3' will return 0

also if you dont want it starting on the first, you can offset it like '(loopindex+1)%3'

4. https://www.scirra.com/forum/construct-classic_forums_cat11.html :)

also these are pretty vague questions,

have you started to attempt to do any of these before asking?

The black box sounds like a bug to do with shaders or blend modes. Although different folders shouldn't produce this bug..