Do you need someone who doesn't do anything and never comes to meetings, then takes all the credits?

Because the last event overrides the preceding event.

When the enemy leaves the layout to left, what do you suppose happens?

1. The event 3 is true, as it is outside layout and the angle is 180. Set the angle to 0.

2. Next, check the last event, keeping in mind that we now have angle at 0. Still outside layout? Yup. Angle equal to 0? Yup. Set angle to 180.

So what do we have here? An enemy that keeps turning back and forth just outside the layout.

You accidentally logic. ;)

Tip: you can condense those events this way-

+ enemy has wall to left

+ OR

+ enemy has wall to right

+ OR

+ enemy is outside layout

enemy: set angle to enemy.Angle + 180 (180 becomes 0 and 0 becomes 180 )

enemy: set horizontal speed to enemy.HorizontalSpeed * -1 (260 becomes -260, -260 becomes 260)

Just set the speed at start of layout or something and there you have it, everything you want in one event. :)

Hm, a good opportunity to whip something together and get back into the "groove".

You can have it keep moving until it encounters an obstacle, in which case it turns around. You can use solid (other enemies, walls etc.) or invisible sprites (in case of hanging platforms so they don't fall down).

*prepares the whip'o'crackin'*

Don't worry, Steve just went to notify God of copyright infringement in regard to the apple.

Your monitor typically runs at 60Hz or 75Hz. These are considered to be ideal refresh rates for your eyes not to notice any transition between frames. That means you are shown 60 or 75 pictures per second.

Timedelta or dt is the time between two consequent frames. How much time does it take before the next frame is shown?

You could simply calculate 1/60 = 0,0166666... or 16,7 milliseconds, however in reality, the computer doesn't always render them exactly at that time. Sometimes it takes longer (particularly intensive processing), sometimes it takes shorter (black screen, nothing to draw), so timedelta can differ.

So, Construct remembers how long it took to draw a frame, the time since last frame. That value is timedelta. You can use this value for a lot of stuff, like precise movement.

For example, if you move 2 pixels right after each frame (which "Always" or "On every tick" does), it won't move at the same speed if the game runs at 30 FPS (frames per seconds); because the frames are shown half as often, the dot moves half as slow, too. Likewise, if you are rendering at 120 FPS, it will move twice as fast.

That effect is often undesirable, so instead you use timedelta. By multiplying the desired speed with timedelta value, you get exactly how much you need it to move each frame, so it will always move at the same speed even if your game slows down or speeds up.

I hope that helped!

Everything is possible given enough time and effort.

You can generate them on the fly. Make a level editor, create levels and save them as data, which is then read when loading the level. Then just create stuff just before it comes onscreen.

Download speed and CPU power have nothing to do with the way updates are handled. On an unrelated note, multi-core 3GHz CPUs are available for as low as 40? and broadband internet is pretty widespread now. I don't see why should the majority be bogged down by select few unfortunates still stuck in the P2 and 56Kb era.

The updater would be nice and convenient, however it is not absolutely necessary. We can live without it, unlike certain upcoming C2 features. Remember that Scirra isn't all that great in body count, however big their aspirations are.

Besides, I tend to be wary about auto-updaters, having gained a few grey hairs from update failures.

Most likely fake. Most spambots report fake browser information.

Graphic and sound assets are the main culprits. Don't go overboard on texture sizes nor animations. There is a reason modern AAA titles occupy a whole DVD despite being short gameplay wise.