You have "pick a random instance" condition which only picks ONE instance. The next condition, for each, only has access to that random picked instance.

Start small, make a short and simple prototype. With experience you get better.

Nobody made a big game from get go.

A note if I may - I believe that porting the IDE to other platforms should come before new IDE features (tilemaps, debugger etc.).

And this poll would have been infinitely better if we could offer our priority lists of features by giving each option a weight (e.g. I'd give modularity a 10, debugger 9, minor improvements 8 etc.).

Modularity would be a major timesaver that would apply to most projects. Multiplayer, while difficult, also requires server-side coding and infrastructure as well as only applies to minority of projects.

I've already stated on page 14 that I no longer am working on this plugin. I simply do not have expertise nor time to provide the requested features and fixes. Spritefont is at best an amateur's shoddy attempt at plugin development; I simply cannot meet the demands. I am but a writer, not a programmer.

Sorry.

So far, nobody has offered to pick it up, nor am I aware of anyone attempting their own spritefont solution.

Guess I'll have to put something up in the first post...

Because I assumed that the last X or Y index is one less than the weight or height in zero-based coordinate system.

So indexes for 16x16 sprites would be from 0 to 15.

You are right, Developer, looks like my math is screwy. That's what happens when you let an amateur code a plugin! <img src="smileys/smiley5.gif" border="0" align="middle" />

It isn't distorted if you make the spritefont object size twice as large as the individual glyph, in this case at least 32x32. So just make the spritefont object larger than you want it to display.

One of those days I'll really have to sit down and crunch those numbers, since it appears that nobody else is willing to pick this mess up. Oh well!

Don't click the game window. Click outside it, on the webpage background.

Oh, that one has been obsoleted because of a bug I couldn't solve. It didn't pick correct instances.

There is system compare action which does its job well, so I saw no need in doing the spritefont text compare event.

Cramming physics heavy game into itty bitty phones? Someone is optimistic.

Look at it this way; when you try to feed the boolean a number or a string, it throws an error. That's one way to prevent nasty bugs.

An easy way is to just use a private variable on those numbers designating the row.