During runtime map editing you can assign triggers to tiles only (not skins).
Tile click, rollover and rollout events are fired if the tile to which the trigger is assigned is globally walkable only.
You are probably assigning a trigger to a non-walkable tile.
we run into the same problem. And I don't see how to work with tile events instead of skin events.
For example, we have a bed skin, that has a click event configured in OpenSpace Editor, that make the player sleep when he clicks on it.
Problem is that he can buy new bed and change the current one. But using edit mode, we can't put skin triggers to the new bed, so when the player changes his bed, he cannot sleep by clicking it anymore.
Same problem with every changeable item wiith which we can interact (doors, tables, chairs, tv, etc...)
Moreover, using the tile events is not even possible, since this kind of object are precisely on non-walkable tiles.
The first bed has its skin triggers defined in the Editor. When the user, during the map editing, changes the bed, OpenSpace is adding a different tile (or supertile) to the map. The new tile should have its skin triggers already defined in the Editor, just like the first one.
In other words you don't assign skin triggers at runtime, but you define them in the Editor for all possible interchangeable items.
