This didn't used to be a problem but the new version of quest now doesn't like variables being named as numbers, this is screwing up some of my code that would be so very nasty without being able to have variables named as numbers. I thought quest 4 was meant to be backwards compatible...

Thanks, I'll take a look into this.

I presume you're referring to having variables called things like #1#?

Very nasty... but yes, it is retained for backwards compatibility (only because a beta of Quest 1.0 had variables like that, but if people have used this since then it ought to still work really)

I'm curious; what are you doing that requires numeric named variables?

It's a username checker, checking for numbers and such within the name. It used to be huge then ages ago I put it in a loop and made it so much nicer...

Also, Alex, when are you adding sounds and such for multiplayer stuff?

Sounds etc. for multiplayer is on the list... it will actually be far easier for users connecting through the web-based interface, since that already handles remote pictures and sounds.

Oops. I found it was a real error after all causing it, I thought it was something else though. Turns out I wrote:

inc <%variable%>

So it was double '%'ed in a way. Sorry.... It's the small stuff like that you miss.