The main 2 problems I (and many other people here) have are the inability to detect only certain frequencies and the responsiveness of the sensor.
To solve the first issue you could make it take input by a comparator that would select the frequency you want.
To solve the second issue you could make it create a much shorter pulse every time the detection reaches the sensor and make it able to have more detections flying to it at once. This way for example the sensor could constantly be giving an output while a player is walking around. This will lead to more lag that could be circumvented by the selectable frequencies suggestion. A 15 block detection radius would also be very much apreciated!
I want to also warn you that your usual solutions for minimising lag restrict the players in a way that causes them to create more lag. For example the piston limit forces players to move way more blocks at the same time due to the extra pistons and slime blocks necessary to achieve the same task that could be done with a higher push limit.
So if you are trying to limit the abilities of the skulk sensor to improve performance you may end up forcing people to create more lag by using more sensors or just make the block mostly useless especially for singleplayer worlds.
Please sign in to leave a comment.
0 Comments