I agree with you there. The CR developers need to provide info on how fast the CR actually is. Millz for example states his CR's run well (or even perfect) with only 10tps. TuanHA stated in the past that his CR's are "too fast for framelock"; that might have changed though. Most developers don't specify this or just don't know, so how are we supposed to know?I think it's entirely up on the routine creator to advise botbases, framelocks and TPS. Saying that TPS doesn't really matter is partially true ofcourse. It's a bit more technical then just saying "it doesnt matter". The bot and routine tick a certain miliseconds, if you divide 1 second by the miliseconds the bot ticks (I use 15ms as example) you get 1000/15= 66 Ticks per second possible. Thus this routine can handle 66 TPS. If the routine runs at 100ms, you can set the value to 60 TPS, but only 10 ticks fit within that second and that's why on some routines its useless.
It's the developer of the routine who should provide proper information. And if they are unsure on how framelock, ticks per second and more work they can contact me and I don't mind explaining them.

Less trial and error; more info and how-to's will make for less postings.