ended up adding one more number after the one sets the mode, to describe a depth level, which is just 1 higher than the highest in that list. so detection for looping/chaining loop etc lists, is just if a gap appears between 1 and whatever the highest number is then theres somethin not right. else you just redo running thru them all equal to the highest depth.
probably gonna add a -f to force it to do it now, since had the -a(after) option forever, but with the newer scheduled mode, in case they have a media player choice that doesnt have a press q to quit instantly like mpv
edits: stopped bein lazy and figured out the timer stuff so now it says per list if you run one, or the comp all per list, and a total time, in seconds.ms, minutes.seconds.ms if its over a 59 seconds
edits:
isnt accurate if the total time is below like .1 second elapsed, but its mainly for the total elapsed time so dunno if i care about that one XD
havent looked to see whats in my kernel on arch to see what timers are available/what speeds but looks like still normally only like .001 is the faster(ist maybe) option, but at a speed of ~10000 a second even for longer lists where there is order of magnitude more data to scan past to get to the correct entries, not sure how i would measure the speed to tell, but shorter ones below 10 obviously would be shorter than .001 s, bein its like .0001 to place even for really long lists, possibly even faster depending on list, maybe like 50-250 or something could be within that first ms even on my slow laptop
mostly just for fun/if you have very large data sets/lists maybe be useful in a verbose output, if one used to take longer but now its really short maybe it got edited incorrectly or something to make it smaller idk