Hey thanks for the reply, glad to hear that 1.5 should be okay for now.

Also, I knew about the rejected run because I used a website to find a list of pending runs like two days ago or yesterday (https://randomidiot13.github.io/queueclient-web/), and then did so again today and noticed that some of the runs I saw before weren't on the list today and they weren't approved, so I figured they were rejected and was just curious as to why (I didn't watch the runs before but I did briefly open the submission page so they were in my history).

The main reason why I was looking at pending runs to begin with is just to see if there was any new runs that I didn't see on YouTube, I don't make a habit of it but I find it interesting to see new runs or ones that haven't been approved yet.

Was looking at recent runs for this game and saw a rejected run where it (the rejection reason) said that the rules may be updated to where runners are asked to play the most recent version of the game. When/if this is added as a rule, will runs played on older versions not be allowed anymore?

Reason I ask is I have a few 1.5 runs which I haven't uploaded yet.

Also on an unrelated note - I've noticed that the newer versions of TDT (should be any compatible after 1.5 - although I haven't checked in a while) show times in milliseconds for the DLC as well (attached image). Could we possibly see DLC levels be added to the leaderboards? I know that previous versions of TDT didn't let the player even play the DLC in the first place but I'm not sure if there was any other reason they are not on the leaderboards.

Hey sorry if this is a stupid question but how can this be .740 ms (instead of .074) if other runs using the v1.5 TDT ending in millisecond times of .xx0 (ex. The Tower Hammer Only 1.03.820) show the 0 in the mission complete screen but this one doesn't? Also runs with times ending in .0xx ms (ex. Insurance Fraud Hammer Only 58.028) don't show zeroes similar to this one.