Jump to content
sale $39.99  $31.99

1 Screenshot

  • 7,411
  • 660
  • 79.88 kB

About LightsOn

This plugin provides a way to automate light control and toggle lights from the server console and via chat command using no fuel. There is a config to allow you to pick and choose what is toggle. There is an also options to automate turning lights on and on at night.

Exciting New Feature: Now with optional instant cooking, fuel can be optional, cook anything in anything, and no burnt food.  New configuration for instant cooking, optional fuel and cook anything. Simple toggle on, and it will instantly cook the contents. The most over-powered cooking in Rust. If you use this feature, you do not need to set Protection to true, as it will not be needed. Cooking includes all "oven" functions (food, ore, and crude oil).

New Feature: Players can toggle on/off any light that is not electric based if it is empty. Useful for cave bases and emergency lighting. Note: if the item is set to ignore, you can't do this.  Note: the timed process will turn it back on/off next time it runs. Quick Hack for players to note: placing any items in "oven" with protections set to true will prevent the light source from being toggled by the plugin.  So you could turn on/off an oven and then place a single stone (for example) and it will stay in that state. Note Ovens include: furnaces, cauldrons, BBQ, camp fire, fire place, fire pits, oil refineries, and hobo barrels. Operators please note the protection flag now has two uses, hopefully this is acceptable.

A big thank you to Wulf and k1lly0u for their awesome lights plugins. If you need fine-grained control of lights, they are both superior options. If you want fuel use for lighting, then AutoFuel is an awesome choice. My understanding of lights came directly from reading these plugins, and they inspired me to make this low load and slightly more inclusive of entities plugin. If it generates lights or effects, I tried to include it. I include a lot of non-light devices (Water Pumps, Fog Machine, Snow Machine, Spooky Speakers, Strobe Lights) to allow operators to have fun with players.

I am open to suggestions to improve this plugin as long as it does not hurt performance.  I use it on my PVE server, and it has a lot of lights.  By using "always on" the load of the lights is light on the server.  It can still be brutal on the client due to the graphics load.  Night Toggle (turning the lights on and off, is reasonably efficient but can spike server load).  It is nice for role playing, but use "always on" if you want the best server side performance.

This plugins is not designed to support user level permissions.  The only permission is for admin access.  This is to minimize the overhead for efficient processing.  There are alternatives with permissions if you want it as a VIP perk. Please do not ask for player permissions, it will not be added.


Permissions

This plugin uses Oxide's permission system. To assign a permission, use oxide.grant <user or group> <name or steam id> <permission>. To remove a permission, use oxide.revoke <user or group> <name or steam id> <permission>.

lightson.allowed

Granting that to a group or player allows them to toggle the lights for the entire server (Admin level). For example:

oxide.grant group admin lightson.allowed


Console Commands

lights on -- Turn on specified lights (either all for all entities or a specific name)

lights off -- Turn off specified lights (either all for all entities or a specific name)

lights check -- check the lights after reloading the config to allow changes without reload (either all for all entities or a specific name)

There is a second parameter where you can specify a portion of the light source short name to force all of them to the on or off state ignoring the config.

Example:

lights on fireplace -- Turn on all fireplaces regardless of the config settings


Chat Commands

/lights on -- Turn on specified lights (either all for all entities or a specific name)

/lights off -- Turn off specified lights (either all for all entities or a specific name)

/lights check -- check the lights after reloading the config to allow changes without reload (either all for all entities or a specific name)

There is a second parameter where you can specify a portion of the light source short name to force all of them to the on or off state ignoring the config.

Example:

/lights check candle -- Turn on all candles if the the flag is appropriate for the time of day


Configuration

The settings and options for this plugin can be configured in the LightsOn.json file under the oxide/config directory. The use of a JSON editor or validation site such as jsonlint.com is recommended to avoid formatting issues and syntax errors.

Console Output set to false will stop message (other than errors and night toggles) from logging in the console.

These can be set  in the json which lets you determine what is turned off and on automatically:

  • BBQs
  • BoomBoxes
  • Campfires
  • Candles
  • Cauldrons
  • Ceiling Lights
  • CCTVs
  • Deluxe Christmas Lights
  • Elevators
  • Fire Pits
  • Fireplaces
  • Flasher Lights
  • Fluid Splitters
  • Fog Machines
  • Furnaces
  • Hobo Barrels
  • Heaters
  • Igniters
  • Industrial Lights (Lamps)
  • Lanterns (which include Chinese Lanterns,  Tuna Can Lamps, Lanterns, and Jack'O Lanterns)
  • Mixing Tables
  • Neon Signs
  • Reactive Targets
  • Refineries
  • RF Broadcasters
  • RF Receivers
  • Searchlights
  • Simple Lights
  • Siren Lights
  • Smart Alarm
  • Smart Switch
  • Snow Machine
  • Spooky Speakers
  • Storage Alarms
  • Strobe Lights
  • Telephones
  • Vehicle Lifts
  • Water Pumps
  • Water Purifiers
  • Electric Water Purifiers

Valid values are a - always on, d - on during the day only, n - on during the night only, i - do not process this entity.

To avoid automatically turning off active processing, there are protection you can set to true for the following:

  • BBQs
  • Campfires
  • Cauldrons
  • Fire Pits
  • Fireplaces
  • Furnaces
  • Hobo Barrels
  • Mixing Tables
  • Refineries

If there is anything inside these (including fuel) they will not have their state changed.  You can still force them off by name. For example:

/lights off furnace

Additional control parameters:

  • Console Output
  • Check Frequency (10-600)
  • Dusk Time (0-24)
  • Dawn Time (0-24)
  • Use Zone Manager Plugin

Notes

If the server lights are on (either via "always on" of the night toggle is on) and you place a light source you have selected to be on, it is turned on when placed. This avoids having to periodically turn the lights on to catch newly placed lights.

This alters fuel requirements to zero through the methods it is using to toggle the lights, since you are removing player agency around fuel usage. Note: Furnaces etc. turned on will not process their contents, just look active and produce light. You are giving free light, but not free processing (unless you activate InstaCook). Simply turn them off and back on for normal processing. It is important to let players know this, as they may initially be confused or frustrated.

Since this plugin is toggling animation flag states (where ever possible), it allows things like hobo barrels to light up with no fuel in them. It does some "hacky" flag settings to avoid needing fuel in other light sources. It is not elegant, but efficient.

If you want free fuel NoFuelRequirements or AutoFuel are good solutions, this plugin tries to avoid altering the fuel level in entities other than hats and jack o lanterns. I only add fuel where the toggle of animation state trick is not working in that use case.  It is best to set any item being processed by another plugin to ignore to avoid conflicts.

Hats and Jack O Lanterns usually require at least one fuel in them to allow players to toggle them. Toggling Lanterns (which includes Jack O Lanterns) with the commands does not need fuel.

If you are using the commands to turning a light source on, and it is already on, it is not altered. If you are turning a light source off with the commands, and it is already off, it is not altered. Toggling lights on should not mess up processing content, as their state is not changed. It will mess up processing if you toggle off and then back on for an entity that processes things (grills, furnaces, refineries, camp fires, firepits and fireplaces). Since I added the Night Toggle feature, I also added Protection for light sources that also process contents. I would recommend you leave these to true. Doing so will not turn these off when dawn happens. That is, to avoid annoying players by interrupting their processing. The side effect is they will always appear on if they set to automatically turn on in the configuration.

Choose carefully what you will configure to be controlled if you plan to use the off command or Night Toggle. If you are going to use the off command I recommend you do not include Furnaces, Grills or Refineries as it will stop processing if they are in legitimate use. If folks tend to cook in campfires, firepits and fireplaces, you may want to skip them as well if you plan to use the off command. Honest, I normally just turn items not normally used to do processing on and leave them on as it has the smallest server load and will not annoy players. It is important to consider consequences of turning things off or toggling them on and off.

Check Frequency controls how often the plugin checks for night or to toggle the lights in seconds. It has a relatively small load unless there are lights to process. If you want the lights on at a very precise time, then a lower number (more frequent check) will help increase the accuracy.

I like to light up all the hobo barrels on the map to give a nice effect, that is why I originally wrote this. It should cover all light sources, please let me know if any are missing. It will be interesting when electricity comes in, I will do my best to ensure this keeps functioning.

The light source name tries to match so "a" would match all light sources with "a" in their name. Use "all" to force all lights server wide regardless of configuration setting.

Support for Zone manager via adding zones to \oxide\data\LightsOn-Zones.json

Example:  

["supermarket_1","supermarket_2","gas_station_1","miningoutpost_1","miningoutpost_2","supermarket_3","gas_station_2","gas_station_3","miningoutpost_3","sphere_tank","launch_site"]

LightsOn.json

  • Like 5
  • Love 2

Mals's Collection

User Feedback

317.5k

Downloads

Total number of downloads.

1.6k

Customers

Total customers served.

20.5k

Files Sold

Total number of files sold.

319.6k

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.