0021694: Extended Autobuild: Simplifying planetary defense - DEV Arcen

ID	Project	Category		Date Submitted	Last Update

0021694	AI War 2	Gameplay Idea		Sep 28, 2019 10:08 am	Sep 28, 2019 10:08 am

Reporter	NRSirLimbo	Assigned To
Status	new	Resolution	open
Product Version	0.892 All Ship and Structure Visuals Done!

Summary	0021694: Extended Autobuild: Simplifying planetary defense
Description	Currently there's a lot of clicking involved with defending planets. Placing turrets, placing Forcefields, Tachyon emitters, etc, etc. I think it would be a good idea to simplify and automate this process as much as possible. I talked about this with some guys on Discord and thought at least some of the following could be done. 1.) Improved Auto-Build: Add more sliders for various structures to the Personal Settings -> Automation tab: Watchman/Assault/Sentry Frigates (0-20, one slider per type). This will build N Station-keeping Watchman, Assault and Sentry Frigates the moment the Command Station is completed. Tachyon Emitters (0-5) per point of interest. Every "point of interest" (Command Station, Wormhole, irreplaceable structures like IGCs or GCAs, Mass Drivers and Ion Cannons, etc) will have so many Tachyon Emitters built next to them. If there's not enough to go around for every point of interest priority is Command Station > Wormhole > other stuff, building 1 each, 2 each, 3 each, etc if more than just 1 is set. Forcefields (0-5) per Command Station. This will build N Forcefields next to the Command Station. If possible, build them BEFORE other structures like Factories so they get the most coverage on the Command Station. Forcefields (0-3) per other point of interest. Same general direction as Tachyon Emitters, only with Forcefields and EXCLUDING Command Stations. They already receive Forcefields above. I think it's important to separate Command Stations from this as they are usually the most important structures on the planet. Focused Gravity Generators (0-5) per point of interest. Same as Tachyon Emitters. Tractor Arrays (0-20) per wormhole. This has a few conditions: IF there are hostile planets nearby, scatter the Tractor Arrays near all hostile ones. Ignore wormholes leading to neutral or ally planets. IF there are no hostile but neutral planets, scatter the Tractor Arrays near all the neutral ones. Ignore wormholes leading to ally planets. IF there are only ally planets nearby scatter all Tractor Arrays around all wormholes. 2.) Auto-Update the auto-built structures This means nothing more than "when a Forcefield is built next to a GCA, it is then hacked and thus disappears, the Forcefield is destroyed (and thus, if the autobuild can use another Forcefield elsewhere, redistributed)" When the conditions for something having auto-built change it should build more or destroy other structures. I suggest running the autobuilding calculations of what goes where once per couple of seconds. If the current iteration finds it should build differently than before it'll destroy what needs to be destroyed, redistribute what needs to be redistributed and build what needs to be built. 3.) Include structures from Battlestations/Citadels Rather self-explanatory. If there's more Tractor Arrays, Focused Gravity Generators, etc from a Battlestation or Citadel on the planet then those get distributed too. There probably should be some kind of "Go" signal for this. Maybe replace Battlestation/Citade FRD with a "Fortify" command which allocates the possible structures for local autobuild.
Tags	No tags attached.

Date Modified	Username	Field	Change
Sep 28, 2019 10:08 am	NRSirLimbo	New Issue