the ordering is based on the timestamp in the database for each piece. what happens behind-the-scenes when a pieces is *reserved* is that it is given the timestamp of *when it expires*. i dont know why i chose to do it this way, but there you have it. so, when a piece is reserved, it gets ordered *later* than pieces that are *finished* after it, but less than two hours after (as that is when it expires). if that makes sense. and if i am even remember this correctly!

needless to say, when a piece is uploaded, the timestamp gets set to that time. thus, when a level is complete, the ordering should be correct.

i suppose i could figure out the math/logic necessary to do the ordering right on the top level, but that wouldnt make it be a quick 5-minute 3-lines-of-code bonus feature then, would it? haha