What if we could have a setting to cap the framerate at a certain number to make our timers more precise?
it could also save along with the map so others can enjoy your perfect timers
And as for the compatibility issue that would arise from a map format addition, if TPT doesn't see the framerate cap variable in a map, or if the value is Zero, it will not cap the framerate at all and will load the map normally
As long as your framerate is at the cap, your timers should be able to function at near-perfect intervals as it would take the same frames per second for a spark to get from point A to point B
Simon I think he means like choose your frame rate (if possible) so that it doesn't shift and make a creation or whatever go slower/faster than intended.
Simon and were in the source code is that limit set? if we could set it to 1 fps and compile we could do some debugging in electrical systems. (framerate is not saved to the server right?)