How do I ban a block from a scenario?

I'm trying to forbid the crafting of artillery turrets in a scenario, so that player can't create them but can use them if they salvage one from a poi

Can't find how. Are there even creating restrictions in MP?

 

You can use a custom config file to alter many things with items, blocks, weapons, crafting recipes, etc. Sadly such a config file can't be automatically included and activated within a scenario, but you can run one in single player or on a server.

You can simply make artillery turrets uncraftable in any constructor and put that config on your server or single player game. If you want it included with a workshop scenario, you could probably place the file in the scenario folder and provide instructions on your workshop description of how individual players can copy the config file over to activate in single player or multi player, but it would be up to each player or server owner to use it or not.

 

thanks! I'll have a lock at those. is there an example around?

 

Empyrion - Galactic Survival/Content/Configuration

Config_Example.ecf is the file you want to look at.

Specifically, under the "templates" section:

Code:

{ Template Name: TurretBaseArtilleryBlocks
  CraftTime: 30
  Target: AdvC
  { Child Inputs
    SteelPlateArmored: 30
    PowerCoil: 10
    Motor: 3
    ZascosiumAlloy: 20
    Oscillator: 5
  }
}

You *should* be able to simply create a new txt file in that same directory, name it "Config.ecf" (without the quotes), and edit it to say the following:

Code:

VERSION: 3

{ Template Name: TurretBaseArtilleryBlocks
  Target:
}

That will over-write only THAT part of the config, leaving everything else default.

That should make base artillery turrets uncraftable by the player. You'll probably want to also remove them from the tech tree so players can't even spend points to unlock them but that's done in a different spot in the config file. I don't have any links to a guide on this atm but I'm sure there's some out there.

Obviously, test in a new game first, and config changes can lead to bugs or other weird issues so use at your own risk. I have not tested this change so it might not work. If you run into problems, simply delete any file named "Config.ecf" in the configuration folder.

 

And unfortunately, I just realized, this might not stop people from using it in a factory blueprint, however I think that can be changed as well.

 

it's perfect, server will not have bp anyway

 

Hope that works!

 

This won't work like this. You can't simply delete the ingredient lines otherwise the game will still use the default values (meaning they will still be craftable.)

"# - parameters not listed (commented out / removed) will cause the game to continue using the internal ORIGINAL values"
Meaning you can't simply delete those lines to make it uncraftable.

 

It's not changing the ingredients, it's removing the constructors that it can be crafted in so it should work. but I didn't test it so it might not work as I expect since it's been a couple months since I messed around with the config.

 

Forgive me, I haven't finished my coffee yet.
I didn't notice that you left it with no target. That may actually work.

 

You're probably doing better than I am, it's almost 7AM where I live and I still haven't gone to bed.