Unlocking Redstone Creativity with the DaylightSensorExpanded Plugin
Vanilla daylight sensors are among the most useful blocks for automating lights, traps, and farms in Minecraft. They output a redstone signal strength based on the time of day, ranging from 0 at night to 15 under the midday sun. But what if you need a sensor that behaves differently—perhaps one that triggers only at dusk, or outputs an inverted signal for a nighttime-only contraption? That is where the DaylightSensorExpanded plugin steps in, giving server owners and map makers total control over how daylight sensors behave.
What is DaylightSensorExpanded?
DaylightSensorExpanded is a lightweight Bukkit/Spigot plugin that remaps the redstone signal strength of daylight sensors. Instead of being locked into the default 0–15 scale tied to the sun’s position, you can define custom profiles that reassign each possible light level to any value you choose. This opens up a world of possibilities for redstone engineers who want precise, predictable outputs from their sensors.
Originally developed by TheNut, the plugin keeps things simple: no bloated GUIs, no messy configuration files. You create a profile with 16 comma-separated numbers (one for each vanilla signal strength), apply it to existing sensors or to all future placements, and the plugin handles the rest. Whether you run a survival server, a creative build world, or a minigame hub, DaylightSensorExpanded adds a layer of polish to your redstone mechanics.
Key Features at a Glance
- Custom Signal Remapping: Define profiles that map each vanilla daylight sensor output (0–15) to a new signal strength of your choice.
- Profile Management: Create, alter, delete, and list profiles through simple commands, making it easy to experiment with different behaviors.
- Bulk Application: Apply a profile to all sensors within a configurable radius, or set it as the default for every sensor a player places in the future.
- Inverse and Threshold Modes: Build an “inverse” profile (15,14,…,0) for nighttime activation, or a “nightlight” profile (1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0) that turns on a lamp exactly at sunset and off at sunrise.
- Minimal Configuration: The plugin works almost out of the box. The config.yml only stores debug level and profile definitions—no complex settings to tweak.
- Debugging Tools: Optional debug logging helps you verify when a sensor’s output is remapped, useful for testing intricate circuits.
How Profile Remapping Works
Imagine the vanilla daylight sensor as a list of 16 states. At full night, the sensor outputs a signal strength of 0; at dawn, it might output 5; at noon, 15. A profile in DaylightSensorExpanded is simply a new list of 16 numbers that replaces those outputs. For example:
- Inverse profile: 15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0 — the sensor gives maximum power at night and zero at noon.
- Nightlight profile: 1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0 — the sensor outputs a constant signal of 1 during the darker half of the day, then drops to 0 once the sun is high enough, perfect for automatic street lamps.
- Always-on profile: 15,15,15,15,15,15,15,15,15,15,15,15,15,15,15,15 — the sensor acts as a permanent redstone torch, useful for testing or map-specific logic.
Once a profile is applied, the sensor will use the remapped values whenever it updates, and the change is invisible to players—the block still looks and sounds like a normal daylight sensor.
Commands and Permissions
DaylightSensorExpanded includes a set of intuitive commands for managing profiles and sensors. Most of them are intended for debugging or one-time setup; regular players do not need any permissions to benefit from the remapped sensors if an admin has already configured them.
Profile Commands
- /dseprofilecreate <name> <parameters> — Create a new profile with the given 16 values. Permission: daylightsensorexpanded.profile.create
- /dseprofilealter <name> <parameters> — Modify an existing profile; all sensors using that profile update immediately. Permission: daylightsensorexpanded.profile.alter
- /dseprofiledelete <name> — Remove a profile and clear it from all assigned sensors. Permission: daylightsensorexpanded.profile.delete
- /dseprofilelist — Show all defined profiles and their remapping values. Permission: daylightsensorexpanded.profile.list
Sensor Commands
- /dsesensorset <profile name> — The next daylight sensor you right-click will be assigned the chosen profile. Permission: daylightsensorexpanded.sensor.set
- /dsesensorsetall <profile name> — All daylight sensors you place from now on will automatically use this profile. Permission: daylightsensorexpanded.sensor.setall
- /dsesensorclear — Right-click a sensor to remove its extended profile, reverting it to vanilla behavior. Permission: daylightsensorexpanded.sensor.clear
- /dsesensorlist — Lists all sensors that currently have a profile assigned. Permission: daylightsensorexpanded.sensor.list
- /dsesensorconvertall <profile name> [radius] — Converts all daylight sensors within the specified block radius (default 50) to the given profile. Permission: daylightsensorexpanded.sensor.convert.all
Configuration Made Simple
The plugin’s config.yml is refreshingly minimal. Two main sections exist:
- Basic: Contains only DebugLevel (0 for no logs, 1 for remap notifications).
- Profiles: Here you can predefine profiles directly in the file. For instance, adding inverse: 15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0 makes that profile available without using commands.
- Sensors: Stores which world coordinates are linked to which profile; normally left empty and managed by commands.
This structure means you can set up everything from the config file before the server even starts, or build profiles on the fly with commands—both methods work seamlessly.
Getting Started on Your Server
Installing DaylightSensorExpanded follows the standard Bukkit plugin routine: drop the JAR file into your server’s plugins folder and restart. For those who prefer a more streamlined approach, the foxygame.net launcher offers a modern way to manage server mods—you can download and enable this plugin directly from its built-in library without ever touching an FTP client. Once the plugin is loaded, create your first profile with /dseprofilecreate nightlight 1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0, then apply it to a sensor using /dsesensorset nightlight and right-click the block. Immediately, that sensor will follow the new rules, giving you a reliable dusk-to-dawn switch.
Why This Plugin Matters for Redstone Builds
Vanilla daylight sensors force you to work around their fixed curve, often requiring complicated comparator subtraction or pulse extenders to get the exact timing you need. DaylightSensorExpanded removes that friction. You can now design a lighthouse that turns on precisely when the sky darkens to a certain level, a greenhouse roof that opens only during the brightest hours, or an alarm system that triggers at a specific in-game minute. Because profiles can be applied to all future placements, entire districts on a creative server can adopt a uniform lighting logic without players needing to understand the underlying redstone.
The plugin also respects the original block’s behavior—inverted sensors still react to right-clicks to toggle between day and night modes, but now the output curve is yours to define. This compatibility makes it a drop-in enhancement rather than a disruptive overhaul.
Final Thoughts
DaylightSensorExpanded is a perfect example of a plugin that does one thing exceptionally well. It doesn’t add new blocks, clutter your inventory, or demand constant maintenance. Instead, it quietly extends a core redstone component, giving builders and server operators a powerful tool to refine their automated systems. With its straightforward commands, tiny configuration footprint, and support for bulk sensor conversion, it fits into any server environment—from a private survival world to a bustling minigame network. If you have ever wished that daylight sensors were a little smarter, this plugin is the answer.