yep, but you can choose an OS which takes little hard disk space. For example, debian uses less than 1GB for the base installation.

Your computer should be able to simulate a slower computer, I've always used virtual box for this.

https://www.virtualbox.org/

And just to reiterate what's already been said, only 0, 1 and 2 registered, tested on Chrome, Firefox, IE, Edge, Opera and NWjs

From what I can see, Construct only supports the three main buttons of mice, I am informed that it is possible in JavaScript to get input on all mouse buttons, here: https://www.w3.org/TR/DOM-Level-3-Event ... ouseevents. I was thinking of implmenting this myself with the SDK, but I don't see how that would work without changing the original mouse plugin. So can I request here that the ability to have button codes for the mouse a feature of Construct?

Wolod I was making it for the next version, which I lost when I updated my pc. Sorry

Sigma83

oosyrag is right, but fails to mention that these the variables should not be instance variables of the individual objects, but instance variables of the family.

Don't use a behaviour?

Something like:

every tick, if mouse is over west, map.setX to map.X + 2

You can add all of the weapons to a family called weapon and all of the enemies to a family called enemy, then you can do weapon on collision with enemy.

Niek It shouldn't cause any lag, see this example: https://dl.dropboxusercontent.com/u/706 ... ample.capx

If (isJumping)

• system.ScrollToPosition(player.X, player.Y)

if you're going for a doodlejump sort of thing have 'isJumping' be something along the lines of player.VectorY < 0

It all depends on how your map is represented. There are different algorithms which will do different things, some may be what you want, and some won't be. Nearly all algorithms will be based off some sort of noise function, but the implementation will be specific to the levels you want to generate.

dellong to make it work properly, for every viewport I needed to re-render the screen so that it captured the correct area, and this is probably why it's so intensive. I will look into optimising as soon as possible.