Blades
Blades and their design influence how much damage your shredder can output. Blades have a few factors for being good, mainly spacing and CE. This page has information on many things related to blades.
Blade Design
Blade design is the general design of a shredders blade, the pattern and logic. The principles of blade design are density, efficiency, and area coverage. Following these will produce a better blade.
Modern Blades
This blade design uses the invincibility of compressor blocks and outwards compression setting to make a vertically and horizontally spaced cross blade. This is the best general design of blade for now, preferred for its high area coverage and block efficiency.
There are a few variants, most simply cut down the sides of the blade shape from four to three or two. Two sided blades, flat blades, do not cover as much area as other blades and have less hits per second.
Sinusoid
This blade uses a repeated pattern of angles to create a spinning sinusoid. These are spaced well, but do not use cutters as efficiently.
A mistake people make when using this type of blade is creating a helix, stacking the pattern to make two sinusoids. This uses way too many blocks and can make the blade dense enough to be pingspiked.
Density
Efficiency
Area Coverage
Cutter Rules
Cutter blocks follow a set of rules, both scripted and naturally occouring.
Minimum Distance
Cutters have a minimum distance rule, this prevents redundant cutters and side by side cutters.
Maximum Speed
Cutters have limits to the speed where they can still function. The first cause of this is ping, this is from the serverside and clientside hitbox being more and more offset the higher the speed is. This, combined with serverside damage checks for cutters, makes ping heavily determine the effectiveness of cutters.
The second cause is a speed limit, cutters eventually stop working at thousands of SPS.
Damage per Second
When a cutter deals damage, it deactivates for 0.1 seconds. This prevents cutters from just dealing infinite damage and instantly pingspiking. Demean makes blades have constant hits per second by making the cutters land in the same exact spot while the blade spins (Each frame the blade must rotate in a way that a cutter goes to the same position as the previous cutter.) With 1 motor demean, the blade will spin 45° per tick. The DPS of a blade depends on the shape and demean settings.
Example: a Flat Blade (15 h/s) has half the DPS of a Cross Blade (30 h/s) when using 15π demean.
Pingspiking
When your cutters interact with an excessive amount of blocks, affected by density of blade and target, your ping can spike up with no limit. This causes you to freeze on the server but not your client, making your position stop replicating. This can lead to certain death.
Demean
Demean is a method of boosting the damage of cutters in a blade. This is done through a calculated MotorSpeed that aligns a specific amount of motor rotation with ingame ticks. The exact rotation needed for a blade is calculated through a few steps.
Roblox operates with the roblox.com/docs/physics engine running at a maximum of 60hz (like frames per second) making the optimal fps, FPS ≥ 60. This also increases the value of Optimisation
To find the correct MotorSpeed for a 4 sided blade, this equation is used (2π×60)÷(360÷45). meaning demean is 15π or 47.124.
To find the MotorSpeed for a 3 sided "tri blade", the equation (2π×60)÷(360÷60) is used. The answer, 20π, cannot fit within a singular motor. The MotorSpeed limit is 50, 20π is ~62.832. The fix to this is 2x Demean, which stacks the speed of two motors. This means the correct value for the motors, divided across the 2 motors, is 31.416.
The optimal MotorTorque value for blades, tested over 1000 times with demean, is 0.63.
To have a better effect, spin backwards to make it capable of pulling targets into itself. Forwards will have a reversed effect.
In summary, a cross blade