Manual Entry for Arrays

You would first use push to push each player into the array's back, putting them in the order you want. To find out who the current player is, you look at the first element. When it's time to move to the next player, you're push the first element to the back, then pop the first element (removing it) thus making the 2nd element the 1st.

push 1

Array(1)

push 2

Array(1,2)

push 3

Array(1, 2, 3)

push 1

Array(1, 2, 3, 1)

pop 1

Array(2, 3, 1)

etc...

They don't do anything, they have no use value.

Except you need 500 rep points to post URL links in the forums. After that...*shrug* you're right.

For me, the choice is simple: Whichever one I have art assets for. I'm a pure coder here, my wife and son are artists...however our other business keeps my wife busy and getting my son to actually produce finished art (he's good with concept art!) is tough.

Once of these days I'll have enough to hire artists. Until then, I work on prototypes until I hit the point where I need real art assets and move on to the next one. Have probably half a dozen ready to beta test, and another dozen or so in various states between concept and alpha.

All waiting on art.

Participate in the forum regularly and you'll have 500 in no time.

You can always take screen shots, but if you need to show large swaths of the event sheet that might be problematic.

If he's really adventurous...the event sheets are saved as XML files if the project is save uncompressed. Good luck with him understanding that without writing some sort of parser (which would take a lot more work than just installing Construct 2)

ash1221

If you install the plugin I mentioned earlier, you simply need to create a new page/post with the following short code in it:

[iframe src='' width='px' height='px']

That's it.

Personally, if it's just incrementing the variable each time, I'd do:

Keyboard: on key pressed 1

-System: Add to Variable 1

If you need to limit the variable, you can use the clamp expression. For example, if the highest the value could be is 2:

Keyboard: on key pressed 1

-System: Set Variable to Clamp(Variable+1,0,2)

If you need to roll the variable back to 0 when it goes past 2:

Keyboard: on key pressed 1

-System: Add to Variable 1

System: Compare Variable > 2

-System: Set Variable to 0

etc...

The events are evaluate in order. You just set Variable to 1...so when it reads the next event Variable = 1 and it results in it being true.

Same issue as lemo.

inejwstine

There are some events that would return 3 objects. In your specific scenario onCollision returns just two objects.

1. If two separate collisions happen to occur at the exact same time (rare, but not impossible, right?) each will happen in its own separate event, right? Meaning, there won't be four instances to pick from in the event.

This is correct. Each collision fire's it's own onCollision event.

2. If three instances all collide together (I don't even know if this one is possible; just want to make sure my bases are covered) then will there be three to pick from? Or would it fire off three separate events: one for the collision between instance 0 and 1, one for 1 and 2, and one for 2 and 0?

If your picker returns 3 objects, then they will be object 0, 1 and 2 (0 based) so you would be correct.

Sounds like you would like to do something kinda like this.

Instead of trapping the health variable, you'd want to trap the colour variable into the local variables and test.

Once I get some sleep, I'll write up a full tutorial on this, since it seems to be something that's been coming up a lot.