ID:273472
 
Are there any disadvantages to using images in situations where one might be tempted to use client.screen (dynamic HUD menus and text, etc. etc.)?

I know that client.screen starts to bog down once you try to do things that are dynamic on it, that's why I want to see if images are better.
It really depends on what kind of effect you're looking for. When using screen objects and screen_loc you know 1,1 is going to be the same no matter where your player goes, but the very nature of /images means they are always "attached" to other atoms so it's a little more difficult to determine where 1,1 is. That's the main drawback of using images. However, if you work out the math, and assuming your player stays fixed at the 'center' of the view, you can create a screen_loc system using images with pixel offsets. Create the images with their loc set to your player, they'll move with your player just as though they were screen objects. Essentially they're overlays that only your player can see, but you can access them directly using client.images.

/images are also just stripped down atoms so you might find them to be a little more efficient, while still retaining the important basics(pixel offsets, loc, icon_state etc.). You can also define new vars under /image, but that'll start to add some overhead, but it still gives you flexibility.