I've updated my every block timed project to be (much) more accurate and include literally every single block. To run the tests in this project yourself, you need the SA Extension and then go to the timing tab in the debugger addon. RTC = Relative Time Cost. This is each block's time cost relative to the cost of the minus operation. E.g Move has an RTC of 7.1 meaning it takes 7.1x longer than the subtraction operation. (Uncertainty is ±15% for math operations and ±20% for other operations) *Note*: if the block has a wait component its RTC is determined by the wait. Certain blocks depend on list/string length, costume size, pen size, pen line length, gpu specs. (touching object and touching colour and colour is touching are not constant! their value depends on sprite size of the object testing/being tested and can actually be <100 if the sprite is a single pixel) **If a block has an RTC of exactly 5000, it means it causes a screen refresh and i've given it an arbitrarily large RTC value. Commands (won't work without the mod): t: test all m: test motion l: test looks c: test control s: test sensing o: test operations v: test variables p: test pen 0: test other (sound, custom blocks, broadcasts) 15/10/24: Have replaced O(n) operations with their linear RTC equations, where n is the length of the list/string that the operation is applied to. 08/05/2026: updated touchingobject:sprite time as the test object was hidden so it reported much faster than it should have been.
クリックで拡大
