Can we PLEASE get something better than "to back" and "to front" in the map layer???

I'll try to explain my conundrum. For years, making maps in roll20 has been a chore for one simple reason that to me, a simpleton when it comes to coding/programming/yadayada, SHOULD be an easy fix. Items can ONLY be be sent to the furthest back (behind the background, which means I cant acces it unless I move around the background) or to the absolute front. WTrying to fix it just one step over others is an absolute nightmare  when you have several modular parts leyered over and under one another. PLEASE PLEASE PLEASE give us the option to just make items move one step up or down, not ALL the way. 

Hi Coral! I agree that this is frustrating. If you want to put it into the suggestion forum, I'll add my vote to it.

By the way,  Just for some technical terminology,  The layer-stack is usually called the Z-Order or the index  and I agree it would be very powerful if we had control over the full order of that like in Photoshop 

Another tab by the Chat, Journal, Collection tabs, etc. Every token in depth order on the map... draggable up/down by a handle, the same way you can drag items in the journal. Then you can visually see their depth. Would also be SUPER handy to have buttons for each: __________ __________ [ Select ] [ Unselect ] ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ̅ ...or just a single, togglable button that indicates "Selected" state... though that may be difficult since every player's interface would have a different set of selected tokens. Then you wouldn't have to move tokens that are on top of the token you want... you could just add the buried token to your selected group by clicking the correct button!

"Paste in Front" or "Paste in Back" of the selected object would also be nice. Most graphic editors can do this.

I use map tiles to build some of my maps and yes this is a problem. Also I would like to see a way to turn a tiled map into a single image so that it will load quicker.

That would probably have the opposite result. A common bit of advice often given here to improve the loading speed of of large maps is to split them up into several smaller images. Hultz (Keeper of Secrets) said: I use map tiles to build some of my maps and yes this is a problem. Also I would like to see a way to turn a tiled map into a single image so that it will load quicker.

Rick A. said: That would probably have the opposite result. A common bit of advice often given here to improve the loading speed of of large maps is to split them up into several smaller images. Hultz (Keeper of Secrets) said: I use map tiles to build some of my maps and yes this is a problem. Also I would like to see a way to turn a tiled map into a single image so that it will load quicker. That's true... but consider a "map layout" builder. Your map can be broken down into tiles (or conversely, built *from* tiles that are already broken down). If you had a "map layout" object prebuilt, you could drag that to a new map layer, and Roll20 would read the properties of the layout object to know what image tiles to retrieve and, based on the size of the "map layout" object, how large those component tiles needed to be sized.

It should be possible to construct a mod script to move forward or move backward. The Align script can modify the stacking order within a selected group of graphics.

ooh... with a handout interface to represent the z-order. We wouldn't get the draggable items, but you could have a "+" button to raise an object in the order, a "-" button to drop it in the order, and maybe an "arm" button to do multilevel moves... ie... you want to move the object at layer 29 (out of 32) to be just in front of the object in slot 17. click the "arm" button on layer 29 the rest of the +/- buttons for each level grey out, and you get "-----------" buttons between the layers as a "drop the armed layer here" you click on the button just in front of 17 (between 17 and 16), the layer moves there. That would be slick.

Thinking back, I think that Align does this by methodical and systematic "to front" operations, rather than editing the z-order specifically.