You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command deploys {{ .Project.App }} on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
The command removes all the Kubernetes components associated with the chart and deletes the release.
49
+
50
+
## Importing a save file
51
+
52
+
> :warning: Importing a save file will **OVERWRITE THE SERVER SAVEFILE** with the name specified in `factorioServer.save_name`. Import with caution!
53
+
54
+
### Importing by URL
55
+
56
+
To import your save file from a URL, set `import_save.source_url` to a direct-download link for your savegame. By default, the file will be downloaded and imported only once.
57
+
58
+
If, on pod intialization, you wish to re-import the file every time the contents of the savegame change, set `import_save.reimport_on_change` to `true`.
59
+
:warning: If the savegame at the source url changes, this will overwrite the server save with that file. Use with caution!
60
+
61
+
If you wish to reimport the save file every time the pod reinitializes, regardless of changes, set `import_save.reimport_every_time` to `true`. This could be useful for demos or testing.
62
+
:warning: This will overwrite the server savegame **every time the pod reinitializes**. Use with caution!
63
+
64
+
### Manual Import
65
+
66
+
To import an existing save file, start/restart the pod at least once. This will create the import folder structure.
67
+
68
+
Now, copy the savegame you wish to import to the `/factorio/save-importer/import/<existing_savegame_name>.zip` on the running pod using whatever mechanism you prefer. To do this with kubectl:
If the Factorio server doesn't start, check that the logs don't have an error with the mods. They are pretty verbose.
108
+
109
+
### Overhaul mods
110
+
It is possible that your mod may extend the default settings. As a result, your server might not start properly and instead throw an error.
111
+
112
+
While we expose all the default settings, we would not be able to determine what is needed if it is absent. To add new settings you would need to convert the desired json file into a yaml struct as we are mounting all configurations as a config map into the container.
113
+
114
+
For example prior to the official release of 2.0, there was an issue with Space Exploration. The `autoplace_controls` by default is an empty array, and thus we were not able to start the instance as there were no settings for them to evaluate. Additionally, they are also modifying some of the other settings. These changes implement the default recommended settings, available in the UI and were stored in a file at `...Factorio\mods\space-exploration\shared.lua`. In the lua file, it has 2 sections, basic_settings and advanced_settings which correspond to settings in `map-gen-settings.json` and `map-settings.json` respecively.
115
+
116
+
At the time of writing, to make these changes you would need to add this to your values.yaml file to override their default values in the chart.
117
+
118
+
> **_NOTE:_** These settings may change and it is important to check with the mod maintainer/community to check the recommended settings.
119
+
```
120
+
map_settings:
121
+
pollution:
122
+
enemy_attack_pollution_consumption_modifier: 0.5
123
+
enemy_evolution:
124
+
time_factor: 0.0000005
125
+
destroy_factor: 0.0005
126
+
pollution_factor: 0.00000025
127
+
128
+
map_gen_settings:
129
+
water: 1.5
130
+
starting_area: 2
131
+
autoplace_controls:
132
+
hot:
133
+
size: 0.5
134
+
cold:
135
+
size: 0.5
136
+
property_expression_names:
137
+
control-setting:moisture:bias: '0.05'
138
+
control-setting:aux:bias: '-0.35'
139
+
```
140
+
More information about the debugging process for the space exploration mod can be read on [Issue 24](https://github.com/SQLJames/factorio-server-charts/issues/24).
141
+
142
+
If you do run into any issues with mods, I will try to work with you on finding the right settings and document them as well.
143
+
144
+
{{ if .Chart.Values -}}
145
+
146
+
## Configuration
147
+
148
+
The following table lists the configurable parameters of the `{{ .Chart.Name }}` chart and their default values.
149
+
150
+
{{ .Chart.Values }}
151
+
152
+
Specify each parameter using the `--set key=value[,key=value]` argument to `helm upgrade -i`. For example:
0 commit comments