Alt-click when placing the pivot point to place it on all frames in an animation. You can alt-click crop as well to crop all of the frames but make sure you place the pivot points before cropping, because alt-clicking to place the pivot point only really works if all of the animation frames are the same size.

Actually, from the link you posted:

"It must be noted that only high quality content will be allowed on Desura. Thus please make sure that the content you are trying to publish is of the best standard and as free from glitches and defects as possible. Beta versions will be allowed only if they are of decent quality."

So in a way, they do need to approve it.

Arsonide has been talking in chat about how he's been finishing up David's online plugin (when he's not busy working on his multitudes of other plugins). It sounds mostly complete. You join log on and chat it up with him.

By using start button is down, it will add one to the variable each tick as long as the button is down instead of once for the press. Try using:

On start pressed

(subevents)

• if timescale is equal to 1, set timescale to zero
• else, set timescale to 1

The for each ordered condition sorts all instances of the selected object based upon the parameter entered, in ascending or descending order, so you could also sort via a private variable, for example. For further understand for each, you can read my tutorial here:

The only difference between 'for each' and 'for each ordered' is with 'for each ordered' the order in which the instances are cycled through is determined by the parameter entered.

Make a family 'sort', put all objects you want sorted in the family then use the event 'for each ordered' using the sort family, put sort.y in the parameter field, and use the action sort: bring to front.

I'm too busy to help with writing anything for the book, but I might be able to help with proofreading it a bit to make sure the info is accurate.

It also kinda depends also what crowd you're aiming at as well - for example, the computers the casual game crowd have tend to have less vram. A lot of integrated cards use system ram as vram though, so vram isn't really an issue for those even though they're generally not very powerful.

Basically, yeah, 128 is a good amount to shoot for. I don't think it's necessary anymore but 64 is really the minimum you should bother try for if you want to be sure older computers can play it too. Keep aware that other things like the operating system have to use vram at the same time, though so you might not have a full 128mb to use on a 128mb card!

Most crashes I've found have been from events. Try deleting events first. You don't even have to delete them, you can put them in a disabled group. Do large chunks at a time, like half the events on the first try, to narrow it down quickly.

It depends what part of the world you're in.

Can you tell me if the problems occur at runtime as well?