For a scroll-able chat output box, I would use an array to maintain the chat history. Every time a chat line is sent, it is added as a new row in the array. Then, the text box would be updated using variables, i.e. FirstRow and LastRow. On every update, you would clear the text box and display the rows specified by the variables.

That way you can also have your scroll controls just change the variables, since you are displaying the rows based on the variables. This would allow for other controls to manage the history, or allow for saving the history.

This is the way I would try to do it, but there are probably better ways.

I hope that helps!

Thank you, Scirra! You are an oasis in a game making wilderness!

ZhaoYun, I have updated the original capx:

http://dl.dropbox.com/u/38038537/examples/AI_Example.capx

This version creates multiple copies of the enemy object, then uses the "pick nearest to" event to determine against which object the sub-events should be run.

I hope this helps.

That was it —

I am running C2 on my my laptop. At work, I have 3 displays, and I was running C2 on display #3. The new project dialog was still going to the non-existent display #3 when I was running C2 at home (with only 1 display).

Thanks for your help!

Yeah, they are the latest drivers. I used the utility you created to go to the AMD site. I updated them just before that last screen shot.

I will play with it some more.

In R90, when I try to create a new project, C2 locks up.

Before clicking New:

<img src="http://dl.dropbox.com/u/38038537/pictures/C2BeforeNew.png" border="0" />

After clicking New:

<img src="http://dl.dropbox.com/u/38038537/pictures/C2AfterNew.png" border="0" />

I have to kill the process in task manager to close it.

This only happens when i try to create a new project. i can open existing projects with no issue. I did not have this issue in R89 or the last stable release (R84?)

• Windows 7, 64-bit
• AMD FirePro M8900

Video drivers are up-to-date.

I found this post helpful to get an understanding of the concept: scirra.com/forum/lerp-clarification_topic48641.html

I also found this external post useful: forums.create.msdn.com/forums/p/45626/272505.aspx

I hope those help.

Gamekill, i can hear sound, using the same machine as specified above.

nihakue, the sound worked for me. Here are my specs:

• Windows 7, 64-bit
• Chrome 18.0.1025.168
• C2 R87

I hope that helps.

Nice concept Newt. It can be addicting, and adding the elements mentioned by the other posters would only make it better.

I don't know if it's nostalgia or what, but i found the graphics style to be really captivating. Good job!

Edit: After playing some more, i would like to add some suggestions.

• When the ship is being built, some type of indicator, like a dial or something, to show the ship's current power level, would be nice. I realize you can sort of tell by the opacity of the ship, but some type of metered indicator would be cool. Maybe the background of the square in which the ship is being built could slowly fill with color, like a clock hand sweeping around.

• Some type of chart showing the distribution of ships by their power level, i.e. 20% heavy; 50% medium; 30% light, or whatever.

• A pause button!

You should contact Tom regarding web-site issues.

but it would also be usefull for textgames en direct textinput without inputfield. This was my primary reason for creating this plug-in in the first place. At the time, there was limited support for text entry. I was also looking at a way to be able to set custom key mappings, e.g. allow the player to reset movement from WASD to something else, in game. This would then allow the constructor to set a variable, and check that variable using the built-in keyboard functions. It was never meant to replace movement using the keyboard plug-in.

Since then, new features/plug-ins have been introduced which pretty much address these issues. I still think this plug-in might be useful in some situations, but it does not interact well with the keyboard plug-in. The keyboard plug-in basically overrides the keycode functionality.

IMO, the best option would be for Ashley to include the keycode functionality in the keyboard plug-in, when he has time, and if the need still exists.