We should be able to paint "features" onto the map. These can be subtle things which don't affect gameplay such as piles of bodies in dungeons or they could be obstacles such as tables or trees. In the case of features we may want them to be positioned and sized arbitrarily as they are meant to provide flare and their position doesn't matter, however if they also serve as obstacles we probably want them to be aligned to game tiles and have a well defined boundary.
Implementation.
Similar to the way tiles work, we should have a list of feature types, and a list of features.
Each feature type could have:
A data URI image.
A number of tiles in width and height (if used as a blocking object).
The map would then have a list of features and the update function in dungeon-client.js would intelligently determine which features to draw and where based on the visible tiles in the viewport.
Summary.
We should be able to paint "features" onto the map. These can be subtle things which don't affect gameplay such as piles of bodies in dungeons or they could be obstacles such as tables or trees. In the case of features we may want them to be positioned and sized arbitrarily as they are meant to provide flare and their position doesn't matter, however if they also serve as obstacles we probably want them to be aligned to game tiles and have a well defined boundary.
Implementation.
Similar to the way tiles work, we should have a list of feature types, and a list of features.
Each feature type could have:
The map would then have a list of features and the update function in dungeon-client.js would intelligently determine which features to draw and where based on the visible tiles in the viewport.