ok so i was wondering if anyone could explain or help me edit the config file or tell me what i need to do to make the warp drives jump further than 30 LY , i know it can be done but not sure how to do so . Also can it be done on a dedicated server that has already started ? thanks
Hi @cpspok, assuming you're steam install is generic edit the file... C:\Program Files (x86)\Steam\steamapps\common\Empyrion - Galactic Survival\Content\Configuration\BlocksConfig.ecf ...using a text file editor. You can use notepad.exe for this but something like notepad++ is a better bet since you can make it show you end of line characters and other stuff like that. Search for the string "Name: WarpDrive" and then look for the two range parameters in the data block and change the 50/30 to whatever you want. ItemPerAU: PentaxidCrystal, display: true CostPerAU: 1, display: true CostPerLY: 1, display: true RangeAU: 50, display: true RangeLY: 30, display: true It looks like you could change the drive from running on Pentaxid to using logs by changing the ItemPerAU and modifying the WarpTank entry so the pentaxid tank held logs but your mileage may vary. 8^) I haven't tried it, but I would assume that to do it on a dedicated server would require changing the file at the server and cycling it otherwise a client could create a super engine locally.
In the past I managed to set Drill charge as "ammunition" for the HV and CV laser drills. One charge would give 250 rounds as default and it was very interesting. With the constant updates and overwrites of the ecf files I got tired editing the values. I only change the detector "Discovery factor" now and maybe warp drives range. In general it is easy but updates makes the situation like chasing your tail.
@imlarry425 , Thank you i got that working now , do you know can we change the teleporter range too or no ? thanks
Hi @cpspok, not sure as I haven't tried. The block "TeleporterCV" seems to support a property of "RangeLY" which is set to zero in the Config_Example.ecf file and the CV teleporter can't normally teleport out of a system. I'd suggest futzing with adding that with a larger integer and seeing if it suddenly comes online for out of system. Likewise adding the parameter to the "TeleporterBA" block *may* give you control over that but ultimately the devs decide which parameters can be modified and which are hard coded and figuring out which are which is the goal of the meta-game Empyrion - Parametric Survival. 8^) Earlier I'd suggested modifying BlocksConfig.ecf directly but reading the comment block in Config_Example.ecf it seems this template is intended as a read-through mechanism to overcome the "chasing your tail" problem that @Myrmidon describes above … parameters that you modify in that file overwrite the values in BlocksConfig.ecf without changing a validated known file. Your tweaks go into a file called Config.ecf that take the form of those in Config_Example.ecf and can be pared down to only the blocks and properties you change. You still would potentially need to make changes after updates but the release cycle has slowed down and if you're only messing with common blocks that have settled down as far as their property lists you would (hopefully) not run into too many issues.
You just need to add that parameter to the CV teleporter in blocks config.ecf and set it to what you want.
