New this build: a new Tilemap plugin and a built-in tilemap editor complete with tilemap editing tools from within the layout view; and a long-overdue autosave option!
Construct 2's new Tilemap support is based around two parts: firstly, the Tilemap plugin; secondly, the new Tilemap bar in the editor displays the current tilemap image, and allows you to draw directly in to a Tilemap object.
There are a couple of tools such as pencil/stamp mode, eraser, and rectangle. Note the rectangle tool can automatically nine-patch your tiles if you have a 3x3 selection, making it quick to draw certain kinds of boxes in the tilemap.
The Tilemap bar also allows you to import .TMX files from the third-party tilemap editor Tiled. Only a subset of features are supported (e.g. isometric or hex maps are not currently supported - just squares), but this provides a nice alternative way to use tilemaps in Construct 2. Tiled has some nifty features like automatically merging the edges of different terrain types as you draw, and we probably won't reinvent the wheel supporting things like that in C2, so take advantage of the importer if you need it.
For handling collisions, any tile with register a collision, and only empty spaces with no tile will not register a collision. To design levels where only a few tiles collide, use tilemap objects on different layers. You could have for example a background decorative tilemap, and then a tilemap on top of that with just the tiles the player collides with, such as walls or platforms.
Software is never perfect, and sometimes it crashes. This much-requested feature should help protect against that. It will automatically save a separate .autosave.capx file in the same folder as your .capx/project on a regular basis. When it autosaves it will not make another autobackup (there's not much point - they are all written to the same directory, so there's not much extra backup security), but it will also save to your three backup folders as well when autosaving. Then if Construct 2 or your system crashes and you forgot to press 'Save' for hours, the autosave file should have a reasonably recent version of your work.
We hope to enable autosave by default by the next stable build, but for now it is off by default. This is because it's a surprisingly complicated feature to implement (unlike an ordinary save it must not modify any of the existing project files or change the saved state of the project). If there are bugs, it could result in lost work - possibly in subtle ways, such as writing a corrupt autosave file, which then is not hlepful in the event of a crash. It is helpful for it to be tested though, so we recommend making manual backups of any important projects then turning it on. Every now and then check if your .autosave.capx file opens correctly, and let us know if there are any problems.