DaylightSensorExpanded: Custom Daylight Sensor Profiles
Every Minecraft engineer knows the frustration. You place a daylight sensor, wire it up, and hope the timing works out. But the vanilla sensor follows a rigid curve: maximum power at noon, zero at night, and a gradual slide in between. That is fine for a simple lamp, but what if you need a farm to activate only at high noon? Or streetlights to flicker on exactly at dusk? The default sensor simply cannot do that. Enter DaylightSensorExpanded: Custom Daylight Sensor Profiles — a plugin that turns a one-trick block into a fully programmable lighting controller.
What Makes This Plugin Different?
Instead of forcing you to build complex redstone ladders or inverters, this server-side tool for Bukkit and Spigot lets you redefine the relationship between time and signal strength. You create a profile — a simple list of 16 numbers, each from 0 to 15 — and assign it to any sensor. Each number corresponds to a specific tick segment within the Minecraft day. The result is complete freedom: invert the signal, keep a constant output for hours, or design a completely custom curve that fits your build.
Think about the possibilities. A standard sensor at noon outputs 15. At night, it drops to 0. With an inverse profile like 15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0, the logic flips: daytime becomes silent, and nighttime delivers full power. For a streetlight, a profile such as 1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0 keeps lamps burning through the night and kills them at dawn. No extra repeaters, no bulky comparator chains — just a clean configuration.
Core Features at a Glance
The plugin is packed with practical tools for server admins and redstone enthusiasts alike:
- Create, edit, and delete custom remapping profiles with ease.
- Apply a profile to a specific sensor with a single click.
- Set a default profile so every newly placed sensor adopts it automatically.
- Convert all sensors within a radius (default 50 blocks) to a chosen profile.
- List every active extended sensor and its assigned profile for quick audits.
Permission nodes, all prefixed with daylightsensorexpanded., let you decide who can tweak sensors and who can only use the pre-built setups. This granular control is perfect for multiplayer servers where you want to avoid accidental misconfiguration.
Commands and Permissions
While the config file handles most heavy lifting, the command set makes live adjustments painless. Here are the essential ones:
/dseprofilecreate <name> <values>— build a new profile./dseprofilealter <name> <values>— modify an existing profile; updates all linked sensors instantly./dseprofiledelete <name>— remove a profile and reset its sensors./dsesensorset <profile>— assign a profile to the next sensor you click./dsesensorsetall <profile>— make all future sensors use this profile by default./dsesensorconvertall <profile> [radius]— mass-convert sensors in an area./dsesensorlist— display every extended sensor on the server.
Each command maps to a dedicated permission, so moderators can get limited access while players stay in read-only mode.
Configuration Made Simple
The developers kept the config.yml refreshingly minimal. Two main sections handle everything. The DebugLevel option (0 or 1) toggles logging for each signal remap — invaluable when debugging complex circuits. The Profiles section stores your named sequences, while Sensors tracks which block uses which profile. A sample config looks like this:
Basic:
DebugLevel: 0
Profiles:
inverse: 15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0
nightlight: 1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0
Sensors: {}
After editing, a simple reload applies the changes. No restart required for most updates.
Practical Applications for Your World
The flexibility opens up dozens of automation scenarios. Here are a few favorites:
- Smart street lighting: Lamps turn on precisely at sunset and off at sunrise, with no flicker during twilight.
- Automated farms: Harvest mechanisms activate only during peak growth hours, saving resources and reducing lag.
- Mob traps: Piston doors or dispensers trigger strictly at night when hostile mobs spawn.
- Scheduled security systems: Alarms activate on a timer, even when no players are nearby.
Because you can apply a profile to every sensor in a radius, scaling these systems takes seconds, not hours.
Installation and Compatibility
Getting started is straightforward. The plugin runs on Bukkit and Spigot servers, with support for recent Minecraft versions. To download DaylightSensorExpanded: Custom Daylight Sensor Profiles, grab the jar from a trusted repository and drop it into your plugins folder. For a step-by-step how to install guide, the standard process applies: stop the server, place the file, start it again, and verify the plugin loads in the console. If you are using a launcher that aggregates mods and plugins, you can often manage everything from a single menu, which is handy when testing client-side mods alongside server plugins like this one.
For players who want DaylightSensorExpanded: Custom Daylight Sensor Profiles for Minecraft without manual file hunting, a launcher can simplify the process significantly. It lets you browse, install, and update plugins directly, keeping your setup organized and ready to play.
Final Thoughts
DaylightSensorExpanded: Custom Daylight Sensor Profiles is a small plugin with a big impact. It removes the limitations of the vanilla sensor and hands you a programmable controller for any light-based redstone logic. The profile system is intuitive enough for beginners, while the command set and permissions offer depth for experienced server admins. If you have ever wished your redstone builds could react to time with precision, this tool is worth a try. Your farms, lights, and traps will thank you.