Off the bat, I remember that things like arrays etc. are now 1-indexed; also overlapping was bugged, so you had to use overlap at offset (0,0). I'm not sure whether that was in 98.7.

Just a couple thoughts.

[quote:1ank4xw4]Each individual copy of a CEG-protected game is only playable by the Steam account authorized to access it.

The catch is right there. You need Steam to play it, I think.

http://www.netfirms.com/web-hosting/

2000 GB monthly transfer, $8.95, quite a few features. Has a lot of spiffy badges, too.

FatCow looks pretty reliable and professional, though I would do some research if I was you.

Made in Flash. Oh joy, jammed keyboard controls and annoying beeping. I do like the art of it, but Flash games make me cry

There is only one solid method that ensures people will buy your game if they like it... look at Galactic Civilizations. When you buy the game, you get a key that you can create an account with - or something like that - which enables you to download patches and other bonus content. You can also play online (well, GC has this Metaverse thingy).

For Construct games, well, you could use unique keys to 'unlock' the content and extra features. When someone buys your game, you send them an unique key! Accounts can only be created with an unique key, so cloned keys can't be used to create a new account, thus one can't just distribute the key to 'friends'. It will work to unlock the game, but account-related features - patches, bonus content etc. - are only available to original accounts.

That is how it works the best in my opinion. Remote computers work as well; you just install the content you downloaded with your account, as long as the used keys match.

Indeed, show us what you can do and we are talking! That is how things go in indie game development. Blind dates tend to go awry.

I haven't done much about that, but I have one thing on my mind: Bullet behavior. If you set its speed to instant, it will check for collision if you use bullet behavior's "On Step" trigger.

Worth noting.

Oh yeah! Thanks!

Well, where do we get the list of used plugins, then?

Suppose that someone's been working on a big project for a quite while, adding and removing behaviors... then forgot about one particular behavior that isn't even used. That leads to bloating and potentially bugs.

Uh... private variables are gonna multiply like crazy. It is best if we leave them under respective objects they belong to.

Anyway, for behaviors, it'd be nice to see which objects have each behavior type, in case I missed one or want to change some behavior settings across the board. Basically, when you add a [Bullet] behavior, you'd get a Bullet folder under Behaviors folder, when you open it, it lists the objects with said behavior.

Your wish will come true in about... say... 6 months, when days start getting shorter!