List every service on the Nitrado account with its id, game, status and expiry. Call this when you don't yet know the service_id of the Project Zomboid server, or when the user asks what they have hosted.

Live status of the PZ gameserver: online/offline, address, slots, players currently connected, game version and memory. Call this when the user asks whether the server is up, who is playing, or for the connection address.

Discover the absolute paths of this server's config files (.ini, _SandboxVars.lua, _spawnregions.lua). The server name is host-assigned, so call this before touching any config path instead of guessing filenames.

List a directory on the gameserver, or search it recursively when a glob pattern is given (e.g. '*.lua'). Call this to explore the server filesystem — saves, logs, mods — beyond the known config files.

The account's audit trail for this service — the panel's 'Registro de eventos'. Records who did what and when: restarts and stops, config file uploads and deletions, settings changes, game installs. Call this for 'who restarted the server', 'what changed recently', or to see whether an action actually went through. This is about actions taken on the service; for what the game itself did, use pz_tail_log.

Read a file from the gameserver as text. Call this when you need the raw contents — a full SandboxVars.lua, a log, a save file. file may be an absolute path or one of the shortcuts 'ini', 'sandbox', 'spawnregions'.

Read the main .ini and return it as a parsed key/value object. Call this when the user asks about a specific setting (password, max players, PVP, public name) — easier than reading the raw file.

Return the current Mods and WorkshopItems lists in load order. Call this before changing mods, so you can see what is already installed.

List the server's log files newest-first: the live console log plus PZ's rotated logs (chat, user, admin, map, pvp, DebugLog-server...), each with its kind, size and start time. Call this when the user asks what logs exist, or before tailing one you're not sure is there.

Read the last N lines of a server log. This is the tool to use for 'what happened', 'why did it crash', 'who connected', or 'show me the chat'. Only the tail is fetched, so it stays fast on multi-megabyte logs.

List the saved configuration snapshots — the panel's 'Perfiles de Configuración'. Nitrado writes one automatically most days, plus any you save by hand, so this is the server's config history. Returns names, ids and dates only; use pz_get_config_profile or pz_diff_config_profile to look inside one.

Return a config file exactly as it was when the snapshot was taken. Use this to see what a setting used to be, or to recover a value that was changed or lost. Passwords are redacted unless you ask for them.

Compare a saved snapshot's server .ini with the one running now, and report only what differs. This is the tool for 'what changed since Friday', 'what did I break', or checking whether an edit actually landed. Passwords are redacted unless you ask for them.

Read the sandbox tuning (SandboxVars.lua): zombie population and speed, loot rarity, day length, XP rates, erosion and so on. Roughly 270 settings, so pass search to narrow it — 'zombie', 'loot', 'day' — which also returns the in-file documentation explaining what each numeric value means. Call this before pz_set_sandbox so you use real setting names and the right enum numbers.

Change sandbox settings in place, preserving the file's comments, ordering and every setting you don't touch. Use dotted names for nested ones ('ZombieLore.Speed'). Values are the raw game values — look them up with pz_get_sandbox first, since most are numeric enums where 1 is not 'on' but a specific option. Takes effect after a restart.

Overwrite a file on the gameserver, keeping a timestamped .bak copy of the previous content. Use this for whole-file replacements such as a rewritten SandboxVars.lua; prefer pz_set_settings for individual .ini keys. Takes effect after a restart.

Update individual keys in the main .ini while preserving comments, ordering and every other option; missing keys are appended. Call this for any change to server settings such as PublicName, Password, MaxPlayers or PVP.

Update Mods and WorkshopItems together. Each entry needs BOTH ids: workshopId is what Steam downloads, modId is what the game loads, and they are different identifiers. Array order is load order, which matters in PZ. Call this for any add/remove/reorder of the server's mod list.

Restart the gameserver so config or mod changes take effect. Players are disconnected. Call this after any write, once the user confirms. This is also how you START a stopped server — the API has no separate start action. Takes roughly a minute; pz_server_status may still report 'started' for a few seconds afterwards, so don't read a stale status as the restart having failed.

Stop the gameserver. Call this only when the user explicitly wants the server down — to apply config changes use pz_restart instead. It stays offline until someone calls pz_restart, which is the only way back up.