I imagine , with no capacity at the moment to properly research this , that you can query the alpha value of each pixel and destroy the object if they all return 0 or the sum of them don ' t meet a threshold , e . g . if you have floating pixels you don ' t want to prevent it from being destroyed . If I remember rightly though , querying the RGBA value of a surface pixel can be expensive so you may need to stagger the checks over a few frames e . g . just check one row a frame and keep track of the results , rather than query every single pixel in the surface . obviously you ' d only need to check the pixels at all if the surface has changed in any way <| sep |> There isn ' t . The only possible outlier would be shitty mech clones that develop stuck button issues , but if you ' re building within battery limits the most that ' ll happen is a hot foggy pocket that you ' ll be dropping to the ground , assuming you ' ve built in accordance to the limits of your battery .