-> The interesting & easy tweaks to make are in sl-defines.lua
-> The interesting behaviors are mostly in control-gestalt.luaIf a turret is being range-boosted by a searchlight when this mod is uninstalled, it may be lost when the save is reloaded.
To avoid the risk of random turrets disappearing:
This will destroy all searchlights and hidden entities used by this mod, and prevent the loss of other turrets.
New coop-multiplayer scenario map to challenge you and your friends
Searchlights automatically scan their territory for foes
Searchlights may boost the range of neighboring turrets and direct them to snipe spotted foes
Custom animated graphics, plus remnants, custom light effects, and high-res integration
Custom audio effects for the searchlight, its light effect, and when spotting a foe
Optimized to allow running several thousand searchlights
Searchlights can be connected to the circuit network
Mod settings
In the event that another mod's turrets are incompatible with SearchlightAssault trying to boost their range, the block list can be used to prevent issues.
It is advised to add incompatible turrets to the blocklist before placing any searchlights nearby.
To add one or more turrets to the block list:
Note that changes made in the mod settings menu will be lost unless you save your game.
Some turrets may not be boostable to begin with, and are automatically ignored by this mod.
Hero Turrets mod compatibility: Mod Settings -> Startup -> Hero Turrets -> Create in updates: True
Potential Mod Incompatibility: Any mod which uses highly scripted turrets that interact with their own hidden entities, or turrets that are populated into a global table.
Workarounds: Add turrets from incompatible mods into the turret-boost block list. (See above section)
Remote Interface: Other mods may add or remove their own turrets from the blocklist using the remote interface. Results of these calls are noted in factorio-current.log. Example of use:
Your mod's control.lua:
remote.call("sl_blocklist", "add", "laser-turret")
remote.call("sl_blocklist", "remove", "laser-turret")
remote.call("sl_blocklist", "add", "lazur_turett")
factorio-current.log:
Script @__SearchlightAssault__/control-blocklist.lua:30: Searchlight Assault: Blocking laser-turret from searchlight interaction.
Script @__SearchlightAssault__/control-blocklist.lua:40: Searchlight Assault: Unblocking laser-turret; interaction now allowed.
Script @__SearchlightAssault__/control-blocklist.lua:26: Searchlight Assault: Turret prototype name specified by remote call not found: lazur_turettFor more information: https://lua-api.factorio.com/latest/LuaRemote.html
You are welcome to contact me via email: bolderbrush10@gmail.com
If you have any feedback or footage featuring my mod, please share with me! I would love to know what people think.
[Mitigated] It's possible to 'fake out' the turtle near the edge of the searchlight range and desync the searchlight from attacking its turtle or make the turtle "lock up"
[Cheat Mode] Mass-deconstructing alarm-mode searchlights and boosted turrets at the same exact time causes the searchlights to re-boost turrets as they die, causing boosted versions of that turret to be spawned in and avoid being mass-deconstructed
[Feature?] Spidertrons can only distract searchlights, not be targeted by them
Boosted turrets have trouble shooting at something if it has its force set every tick
Two searchlights have trouble targeting each other at the same time (Probably because of raise/clearAlarm() "destroying" their targets and creating a new entity of the alarm / base type)
A gestalt is an aggregation of things which together are more capable than by the sum of their individual parts.
In this mod, a 'gestalt' refers to the collection of a Searchlight, the list of turrets it may range-boost, and several hidden entities which each are essential to making features work.
The term "Turtle" is a reference to the rendering concept of some old, beginner-friendly programming languages (such as 'Logo', from 1960's).
The idea is to imagine a turtle with a marker held in its tail, and wherever this turtle goes, it leaves behind a line. You'd write a program specifiying distances & directions for the turtle to follow. And thus, you could control the turtle to control rendering a picture.
And in this mod, our turtle, instead of drawing a line, will help render a searchlight effect.
I enjoyed the challenge of making this mod with as few changes to the base game as possible, but this codebase would be drastically smaller if these issues weren't in place:
sl-defines.lua - miscellaneous static definitions such as turret range, colors, etc. Shared between most files.
control.lua - handles event registrations & filtering, calls behavior from the control-*.lua files
control-gestalt.lua - controls foe seeking behavior, range-boosting behavior, etc. Interacts with other control-* files
control-searchlight.lua - behaviors for the searchlight itself when created / alarms are raised, etc
control-tunion.lua - behaviors for range-boosting turrets
control-turtle.lua - behaviors for the dummy-entity that the searchlight "attacks" to render a light at surface locations
control-forces.lua - sets up the forces assigned to hidden entities and handles force migrations
control-gui.lua - Graphical User Interface controls, for displaying windows allowing control of searchlights to players
control-items.lua - converts items in blueprints to the base versions of boosted turrets
control-blocklist.lua - controls for filtering incompatible turrets per mod settings and remote interfaces
control-common.lua - data structures to be shared across control-* files and functions for maintaining them
sl-relation.lua - a simple matrix to help track relations between turrets, foes, and searchlights
sl-render.lua - displays the searchlight's search area
sl-util.lua - math functions, copying functions, and other miscellaneous functions
info.json - information to display in the mod portal webpage, plus version / mod dependency information
settings.lua - prototypes for the settings that can be configured for this mod
data.lua - lists which files the mod manager should read to build & modify prototypes
data-updates.lua - reads what turrets OTHER MODS have put into the game
and generates extended-range versions of their prototypes
(this allows a searchlight to "boost" any given turret's range).
If another mod creates its own turrets in its own data-updates.lua or data-final-fixes.lua files,
then searchlights are probably not going to be able to boost that mod's turrets.
data-final-fixes.lua - Double checks that any boosted turrets have the correct health,
since other mods have been discovered to change vanilla turrets in data-updates.
Generates extended-range versions of ammo prototypes, since other mods have
been observed modifying vanilla ammo in data-updates.
Also declares our own entities here, so other mods will stop messing with them.
Prototypes contain the definitions for a unit's graphics, animations, and stats (such as max health, range, and damage)
prototypes/sl-entities.lua - prototypes for the searchlight, hidden entities such as the turtle, etc
prototypes/sl-datastage-entities.lua - prototypes for entites that rely on basegame entity data
prototypes/sl-graphics.lua - pictures, lights, spirites, and animations
prototypes/sl-gui.lua - defines GUI styles for later use in control-gui.lua
prototypes/sl-shortcuts.lua - defines / modifies in game hotkeys (used to open the searchlight GUI)
prototypes/sl-signals.lua - virtual signals for refined control over searchlights
prototypes/sl-techItemRecipe.lua - details for how to research and craft a searchlight
compatability/* - Mod-specific compatability fixes & features
compatability/sl-compatability.lua - Collates various mod-specific calls into a handful of functions
locale/* - Translations of the various in-game strings displayed to the player
menu-simulations/* - Contains small demos that run during the game's main menu, on a random rotation
scenarios/* - The latest revision of the Prison Break game mode. Of note are the files _slsilobreak.py and _slprisonbreak.py, which contain scenario-specific logic, events, and win conditions.
What if we just manually call render for a searchlight effect and move & search around it every tick ourselves?
This is extremely performance intensive, noticably costing fps after only a few dozen searchlights. It's vastly more efficient to have the game create an entity, shoot at it, and let the engine do pathfinding and rendering calls for us. (Even with all the rigmarole associated with maintaining that entity...) Plus, we get to have the searchlight effect 'rotate' around the turret at no extra cost.
What if we used TargetMasks to protect turtles from being attacked, instead of giving them their own force?
Unfortunately, capsule robots and other non-turret entities don't seem to respect the TargetMasks.
What if we required players to connect their light with wire to the turrets they want it to affect? Connect searchlights to a beacon to have the light auto-boost in a radius? Have another version that takes a beacon as an ingredient to auto-boost? Have a version that takes a radar / rocket control unit for a really big boost?
Imagine what the wube devs would do: There'd just be ONE version of a turret, and it'd be straightforward to use.
How can we indicate the boostable radius / decorate terrain of boostable region?
No longer necessary, decided to just boost adjacent turrets. It was very painful to try to figure out a way to get turret range and radius_visualization to coexist.
[DONE] energy_glow_animation on turrets flickers badly Dev responded and agreed to solve: https://forums.factorio.com/viewtopic.php?f=7&t=100260&p=554307#p554307
OnPowerLost/Restored event mod interface request (So we don't have to check power manually in onTick)
Write up how non-turrets just totally ignore trigger_type_mask... And how it's seemingly-impossible to set up a blocklist for an entity that you don't want even-just-turrets to attack.
'on_save' event, or a way in general to make sure that uninstalling our mod will give people back their original turrets.
Report prefer_straight_paths = true as bug? Seems to do the opposite of what it says
When editing an already-saved blueprint's contents by selecting a new area, the on_player_setup_blueprint event is fired, but the replacement contents don't show up in the player's blueprint or cursor blueprint stack (cursor_stack.is_blueprint is true, but is_blueprint_setup() is false, get_blueprint_entities() returns nothing, and get_blueprint_entity_count() is zero) Where it does show up is in the blueprint from the player's inventory, which means you have to iterate through the whole inventory and hope you can find the right blueprint, AND also deal with the problem of the blueprint being nested in a book... Related? https://forums.factorio.com/viewtopic.php?t=99845
Create more main-menu simulations, update existing sim. (Unfortunately, the mod's control.lua doesn't work in main-menu simulations, so we have to work around that...)
Retune prisonbreak scenario difficulty
Victory screen prints out what difficulty you were on (with a percentage of playtime since reaching that difficulty) and hint how you can increase the difficulty level
Tips & Tricks integration
Handle cloning entities / brush cloning map areas
Searchlight brightness decreases during brownout
Searchlight color controlled by circuit signals
Mod compatability setting feature: \nWildcard matching possible with asterisk *
Look more into teleporting or somehow... hiding the entities we're replacing. It'd be nice to not have to spawn / destroy turrets all the time just because we're boosting them. Initial research doesn't look promising.
Break apart into a 'boostable turrets' mod. Let people use mod settings to control what level the boosting is. How to handle recipes? Just a beacon to all the regular recipes, enable it with a unique range-boosting technology? Or just make a stand-alone version of the mod and a non-standalone version?
Re-render everything with some kind of smudge / blur post-processing effect so it can blend in better with the base game
Shadow layer cleanup: I think I need to go into photoshop or blender and rig it so that any pixels from the base layer exclude pixels from the shadow layer