Silo 2 Reset Key
Nuke Codes always have 8 digits and are only valid in their corresponding nuclear silo: Alpha, Bravo, and Charlie. You can use the launch control terminal in any of these silos to specify a location on the Fallout 76 Map as a target for your nuclear missile.
Silo 2 reset key
If you want to launch a nuclear missile in Fallout 76, you need one nuke code: Alpha, Bravo, or Charlie. The only restriction is, that you need to use the code in the corresponding silo. E.g. in silo Alpha, only the Alpha Nuke Code will work.
The Silo is a nuclear missile silo located on a right turn from the road leading to Tumbleweed. The buildings on the surface have no interesting value to them due to an absence of items. However, the surface contains enemies such as T-Dolls and Cultists. The only thing interactable inside the Silo is the nuclear launch console imbedded into the ground, which is only able to be used by people if they have both the launch key and launch code, causing a server-wide event.
It is important to understand, that by updating Silo you do not automatically switch the Ansible version. Ansible is stored in the Docker volume silo.$(whoami). If you want to switch the Ansible version, you manually need to run the switch.
The Docker command which gets executed for calling Ansible is stored inside the image itself, so it cannot be modified. To inject additional parameters into the command you can define functions in ./.ansible-silo, your /.ansible-silo or globally in /etc/ansible/ansible-silo/ansible-silo file matching the pattern silo_* or _silo_*. The runner script will execute all silo_* and _silo_* functions and append their output to the Docker command.
In Silo bundles you can add functions to the file bundle_extension.sh inside your bundle directory. To customize behavior per user or host, you also have the option to add functions to files matching the image name. If, for example, you run a bundle called foo-bar, Silo will search for the files ./.foo-bar, /.foo-bar and /etc/ansible/ansible-silo/foo-bar and append the output of all functions matching the pattern foo_bar_* to the Docker command.
If set to a valid Silo version, that specific version of Silo container will be started. This does not change the installed ansible-silo command. Most functionality though is inside the container and not the starter script.
The name of the volume can be changed by passing the environment variable SILO_VOLUME. The volume name will be prepended with silo. and automatically be created if it does not exist. It will contain Ansible 220.127.116.11, the latest version as of writing this document. To change the Ansible version in that volume run the switch command:
The ansible-silo image is an automated Docker build triggered by Travis CI, whenever a tag passed all tests. This means, to release a new version only a new tag in the form v1.2.3 needs to be released.
To ensure we are never forced to update any dependency when we build the silo Docker image, all APK dependencies are stored in the Docker image ansible-silo-base. If required, this image can be built and uploaded with the command make ansible-silo-base push-base. Make sure to afterwards update the tag in the Dockerfile and release a new version of ansible-silo.
A Standard Permit allows a player to construct two silos. It also allows a player to use 2 boosts simultaneously and equip 2 Artifacts simultaneously. Standard Permit players cannot upgrade the Fuel Tank.
The Pro Permit is a premium Permit that can be purchased in The Shop (or by clicking a locked feature only unlockable with the Pro Permit) for USD$9.99. A Pro Permit allows a player to construct up to 10 silos and makes your silos high quality by doubling offline earnings compared to the Standard Permit. The Pro Permit also allows a player to use up to 5 boosts simultaneously, equip up to 4 Artifacts simultaneously, and upgrade the Fuel Tank (at the expense of Golden Eggs).