Facility Meltdown

The apparatus was a vital part of the upkeep of the facility's nuclear reactor - and you just took it out.

With the facility meltdown mod the appartus has a lot more risk (and reward) attached to it. When you take it out the entire facility spirals into a self destruction sequence! You'll have 2 minutes to escape and take off before you get vaporized.

Take a look at the known isuses if you have a problem, otherwise join the lethal company modding discord and find the FacilityMeltdown thread and report it there!

Config

Only the host needs to change their config as it is synced.

OPTIONAL ingame config editors

lethalconfig or lethalsettings will let you edit the settings in-game.

Known Issues

There has been previous reports of modded moons not playing well with this mod! As always go over to the lethal company modding discord and I can try and take a look. There seems to be no problem with Lethal Level Loader or LECore so it could be map dependent. In which case I wil NOT be fixing it. I can not fix every modded moon in this mod otherwise I would get nothing done.

For Modders

If you are a modder and you want to add custom effects in general or for your specific moon you can add a refernce to the dll and extend the MeltdownSequenceEffect class. Example:

internal class EmergencyLightsEffect : MeltdownSequenceEffect {
    public EmergencyLightsEffect() : base(MeltdownPlugin.modGUID, "EmergencyLights") {}

    public override IEnumerator Play(float timeLeftUntilMeltdown) {
        for (int i = 0; i < RoundManager.Instance.allPoweredLightsAnimators.Count; i++) {
            RoundManager.Instance.allPoweredLightsAnimators[i].SetBool("on", true);
        }

        yield return new WaitForSeconds(2f);

        for (int i = 0; i < RoundManager.Instance.allPoweredLightsAnimators.Count; i++) {
            RoundManager.Instance.allPoweredLightsAnimators[i].SetBool("on", false);
        }

        yield return new WaitForSeconds(5f);
        yield break;
    }
}

Then register it by creating an instance in your plugins Awake new EmergencyLightsEffect().

Available methods to override

void Start -> Called the moment the appartice is taken out IEnumerator Play -> Called either once (if .IsOneShot is true) or repeatedly until the exposion happens, or the ship leaves IEnumerator Stop -> Called when the explosion happens or .Playing is set to False in .Play void Cleanup -> Called when the ship leaves bool IsEnabledOnThisMoon -> return true if this effect should play on this moon

v2.6

• Entire rewrite of the config system.
• Meltdown now entirely handles config syncing, CSync is no longer a dependency.

v2.6.1

• Added more protection if meltdown fails to setup some effects.
• Fixed meltdown starting twice ig?

v2.6.2

• Fixed accidently clearing client configs.

v2.6.3

• Fixed Geiger Counter
• Fixed ship and map props lights turning red.
• Changed how the outside lights flash, should no longer be an all consuming void.

v2.6.4

• Hopefully fixed some windows locales being unable to load meltdown.

v2.6.5

• Fixed explosion particles being pink.
• Added a new config option, MinPeopleToPullApparatus. Default is 2. Requires at least this many people. If this number is larger than the amount of people in the lobby then EVERYBODY will need to be nearby.
• Lobby Compatibility is no longer a "hard" dependency but will remain a dependency on thunderstore. If it is causing issues you can disable it and meltdown will still work.

v2.6.6

• Fixed MinPeopleToPullAPparatus not taking into account dead people :skull:

v2.6.7

• Fixed Config not syncing correctly.

v2.6.8

• Applied Hotfix on GeneralImprovements to unbreak the tooltip when you need more people to pull the apparatus.
• MinPeopleToPullApparatus now only applies to 9PM. After 9PM anybody can grab the apparatus, regardless of how many people are nearby.

v2.6.9

• Removed GeneralImprovements hotfix as it was fixed in v1.2.7 :3

v2.6.10

• Reapplied the hotfix LMAO.

v2.6.11

• Undid the reapplied hotfix. :skull: