ID:1293071
 
Code:
obj/roar
icon='roar.dmi'
r1
icon_state="1"
pixel_x=-32
pixel_y=-32
r11
icon_state="1"
pixel_x=-96
pixel_y=-96
r2
icon_state="2"
pixel_y=-32
r22
icon_state="2"
pixel_y=-96
r3
icon_state="3"
pixel_x=32
pixel_y=-32


Problem description:

Codes\Oversized Icons.dm:707:error: -32: bad number

I was updating and decided to hit Clean Compile (hoping it would cut down resource a bit) and all it did was create errors out of nowhere saying bad number. How do I fix this?

btw there are over 100 errors similar to this
It sounds like you've ran into the bug that was reported here. At present it doesn't appear that the bug has been resolved though.

A possible workaround (though it'd take a lot of reworking since you're hitting the node limit, so you may be better off just waiting for the bug to get fixed) would be to minimize your type paths. For example, you could take the six paths you have there and do something like:

proc/offset_image(i, state, x_offset = 0, y_offset = 0)
var image/my_image = image(i, state)

my_image.pixel_x = x_offset
my_image.pixel_y = y_offset

return my_image

obj/roar
icon = 'roar.dmi'

New()
overlays.Add(
offset_image(icon, "1", -32, -32),
offset_image(icon, "1", -96, -96),
offset_image(/* etc */)
)

This would help cut down on the number of type paths you're using, since it only appears you're visually offsetting each part of the roar object anyways.