ID:1492277
 
I have made a map with some stairs, and banisters surrounding them. The stairs are turf but the banisters are objects. I want to make the banisters dense however setting them to 'density = 1' prevents you from walking on the entire piece of turf, and I only want it to stop you from walking on the bit with banisters (essentially how do you set only a part of the turf dense?). Any ideas?
Are you asking about pixel movement? I think a screenshot or diagram would clear this up.

(also this belongs in Developer Help)
You'd need to look up the vars; bound_x, bound_y, bound_width and bound_height.

bound_x is the amount of pixel gap, between the left side of the icon and the place where your icon actually starts. Default is 0.

bound_y is the same as bound_x but the gap is between the bottom of the icon instead of the left side. Default is 0.

bound_width is the length in pixels of your icon's width. Default is 32.

bound)height is the length in pixels of your icon's height. Default is 32.

Those variables are set only for atom/movable types. So you can use it on obj's, but not turf's.
In response to Kaiochao
Yes, pixel movement sounds like what it is. Here is a screenshot: http://s1343.photobucket.com/user/rexasarus/media/ byond_zpsd1659947.png.html
In response to Kaiochao
Thanks Bakasensei, would you have an example for assigning the bounds based on the screenshot I just uploaded?
It looks like it's about 8 pixels wide? Can't tell from the quality. So the vars would be setup something like this:
bound_x=24
bound_width=8
(No need for bound_y, or bound_height. 'Cos both of the defaults are still correct).
Thanks guys, I've got it now :) Falcon lazorz, what you said worked, I had to set the bounds for the mob and the banister and that worked. Thanks again :)
There's an easier syntax for defining a bounding box.
bounds = "[ax],[ay] to [bx],[by]"
/* where
(ax, ay) is the bottom-left corner
(bx, by) is the top-right corner
*/

With this, you don't have to worry about bound_x, bound_y, bound_width, or bound_height. Setting bounds sets all the other variables automatically.

The coordinates are the same as the one shown in the icon editor when you mouse-hover over a pixel.
Thanks Kaiochao, that works and would save a load of time :P