Thinking. 1. Analyze the Request: * Role: Expert technical writer / System administrator for Minecraft servers. * Topic: "Как настроить автоматическую очистку мира" (How to set up automatic world cleaning/trimming). * Platform/Environment: Specific host "proxify.cloud" (Proxmox panel, dedicated server, Ubuntu). Wait, the user prompt says панель proxify.cloud, but Proxmox is also mentioned. I need to be careful here. Proxify.cloud is a specific host; they might have a custom panel. Usually, hosting providers with Proxmox give access to the Proxmox web GUI (like IP:8006). There isn't a specific "panель proxify.cloud" that I am familiar with unless it's their specific reseller/customer area. I will interpret "панель Proxmox" as the Proxmox VE web interface, accessed through the account I have on proxify.cloud. * Language: Russian. * Style: Detailed step-by-step, markdown, heading # matching topic, ## subheadings, numbered steps, code blocks, specific commands, file paths, examples. Length 800-1500 words. No fluff. No HTML tags. * Content Requirements: * Start with # (matching topic). * Use markdown. * Mention proxify.cloud panel where appropriate. * Concrete commands, paths, examples. * Length: 800-1500 words. * Only practical steps. * End section: "Возможные проблемы и решения". * Only markdown, no HTML.

*   **Minecraft Server Context:** Automatic world clearing/trimming. On a dedicated server, this usually implies an automated script that removes old/unused chunks to reduce world file size, or periodically deletes/resets specific dimensions.
    *   *Self-Correction on "очистка мира":* In Russian Minecraft server admin slang, "очистка мира" usually means either:
        1.  **Trimming unused chunks** (using tools like `Minecraft Region Fixer`, `MCA Selector`, or `TrimChunkData` in Paper/Spigot). Paper has `/paper region` commands. There's also the `/minecraft:chunk` or `/forceload` but trimming is specific. Wait, Vanilla 1.19+? No, usually plugins or external tools. The `/minecraft:chunk` isn't for trimming paper's `paper trim`? Let's look at Paper plugins. `Chunky`, `WorldBorder` are for generating/pre-generating. `Region Fixer` for trimming. `FastAsyncChunkPurge`. `ObsidianDestroyer`? No. The most standard way now is using the in-game command if using Paper 1.18+ `paper region save`? No, Paper has `/paper chunk`? Wait. Paper has `/paper map`. No, the vanilla `/execute if blocks` or structure blocks... No.
        2.  **Resetting the Overworld/Nether/End** (deleting region files while preserving spawn). This is a very common "cleaning". "Очистка мира" in the context of hosts like this often specifically means a script to delete the `region` folder, `DIM1`, `DIM-1`, and possibly `playerdata` and `stats` while keeping a fresh `level.dat` or specific spawn chunks pre-generated.
        3.  **Auto-restart with world deletion on schedule** (classic anarchy/seasonal server style).

*   Let's look at the phrasing: "Автоматическая очистка мира". "Automatic world cleaning".
*   Let's assume the user wants a script that runs on a schedule (cron) that either:
    A) Trims the world of chunks that have no players (Paper plugin method: `/paper region`,`/chunky`, or an external Python/Bash script using `MCA Selector` or `Region Fixer`).
    B) Wipes the world except for spawn. "Очистка мира" can straightforwardly mean **wiping the world files** (deleting `world/region`, `world_nether/DIM-1`, `world_the_end/DIM1`).

    Let's provide the *most practical* and *requested* solution for a host like this running Paper/Spigot/Purpur. The most common request for "автоматическая очистка мира" on a VPS/Dedicated server is:
    1.  Automating world trimming using the `Chunky` plugin and scheduled tasks? No, `Chunky` generates.
    2.  Using `FastAsyncWorldEdit` trim? FAWE has `//replace` but not auto trim.
    3.  Using `ObsidianDestroyer`? No.
    4.  Using an external Python script `mca-selector` or `region-fixer` (deprecated).
    5.  Using in-game `/execute` and structure blocks? Too complex.
    6.  Writing a Bash script to delete region files older than X days, or delete all region files except spawn.

    Let's design a robust solution using a **Bash script** run via **Cron** on the Proxmox host (Ubuntu). The script will:
    *   Stop the Minecraft server gracefully (using `screen` or `rcon`). *Wait, the server doesn't have to stop if we are just trimming? If we delete region files, the server MUST be stopped.*
    *   Back up the world.
    *   Delete region files.
    *   Start the server.

    Let's refine "очистка мира". Given it's a dedicated server, the most impactful and requested task is **регенерация мира / вайп без потери спавна** (Regeneration / Wipe without losing spawn).
    *Step 1: Grab the spawn chunks. Save them.*
    *Step 2: Stop the server.*
    *Step 3: Delete world files (region, playerdata etc.).*
    *Step 4: Restore spawn chunks.*
    *Step 5: Start the server.*

    Wait, the user said "Автоматическая очистка мира". Let's interpret this in the most standard Russian Minecraft hosting context. Usually, this means trimming unused chunks to reduce lag and world size, or a full reset.

    Let's combine both!
    Option 1: **Тримминг мира** (Trimming chunks without players). Using `Paper` built-in command (since it's a server, likely Paper or Fabric. Paper is standard). `/paper region save`? No.
    *Paper commands:* `/paper chunk`? No, `/paper entity` counts. Vanilla `/data`...
    *Plugin method:* **Region Fixer** or **Paper Trim** (via `/wc`? No, WorldBorder `/wb trim` generates circles? No, `/wb trim` removes chunks).
    *Wait, `WorldBorder`'s `/wb trim` command (part of the WorldBorder plugin by BeepFalse) actively removes chunks outside a certain border.*
    *Let's use **Chunky** (and the `ChunkyBorder`?) No.
    * **Bluemap**? No.
    * **FastAsyncWorldEdit** (FAWE) has `//trim`!
    * **ObsidianDestroyer**? No.
    * **ProtocolLib**?
    * Let's think of the simplest script that works on Ubuntu with cron.
    * **Tool:** `mcaselector` (MCA Selector) is a Java GUI tool, but it has a CLI mode! No, it's a GUI tool (JavaFX). You cannot run it easily non-interactively in a headless server without Xvfb. "mcaselector-cli"? No, the developer explicitly said no CLI for standard users, but there is a headless mode via `--headless` flag in newer versions! `java -jar mcaselector.jar --headless --world /path --delete-unreferenced`? Wait, MCA Selector has a "Tool" -> "Delete chunks" or "Delete entities". It has a headless mode starting from version 2.0!
       `java -jar mcaselector.jar --help`
       Example: `java -jar mcaselector.jar -w /path/to/world -d -s` (delete chunks)? No, the headless mode is complex. Let's check the exact commands. `--tool SELECTION --world /path --delete-chunks-tagged` is not natively a simple CLI script unless a filter/selection is preconfigured.
       MCA Selector headless allows applying a pre-saved filter! Yes, you can save a filter in the GUI and then apply it via headless.
       But the user might not have MCA Selector installed. Let's rely on **pure command line** tools or **server plugins**.

    **Best approach for "Автоматическая очистка мира" on a host like proxify.cloud:**
    1.  **Using Bash and Cron:** A script that stops the server, deletes specific regions, and restarts it. This is the most "server admin" approach.
    2.  **Using a Plugin:** A plugin that does this automatically in-game (e.g., `AutoTrimWorld`, `AutoResetWorld`, `SeasonalReset`).
        Let's use a plugin called **AutoResetWorld** or **WorldRegenerator**? No.
        How about **OCEAN**? (Plugin for Paper). No.
        Let's use **Purpur** (a fork of Paper) which has built-in settings like `blocks.purpur.trident`? No.
        **Paper** has `settings.chunk.per-player-mob-spawns` but no auto-trim.

    Let's provide a solution using a **cron job** + **bash script** + **`rcon`** to issue commands. This is universally applicable and doesn't rely on specific panel features of proxify.cloud (which is just Ubuntu + Proxmox). I will acknowledge the panel for starting/stopping VMs and accessing the console.

    **The "Cleaning" process "автоматическая очистка":**
    I will write a guide for **two** common interpretations of "автоматическая очистка мира", since the user didn't specify which one. This covers 1500 words perfectly.

    *Interpretation A: Тримминг чанков (World Trimming)*
    -> Remove unused chunks outside a radius or that haven't been visited.
    -> Tool: `MCASelector` with headless mode, or a Paper plugin `Chunky` + `WorldBorder`, or a script that deletes region files older than a timestamp.

    *Interpretation B: Вайп мира (World Reset / Wipe)*
    -> Complete reset of the Overworld, Nether, and End, keeping the server spawn area.
    -> Tool: Custom Bash script using `rcon` and `cron`.

    **Structure of the Article:**
    1. `# Как настроить автоматическую очистку мира` (Title)
    2. `## Введение` (Brief intro, target environment)
    3. `## Предварительные требования`
       - Доступ к Proxmox (proxify.cloud)
       - Ubuntu Server
       - MC Server (Paper/Purpur) with RCON enabled
    4. `## Сценарий 1: Автоматический тримминг чанков с помощью MCA Selector`
       - `### Установка MCA Selector`
       - `### Создание скрипта для тримминга`
       - `### Настройка Cron`
    5. `## Сценарий 2: Полный вайп мира с сохранением спавна`
       - `### Подготовка спавна`
       - `### Создание скрипта вайпа`
       - `### Настройка Cron`
    6. `## Возможные проблемы и решения`

    **Detailed Drafting:**

    Title: `# Как настроить автоматическую очистку мира`

    `## Введение`
    Если ваш сервер на хостинге `proxify.cloud` (Ubuntu, Proxmox) начал тормозить из-за переполненного мира, или вы проводите регулярные вайпы (например, раз в месяц), автоматизация этого процесса — необходимость. В этой инструкции мы рассмотрим два популярных сценария: тримминг неиспользуемых чанков и полный вайп мира с сохранением спавна. Все действия выполняются через SSH или консоль Proxmox.

    `## Предварительные требования`
    1. Доступ к панели `proxify.cloud` или Proxmox для управления ВМ.
    2. Установленный сервер Minecraft (рекомендуется Paper/Purpur).
    3. Включенный RCON в `server.properties`:
       ```
       enable-rcon=true
       rcon.password=ваш_сложный_пароль
       rcon.port=25575
       ```
    4. Утилита `rcon-cli` или `mcrcon`. Мы будем использовать `mcrcon`.
       ```bash
       cd /usr/local/bin
       wget https://github.com/Tiiffi/mcrcon/releases/download/v0.7.2/mcrcon-0.7.2-linux-x86-64.tar.gz
       tar -xzf mcrcon-0.7.2-linux-x86-64.tar.gz
       rm mcrcon-0.7.2-linux-x86-64.tar.gz
       # Теперь mcrcon доступен из конс