kevin :
I fully hope to do a sequel, but I’m taking a break from Starcom to avoid burnout. Once I start work on it again, I’ll try to track own people who have expressed interest to beta test.

I’m still looking for Starcom 2.
I don’t need much changes; I’d suggest having a larger universe; and having for instance 3 ways of solving the game; eg. 8 things you have to do, then 1 out of 3 that you can choose yourself, to vary the game.
I stilll play Starcom, even though I’ve completed it a bunch of times.
It’s a great game for relaxing (but as I wrote above, it would be awesome with some variations, in case you play it more than a few times).
The look and feel of the game is excelent. Controlling the ship is excellent.
Unfortunately, Flash has a problem, so when in my browser, I click another application, and then return to the browser, the keys don’t work anymore, and I have to start over.
I’m happy that there is a way to save the game.

I recommend downloading the high quality version (click on the time near the top to go to the download page).

1) With the retro thrusters, they should either be excluded from the game, or be activated after the player has stopped moving for a couple of seconds. Otherwise making the ship remain completely stationary would be a real pain.

2) With the missle lock, an easy solution would be to add a toggle “permanent lock” key. The player could lock on to say, a Destroyer and then press “L”, and no matter what the player moves his mouse over, it would remain locked on to the Destroyer. Then he could either press “L” again, or kill the destroyer to reset the game to automatic targeting.

Anyways, great game and keep up the good work.

Also I decompiled it to see why there was so much lag on my computer, and even delayed responses to key presses, and key releases. There are a lot of untyped variables (untyped variables or variables typed as * (same thing) are easily 4x slower than a typed object, and for things like int it’s more than 10x as slow), and unnecessary copying of variables all over the place.
In the sequel, you should explicitly type every variable you create, and you don’t need to make a copy of the XML before you write it to the ByteArray (ByteArray makes a copy of the memory at that location, so when you do that, you have three copies in memory, this can lead to a memory leak).