# How to Configure the Meteor on Your Eco Server (Disasters.eco) (/docs/eco/meteor-disasters)



import { Step, Steps } from 'fumadocs-ui/components/steps';
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';

The meteor is Eco's signature pressure mechanic — a 30-day countdown to apocalypse that drives every government, environmental, and engineering decision on the server. Most server admins want to either **disable it** (casual / RP / building servers) or **tune the timer** (longer for new groups, shorter for hardcore). This page covers both.

The Critical Gotcha [#the-critical-gotcha]

Meteor settings live in **`Disasters.eco`**, not `Difficulty.eco` like most guides incorrectly state. If you've edited `Difficulty.eco` looking for a meteor toggle and nothing changed — that's why.

```
Eco/Eco_Data/Server/Configs/Disasters.eco
```

If `Disasters.eco` doesn't exist on your server, copy `Disasters.eco.template` (in the same folder) and rename it.

The Settings [#the-settings]

```json
{
  "CreateMeteor": true,
  "MeteorImpactDays": 30.0
}
```

| Key                | Default | Description                                        |
| ------------------ | ------- | -------------------------------------------------- |
| `CreateMeteor`     | `true`  | Master toggle. `false` = no meteor spawned at all. |
| `MeteorImpactDays` | `30.0`  | Days from world creation to meteor impact.         |

Disable the Meteor (New World) [#disable-the-meteor-new-world]

<Steps>
  <Step>
    Stop your server from **Console** in the [XGamingServer Panel](https://panel.xgamingserver.com).
  </Step>

  <Step>
    Open `Eco/Eco_Data/Server/Configs/Disasters.eco` in **Files**. Set:

    ```json
    {
      "CreateMeteor": false,
      "MeteorImpactDays": 30.0
    }
    ```
  </Step>

  <Step>
    Save and start the server. **Critical:** this only takes effect on a **new world generation**. If your world already exists, see "Live World" below.
  </Step>
</Steps>

Tune the Meteor Timer (New World) [#tune-the-meteor-timer-new-world]

Same workflow — change `MeteorImpactDays` to whatever you want.

| Value   | Effect                                                    |
| ------- | --------------------------------------------------------- |
| `30.0`  | Default — 30 in-game days                                 |
| `60.0`  | Casual — 60 days for slower-paced groups                  |
| `100.0` | Builder — 100+ days lets players actually finish projects |
| `15.0`  | Hardcore — 15 days, intense pressure                      |

Live World — Use Admin Commands [#live-world--use-admin-commands]

If your world is already generated, editing `Disasters.eco` does nothing. You have to use admin chat commands instead:

<Tabs items={['Destroy the meteor', 'Adjust the timer']}>
  <Tab value="Destroy the meteor">
    In the in-game chat (as admin):

    ```
    /meteor destroy
    ```

    The meteor is removed entirely. The world has no impact event. To re-spawn it later you'd need a fresh world.
  </Tab>

  <Tab value="Adjust the timer">
    ```
    /meteor addhours 240
    ```

    Adds 240 hours (10 in-game days) to the impact timer. Use a negative number to bring impact closer:

    ```
    /meteor addhours -240
    ```

    The change is immediate and persists across restarts.
  </Tab>
</Tabs>

What Happens When You Disable the Meteor [#what-happens-when-you-disable-the-meteor]

* The meteor visual in the sky disappears
* The 30-day countdown UI element doesn't appear
* The impact never occurs
* All other game systems (skills, government, ecosystem) work normally

This makes Eco play more like a pure cooperative civilization simulator without the deadline pressure. Some servers re-enable it later via `/meteor` commands once players have built infrastructure.

Verifying the Setting Took Effect [#verifying-the-setting-took-effect]

After restart, look at the world map UI for the meteor countdown. If it's gone, the setting worked. If it's still ticking down, either:

* The server overwrote your edit (you didn't fully stop it before editing)
* The world was already generated and the new setting only applies to fresh worlds
* The file you edited was `Difficulty.eco`, not `Disasters.eco`

Related Guides [#related-guides]

* [Configure Your Server](/docs/eco/configure-your-server)
* [World Generation](/docs/eco/world-generation)
* [Admin Commands](/docs/eco/admin-commands)
* [Backup & Restore](/docs/eco/backup-restore)