In this post (https://www.ecocitycraft.com/forum/threads/redstone-clocks.176289/#post-983209), it says that a redstone clock has to have less than 500 signals per second. I tried making a clock, and the server removed it. So I made it slower, and the server removed it. Repeat about 6 times. My current clock sends one signal every 2.5 seconds, and is still being removed. I tried looking online for what type of clock qualifies for being under x signals per second, but couldn't find any information relating redstone clocks to that form of measurement. So what does "500 signals per second" actually mean? How slow does a clock actually have to be to meet this requirement? Is there a way to measure how many signals per second a clock is?
These are all very good questions and I hope we get some answers on how we can measure to verify we are not breaking server rules. It would also be great if the "powers that be" would video some "acceptable " builds - especially along the lines of sorting systems and "lossless" cobble generators. My "lossless" obsidian went completely to crap after the hopper nerf so I would appreciate if someone has a design they would like to share.
if I understood the criterion correctly (although I cannot guarantee that I did), this value is referring to the number of total signal updates caused by the clock. For example, if I have a line of redstone dust that is ten blocks long and I supply it with a signal, this will update 10 blocks. If my current changes from high to low or from low to high once per second, this results in 10 signals per second. However, I am not sure whether only the block itself counts or also the surrounding blocks; I haven't been able to test that clock prevention mechanism yet. I would, however, assume that this takes surrounding blocks into account because a single block of redstone dust will trigger nearby blocks when powered. Unfortunately, I'm not aware of any method other than calculating it (except for trial and error).
while already mentioning me for redstone clocks: is it actually 500 per second or is it 500 per "config set timeframe"? i took a look at it and you could set signals and a timeframe which the plugin measures in. this would actually help figuring out and explaining to people
