All tiles in a tileset are considered blocking by default.Only tiles on the 'gameplay' layer are considered when it comes to collision detection & resolve.After all I'm working with a non-programming game/level designer.

The platformer I'm working (more here and here) on uses this strategy, and purposefully makes these properties editable both in Tiled and in a configuration file (Lua script with a table). And some games actually need both GID-based and object-based collisions. Though your assumptions about how this can be done is correct, too. You're probably correct that this is handled in the engine internally and not editable in Tiled. I would assume BrowserQuest uses the tile indices (GIDs) to determine collisions. If anyone knowledgeable with Tiled could take a quick look at the map, I'd appreciate it! I'm tearing my hair out here :). Only because BrowserQuest has whole-tile movement, and it wouldn't look too odd if a small apple, taking up only a fraction of the tile size, prevents movement over that entire tile.īut I'm creating a game with more precise movement, so collision has to be tight to the apple, and I really want to know how BrowserQuest approached collision defining. I could imagine that they are not using explicit collision layers, but instead determining collision in the actual engine, based off the presence of specific tile layer sprites. I especially need to know how they handled less rectangular shapes like: Furthermore, the tile layers containing the tiles for such cliffs have no properties at all, meaning that they didn't just specify 'collision' for such tile layers. I've checked through all their layers, expecting an object layer to be handling cliff collision like:īut there are no such object layers to be found. I'm using BrowserQuest as a big source of inspiration for my project, and I want to know how they handled collision on the level editing side. Create a tiled layer, and make all tiles in the layer have a collision property, and interpret all tiles in the layer as collision objects.Create an object layer, and interpret the shapes in the engine as collision objects.From what I understand, with tiled, there are two main ways to specify collision:

Browserquest 2 map