Remove required id verification for editablemeshes/images

[Judgy_Oreo]

@MRLOSER_HAHAha

Parts aren’t It bad it doesn’t look reallie or something

Here is a 4K example of a ViewporyCanvas image, a library made by boatbomber which existed before EditableImages. It uses parts:

GitHub - boatbomber/ViewportCanvas: A greedy meshed canvas for arbitrary drawings on...

Here is GradientCanvas which existed before even that:

This one uses UIGradients.

GitHub - boatbomber/GradientCanvas: A canvas renderer using greedy gradients to draw...

Not to mention some people just use Frames directly because it’s still possible to display high-resolution images using those:

Toaster! (A render engine for Roblox!)

I’ve recently got the idea of creating a ray tracing render engine for Roblox (or at least just making a project) I wanted to at least show it off before I have to go back to school tomorrow but here are some stats that I’ve created so far and features I want to add! (It’s not very polished because I whipped it up in a day so be prepared!) Toaster should not be used as a replacement for rendering complex scenes, but as an easy way to export simple scenes! Toaster was also heavily insp…

Roblox will not forgo any safety protections by removing the ID-lock. All they’ve done is make games laggier, because if someone wants to display a custom, runtime image, it was already possible for them to do so before EditableImages were implemented. EditableImages are just more performant (but from my experience, if I’m recalling correctly, GradientCanvas is the fastest of the methods I’ve mentioned to generate and statically pretty performant, but it’s been a few years since I’ve used it).