DEV Community

ahmed isam
ahmed isam

Posted on Originally published at codexpetgenerator.com

Codex Desktop Updates: What's New for Pets

--
title: "Codex Desktop Updates: What's New for Pets"
description: "A codex pet update arrives inside the Codex desktop app."
tags: ["codex", "desktop", "updates", "pets"]

canonical_url: https://codexpetgenerator.com/blog/codex-desktop-updates-pets

A codex pet update arrives inside the Codex desktop app. There is no pet updater to run and nothing to reinstall.

What a codex pet update actually touches. - Your pets folder: untouched by the installer

  • The spritesheet and pet.json you generated: untouched
  • Your custom palette and animation states: untouched
  • The renderer, the animation timer and the default pet set: replaced with the new build

Where the pet files sit during an upgrade. Everything you own lives under the pets directory in your home folder: ~/.codex/pets/ on macOS, %USERPROFILE%/.codex/pets/ on Windows. Installers write to the application directory, which is a different place, so an upgrade has no reason to walk into your pets folder.

Reading a codex pet changelog without the noise. Changelogs are written for the whole app, and the pet-related lines hide somewhere in the middle. The words worth scanning for are renderer, window, assets and sprite.

What to check before you report a broken pet. Most reports of an update breaking a pet turn out to be one of four things, and all four take under a minute to rule out. Run them in this order before you write anything up.

The part worth keeping: Generate a pet at codexpetgenerator.com, keep the folder in your home directory, and updates stop being an event. Full write-up is on the source blog.

Top comments (0)