2x2 piston door, unless spammed and overcomplicated, no Stone gen, maybe if it's huge fast and well, you get the idea
Limit has been increased from 1500/10 secs to 1750/10 secs, this is basically 175 events per second rather than 150. This may help some users that were limited.
For those that could use a tip about redstone and the limiter: I ran a few tests on my island, and it turns out that solid blocks powered by redstone dust and repeaters (and possibly anything that conducts through solid blocks) do not count toward the redstone firing limit, which is promising. It would be pleasant to have a detailed list of blocks and redstone actions/firings that do count toward the limit.
Making this comment here as it relates but may add it to suggestions later. Drogo has found that after restart his redstone machines need rebooting as they have hit the limit. This usually only happens after restart and the lag that inherently comes with it. During this time, Drogo often sees his machines freeze and then a mad flashing of redstone which might be causing the limiter to kick in. Drogo is not wanting the redstone count increased, but if it worked on 3500 pulses per 20 seconds, rather than 1750 per 10 seconds, then redstone machines would be less effected by any catchup after lag spikes while still being limited to the same overall rate currently set. Does anyone else have to go resetting redstone after restarts?
Is the limiter still set to 1750 per 10 seconds? I have a fast pulse running but there are only 12 redstone pulses in a single chunk and it is randomly being limited. This would mean that it is firing 1750/12/10 = 14.6 times per second. It's not. It is firing about 5 times per second however after periods of lag it does seem to run faster. I just reduced this to only 10 pulses (7 redstone, one observer and two droppers) and it's still being limited!! That means that after periods of lag, it is running at 17.5 ticks per second!!
It seems that my slot machine just really doesn't fit on the server now with the redstone limiter in place. And Drogo might be right. Waiting for the 60 second timer doesn't help, as the machine is shared between multiple chunks; the redstone just goes out of sync and breaks itself. Redstone dust alone is known to be the biggest cause of lag in any redstone contraption, so perhaps it's more beneficial to limit redstone dust alone (and maybe a couple other things if practical), instead of limiting the much lag-friendlier redstone components.
