Four words:
Redstone
Now
Loads
Chunks
Implications? People could leave CPUs running and not freeze up when they leave.
My opinon? I personally don't see this as something major. We have a very powerful machine running the server (<3 Mort), and other Redstone servers *cough* stym's *cough* are, for the most part, unaffected by this. The reason being that they have a rule to not leave clocks running, and staff having the right to turn clocks off.
ORE solution: I think we should take the same approach as stym's. Why? Bcause the other alternatives are 1. Don't do 1.8. We can't do that because Nick will commit suicide. Or there's 2, have a plugin that freezes clocks. The problem I have with this is how a plugin determines what constitutes as a clock. It is possible that running CPU's may be stopped and random parts locking up and being disabled because of this; these plugins were designed for non-redstone centered servers who wouldn't have these issues. I think this change is a good thing as we are no longer limited in the size of our redstone devices by render distance. Also, intOREnet probably won't work under plugin/repeater freezing conditions.
So we ultimately have 3 options as a server.
1. Stay 1.7.9 (Nick will die)
2. Plugin which freezes clocks (CPUs and intOREnet will die)
3. Rule requesting you switch clocks off and staff have the right to stop clocks. (Nothing dies, but maybe a few minutes of staff time a day.)
As for my source, I cannot find something that confirms this, but I tested with different speed clocks in both single player and the 1.8 test server nick has set up. As stated above, stym's server (1.8.3), redstone clocks do not freeze.
Redstone
Now
Loads
Chunks
Implications? People could leave CPUs running and not freeze up when they leave.
My opinon? I personally don't see this as something major. We have a very powerful machine running the server (<3 Mort), and other Redstone servers *cough* stym's *cough* are, for the most part, unaffected by this. The reason being that they have a rule to not leave clocks running, and staff having the right to turn clocks off.
ORE solution: I think we should take the same approach as stym's. Why? Bcause the other alternatives are 1. Don't do 1.8. We can't do that because Nick will commit suicide. Or there's 2, have a plugin that freezes clocks. The problem I have with this is how a plugin determines what constitutes as a clock. It is possible that running CPU's may be stopped and random parts locking up and being disabled because of this; these plugins were designed for non-redstone centered servers who wouldn't have these issues. I think this change is a good thing as we are no longer limited in the size of our redstone devices by render distance. Also, intOREnet probably won't work under plugin/repeater freezing conditions.
So we ultimately have 3 options as a server.
1. Stay 1.7.9 (Nick will die)
2. Plugin which freezes clocks (CPUs and intOREnet will die)
3. Rule requesting you switch clocks off and staff have the right to stop clocks. (Nothing dies, but maybe a few minutes of staff time a day.)
As for my source, I cannot find something that confirms this, but I tested with different speed clocks in both single player and the 1.8 test server nick has set up. As stated above, stym's server (1.8.3), redstone clocks do not freeze.