[eah]

So my friend gaudino wants to use a piston clock as a mechanism to cause a chain reaction on a roller coaster ride type thing. He's concerned on whether it's allowed or not seeing as it's redstone constantly changing state. Though, it doesn't have the purpose to cause lag. The other major concern is that Lm108 and Intelli TPed to the clock while it was active and Lm said something about his client saying that we were flying. Any reason why it would say that? The coords are 1016, 209. I also have a video of it in action if that's necessary.

[alexrybicki]

So my friend gaudino wants to use a piston clock as a mechanism to cause a chain reaction on a roller coaster ride type thing. He's concerned on whether it's allowed or not seeing as it's redstone constantly changing state. Though, it doesn't have the purpose to cause lag. The other major concern is that Lm108 and Intelli TPed to the clock while it was active and Lm said something about his client saying that we were flying. Any reason why it would say that? The coords are 1016, 209. I also have a video of it in action if that's necessary.

TL;DR " redstone constantly changing state. "

that's pretty much all you need to know.

[Prodigy9]

" redstone constantly changing state. "

that's pretty much all you need to know.[/quote]
Yup. Frequent state changes cause lag.

[ImUrDaddy5150]

I was told, so long as the mechanism is not ALWAYS on, it is acceptable. If it is a constant loop that can only be deactivated by breaking it, it is not allowed. However, if the loop is triggered by one thing, does its loop, and shuts back off, it is perfectly acceptable.