Per the v323 release notes,
image() has several optional arguments for pixel offsets. Providing arguments for pixel_x, pixel_y, and pixel_z will work, but not for pixel_w.Code Snippet:
mob/verb/ImagePixelOffsets()
// pixel_w doesn't work, regardless of whether or not the argument is explicitly named, i.e. pixel_w = 128
var/image/i = image(icon(), src, "what", 2, NORTH, 16, 32, 64, 128)
world << "pixel_* offsets: {x = [i.pixel_x], y = [i.pixel_y], z = [i.pixel_z], w = [i.pixel_w]}"
Expected Results:
Output: pixel_* offsets: {x = 16, y = 32, z = 64, w = 128}Actual Results:
Output: pixel_* offsets: {x = 16, y = 32, z = 64, w = 0}Reasoning:
I'd wager this is a bug due to the fact
image() accepts pixel_w as a named argument--yet will reject anything else that isn't supported (like suffix or maptext_x, for example). It would also be strange to only support setting pixel_z and not its companion pixel_w.