Description - We added a config file that allows you to change all relevant parameters for almost all blocks/items/templates/entities used in the game. For example, you can change the damage value of the minigun etc. - The config file can be found here: ...\Steam\steamapps\common\Empyrion - Galactic Survival\Content\Configuration\Config_Example.ecf - To activate it, rename Config_Example.ecf into Config.ecf. > You need to RESTART the game for the changes to take effect! Please note: the config currently cannot be included in a scenario, but needs to be placed in the main folder as described above.
One other thing I believe should be allowed in this game is the ability for modders to add different models for each block type. Allow modders to add different thrusters models, different weapons models and etc.
Hummel , Why was the AllowPlacingAt: line removed from the new config file in the latest update? I was using this line to add different block types to different ships. If this was not removed from the file by mistake then please explained to me why it was removed . I noticed the first FAQ Config file forum was closed which had pictures of what you could do with with the AllowPacingat line and now it's closed and that line is removed from the new file... I don't see how some of us having the ability the add solar panels and generators to other ships by editing a file in our own game is stopping the development of this game.
I concur. I know @Hummel-o-War stated that the removal of this option was related to bug reports/issues players reported when allowing devices to be placed on structures that they normally couldn't be placed on, but this explanation doesn't really hold water for me. Any such issues like that should be summarily dismissed with the response that "right now this device isn't supported on these structures; please reset your config file if you're having problems." Make players own the changes they make to the config file, rather than effectively punishing those players who know what they're doing.
Fiddling around with blocks, blocksizes and mechanics cannot be properly done with a config file only. The experimental version has clearly shown this. The issues were manifold and the amount of bug reports related to this that poured into the QA inboxes indicated that this is adding a very questionable game experience...if any. That’s why it was removed. This needs to be done via a proper modding api.
But why not leave the option in until a proper modding api is added to the game? If I'm remember correctly we are a long ways away from a proper modding API being added to this game. Some of us were aware that not all blocks were going to work correctly but we were still going to use it until something better is added to the game. Those players who can't understand that this config file is just the starting point of adding modding to the game should be told just to wait until the modding api is in. I just think those who understand what the words "Experimental" and "Alpha game" mean should not have their gaming experiences affected by those who don't have no idea what those words mean.
I have to agree Geo. There have been plenty of features in this game that didn't work properly but these features were left in the game and improved over time. I don't see why this one would be any different. I think they should have left this feature in the game until they added a mod api, just to give us something because this feature was a game changer and give us more control over our own game.
i know you want to play around with this, but given the way how blocks are set up and connected to the different types of structures internally, this is a dead end You can believe me or not, but opposed to other not-yet finished features, That’s nothing you just can leave as it is and „improve“ over time by evolving the code base.
I'm looking over this file and I like it except it seems that no one bothered to add in the real values for stack size, so if you enable this, you have to first go into the game and write down all the stack sizes or you'll get only 5 of them. Or am I reading this wrong? The TraderNPCConfig.ecf is another story. I like where this is going.
All right, fair enough; we'll stop bothering you about this. Thanks for patiently explaining your reasoning .
Is there any way we can get this in a standard format, (e.g. JSON or yaml), or at the very least can you share the parser/writer that you're using to read/write the ecf file?
Does the order of the items matter, in this ecf file? Can I, for example, start grouping information together to make it easier to manually parse?
I shall! I'll be starting here. https://empyriononline.com/threads/food-system.455/page-13#post-79843
I have a question. What is the total valid range of ID numbers for both blocks and items? Second question. What is the currently Used, meaning already assigned, range for both? a broad range on the second question will do.
I was searching through the config file to try and change the "Ores per Hour" rates on the Auto Miners, as well as the "Storage Limit", and couldn't find a reference to them, nor to other phrasings I tried. Am I missing something or is that not possible yet?
