Beacon Rebalance

The Mod

Do you wish that the most optimal beacon layout wasn't a bunch of boxes? Do you wish that you had to put a little more thought into how your beacons were spaced? Well I have good news for you. No longer will beacons be buddy buddy with each other, in fact, they'll be at odds with one another at every step of the way.

Overload Effect

Machines will no longer be able to be under the effect of more than one beacon, but beacons are made more powerful to compensate. If a machine is under the effect of more than one beacon, it will shut down, and a small red icon will appear, letting you know the machine is overloaded.

Beacon Boost (And More Beacons!)

• The vanilla beacon is given a boost to it's module inventory, and it can now share the effect of eight modules with machines around it, and only uses 350KW.
• The beacon mk2 has a range (32x32 tiles) and module inventory (15 modules) boost, but has a slightly larger footprint (4x4 tiles) and uses 30% more power per module per tile than the vanilla beacon (12MW).
• The beacon mk3 has the same range and footprint as the mk2, but has 33% more module slots (20 modules) for 66% more power per module per tile (20MW).

Config Settings

You can disable the higher tier beacons in the mod settings menu.

Credits

• Thumbnail and some spritework by Sir-Lags-A-Lot.
• The tier two and tier three beacons are based off of the wide area beacons from Space Exploration by Earendel.

Fun Facts

• This mod has no impact on your UPS (unless you place/remove 10000 beacons in the same tick).
• Other mods with beacon overload mechanics will be weird or just not work, so don't run this mod with other mods like that.
• Mods that mess with the vanilla beacon will likely break things. Mods that add beacons might be fine.

Compatibility

• K2 Singularity Beacons will have 15 module slots, just like in K2-SE. Tech tree and recipes are adjusted to fit better in K2.
• FE+ Modules also supported.
• Bob's Modules also supported.

Remote Interfaces

• Add a whitelisted beacon to not count towards beacon overload:

local function on_load_setup() remote.call("wr-beacon-rebalance", "add_whitelisted_beacon", "your-beacon-name-here") end script.on_load(on_load_setup)

• Remove a beacon form the whitelist:

remote.call("wr-beacon-rebalance", "remove_whitelisted_beacon", "your-beacon-name-here")

• Get the list of whitelisted beacons:

local beacon_list = remote.call("wr-beacon-rebalance", "list_of_whitelisted_beacons")

• Recalculate the overload status of all beacons (you will need to do this when modifying the whitelist to affect previously placed beacons and machines):

remote.call("wr-beacon-rebalance", "reset_beacons")