How to write a Devlog Entry

1. Group First: Before anything else, group related items from the raw change list into a single, high-level feature. For example, added popup on actor hover and added popup bgs become one item: a popup with actor info.

   • Use colon and list for details: When a feature has multiple specific implementations, use list those to preserve granular information. For example:

     - навыки для ящеров: травят оружие ядом, последний получает эффект Last Stand
     - огромный рефакторинг системы навыков: контейнер, умный базовый класс, много фиксов

   • Don't over-consolidate: The goal is clarity, not minimalism. Preserve important details within grouped items.

2. Adopt an Informal, Player-Centric Tone: This is the primary goal. For each high-level feature, rewrite the description in concise, informal Russian. Focus on the player's experience and the fun aspect of the change, not the technical implementation. This is where "прикольные имена ящерам" comes from instead of "added names to actors".

3. Abstract and Simplify: Abstract technical details into their purpose (e.g., updated GEMINI.md -> обновил инструкции для ИИ-агента). Keep descriptions concise and punchy (e.g., контейнер, умный базовый класс, много фиксов instead of lengthy explanations). Omit minor, uninteresting details, but preserve items that show meaningful technical progress (tests added, sound system improvements, class system enhancements). Use catchalls like много всякого мелкого и большого when appropriate.

4. Use Categories Sparingly: Only introduce categories if there are two or more items that fit into that category. Otherwise, omit isolated or minor technical changes to avoid clutter.

   • Common categories (use when applicable):
     • Main features (no category header, appears first)
     • Фиксы: - Bug fixes
     • Доки: - Documentation, design notes, architecture drafts (include specific details about what was decided)
     • Рефакторинг: - Code refactoring
     • Тулинг: - Tools, AI instructions, development utilities

5. Format as a Simple List: The final output will be a simple markdown list starting with -. The main, player-focused changes will appear at the top, followed by any categories if they were needed.

Constraints

• Do not change older entries
• Start each point with lowercase letter
• Do not put . (dot) at the end of each point