rpgsync 0.1.0__tar.gz

rpgsync-0.1.0/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+## Versions
+
+rpgsync is released on [PyPI](https://pypi.org/project/rpgsync/) as `0.MINOR.PATCH`:
+
+- **MINOR** goes up when the scripts change: `rpgsync pull` writes a game's scripts
+  differently (another layout, other names, another way to write a command), or scripts
+  written by it may not work with the previous minor version (a DSL name renamed or
+  removed).
+- **PATCH** goes up for everything else: fixes and additions after which `rpgsync pull`
+  writes the same scripts.
+
+A game's `Scripts/pyproject.toml` depends on the version that set it up,
+`rpgsync~=0.MINOR.PATCH` (that version and its later patches), and its `Scripts/uv.lock`
+pins the exact one. [Upgrading rpgsync](README.md#upgrading-rpgsync) moves a game to a
+newer one; [Releasing](docs/development.md#releasing) makes a new one.
+
+## Unreleased
+
+## 0.1.0
+
+First release on PyPI.
+
+- A new game's scripts depend on `rpgsync~=0.1.0` from PyPI, pinned by their `uv.lock`,
+  instead of a link to this computer's rpgsync folder.
+- A developer of rpgsync links their rpgsync folder as `Scripts/.rpgsync/rpgsync`:
+  rpgsync installs it, editable, in the scripts' environment, and leaves
+  `pyproject.toml` and `uv.lock` as they are.

rpgsync-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Nicolas Oulianov
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

rpgsync-0.1.0/PKG-INFO

@@ -0,0 +1,288 @@
+Metadata-Version: 2.4
+Name: rpgsync
+Version: 0.1.0
+Summary: A Python twin of your RPG Maker 2000/2003 game
+Keywords: rpg-maker,rpg-maker-2000,rpg-maker-2003,easyrpg,gamedev,dsl
+Author: Nicolas Oulianov
+License-Expression: MIT
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Games/Entertainment :: Role-Playing
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Typing :: Typed
+Requires-Dist: pydantic>=2.14.0
+Requires-Dist: rich>=15.0.0
+Requires-Dist: ruff>=0.16.10
+Requires-Dist: typer>=0.27.3
+Requires-Python: >=3.11
+Project-URL: Homepage, https://github.com/oulianov/rpgsync
+Project-URL: Repository, https://github.com/oulianov/rpgsync
+Project-URL: Issues, https://github.com/oulianov/rpgsync/issues
+Project-URL: Changelog, https://github.com/oulianov/rpgsync/blob/master/CHANGELOG.md
+Description-Content-Type: text/markdown
+
+# rpgsync
+
+A Python twin of your RPG Maker 2000/2003 game.
+
+**rpgsync** turns the events of your game into readable Python scripts, and keeps both sides in sync while you work.
+
+- Edit events in your favourite editor, with autocompletion, type checking, search and git.
+- Translate dialogs and database more easily
+- Implement automated tests to verify game mechanics
+- Improve your game using the modern developer's toolkit
+
+
+## Code example
+
+```python
+@event(10, "Jeremy", x=15, y=38)
+class Jeremy(Event):
+    sprite = ("heroes1", 1)  # the settings of every page
+    layer = "same"
+
+    def page_1(self):
+        """Greetings (stored in the game as the page's first comment)"""
+        text(r"\n[3] : Bonjour, je suis \c[2]Jeremy\c[0].")
+        this.move(move_up * 3, face_player, frequency=8)
+        Ulysse.move(move_up * 2)  # another event of this map, by name
+        if party.gold >= 100:
+            match show_choices("Payer", "Partir"):
+                case "Payer":
+                    # Take gold (this is stored in the events!)
+                    party.gold -= 100
+                    items[3].count += 1
+                case "Partir":
+                    return
+        else:
+            text("Reviens avec de l'or.")
+        variables[102] += 1
+
+    @page(when=variables[102] >= 1)  # the active page: the last one whose condition holds
+    def page_2(self):
+        text("Merci encore !")
+        Ulysse.page_1()  # runs Ulysse's page 1 (Call Event)
+
+
+@event(11, "Ulysse", x=10, y=42)
+class Ulysse(Event):  # The other event!
+    sprite = ("heroes1", 0)
+    layer = "same"
+
+    def page_1(self):
+        pass
+```
+
+Every command, option and value is typed and documented in
+[`rpgsync/dsl.py`](https://github.com/oulianov/rpgsync/blob/master/rpgsync/dsl.py): your
+editor shows the docs on hover and flags wrong values (a misspelled direction, a sprite
+index above 7, ...). [Writing scripts](https://github.com/oulianov/rpgsync/blob/master/docs/scripts.md)
+explains events and pages, variables by name, the database and the map tree.
+
+## Demo
+
+A Doom-like 3d game in RPGMaker using only pictures of vertical slices. The tedious, repetitive event code has been automatically generated.
+
+https://github.com/user-attachments/assets/9246ff34-b226-4ebc-b8a3-e55b3adcc5d5
+
+
+## Compatibility
+
+rpgsync works with **RPG Maker 2000 and 2003** games, both in old versions (1.08) and
+Steam version (1.12a). It was tested on EasyRPG's test suites and on complete games.
+[Learn more.](https://github.com/oulianov/rpgsync/blob/master/Tested_Games.md)
+
+**Supported Patches:** Everything! DynRPG, Maniac Patch, EasyRPG commands, Power Mode
+2003, Ineluki Key Patch... Patches with unknown commands are kept as raw. Patches that
+only change the engine don't matter for this module.
+
+
+## Getting started
+
+### 1. Install uv
+
+rpgsync uses [uv](https://docs.astral.sh/uv/) to manage Python:
+
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
+```
+
+(Windows: `powershell -c "irm https://astral.sh/uv/install.ps1 | iex"`)
+
+### 2. Install rpgsync
+
+```bash
+uv tool install rpgsync
+```
+
+This puts the `rpgsync` command on your PATH.
+
+### 3. Set up your game
+
+Run rpgsync in your game folder (the one containing `RPG_RT.ldb`):
+
+```bash
+cd /path/to/MyGame
+rpgsync
+```
+
+The first time, it asks, then writes your maps, database and common events as Python
+scripts in `Scripts/`, with tests and their own Python environment. It then keeps the
+game and the scripts in sync until Ctrl+C.
+
+Open the `Scripts` folder in your editor and select its `.venv` as the Python
+interpreter. You're seeing your Python clone!
+
+If the game is in git, commit `Scripts/` with it, `pyproject.toml` and `uv.lock`
+included: they pin the rpgsync version of the game (see
+[Sharing a game](#sharing-a-game)). Its `.gitignore` leaves out `.venv/` and rpgsync's
+own files (`.rpgsync/`).
+
+
+## Everyday use
+
+```bash
+rpgsync           # keep the game and the scripts in sync, until Ctrl+C
+rpgsync status    # what is pending, on which side
+rpgsync pull      # game -> scripts
+rpgsync push      # scripts -> game
+rpgsync check     # compile and check the scripts (types too), write nothing
+rpgsync clean     # delete the backups of overwritten files
+```
+
+- A command works on the game of the current folder (the game's or `Scripts/`), or of
+  the folder given: `rpgsync status /path/to/MyGame`.
+- `--map N` limits a command to one map. `check` also takes scripts and folders:
+  `rpgsync check Map0004.py database`.
+- `pull --force` overwrites scripts that have unsynced edits; `push --force` writes
+  every script, not only those changed since the last sync.
+- `rpgsync locate --map 4 --event 12` prints where the scripts write an event
+  (`FILE:LINE`).
+- `rpgsync COMMAND --help` lists a command's options.
+
+### With the EasyRPG Editor
+
+> [!TIP]
+> **The EasyRPG Editor is the recommended editor to use with rpgsync.** It stays open
+> while rpgsync runs, and merges your Python edits with the changes you make in it.
+
+In the [EasyRPG Editor](https://github.com/oulianov/Editor), turn on **rpgsync mode**
+(Settings). The Editor reloads the changes made on disk and shows them as well as it
+can, so it can stay open while `rpgsync` runs. When both sides change the same game,
+it merges what each changed and only asks when the same entry changed on both sides.
+
+### With the RPG Maker 2000/2003 editor
+
+```bash
+rpgsync pull     # game -> scripts
+# edit the Python files
+rpgsync push     # scripts -> game
+```
+
+then open the editor and keep editing there.
+
+> [!WARNING]
+> **Keep the RPG Maker editor closed while you edit the Python files.**
+> The editor keeps its own copy of your game in memory and ignores your Python
+> edits: its next save (a map, the database, or quitting) writes that copy back
+> over them.
+
+### Play-test with EasyRPG Player
+
+[EasyRPG Player](https://easyrpg.org/player/) runs RPG Maker 2000/2003 games on
+Windows, macOS, Linux and more, and is the quickest way to test your changes: start
+the game, play, quit, edit, start again.
+
+### Will this break my project?
+
+rpgsync is built so that **it should not**. If anything, you can always go back.
+
+- **Invalid scripts are never written.** A typo, a wrong value or a RPG Maker 2003
+  command in a 2000 game stops at the
+  [checks](https://github.com/oulianov/rpgsync/blob/master/docs/checks.md).
+- **Every overwritten file is backed up** (game files and scripts) in
+  `Scripts/.rpgsync/history/`, the last 50 syncs. `rpgsync clean` deletes them once
+  you no longer need them.
+- Only what you changed is written.
+- If the same event changed on both sides, the editor's version is kept and your
+  script is saved next to it as `MapXXXX.conflict-<time>.py` (in one file, for a
+  script split in files).
+
+Using git on the game folder and doing backups is still a good idea.
+
+
+## Sharing a game
+
+`Scripts/pyproject.toml` depends on the rpgsync release that set the game up
+(`rpgsync~=0.1.0`), and `Scripts/uv.lock` pins its exact version. Whoever clones the
+game runs that version, in `Scripts/`:
+
+```bash
+uv sync           # install the game's rpgsync, and the scripts' tools
+uv run rpgsync    # run it
+```
+
+A CI job does the same: `uv sync --locked`, then `uv run --locked rpgsync ...`.
+
+
+## Upgrading rpgsync
+
+The `rpgsync` command:
+
+```bash
+uv tool upgrade rpgsync
+```
+
+A game, in its `Scripts/` folder:
+
+- **A fix release** (0.1.0 → 0.1.3) writes the same scripts:
+
+  ```bash
+  uv sync --upgrade-package rpgsync
+  ```
+
+  then commit `uv.lock`.
+- **A new minor version** (0.1.x → 0.2.0) writes the scripts differently. With
+  nothing pending (`rpgsync status`):
+
+  ```bash
+  uv add "rpgsync~=0.2.0"
+  uv run rpgsync pull --force
+  ```
+
+  then commit `pyproject.toml`, `uv.lock` and the rewritten scripts together.
+
+[CHANGELOG.md](https://github.com/oulianov/rpgsync/blob/master/CHANGELOG.md) lists
+what each version changes. An `rpgsync` command newer than a game's version would
+rewrite its scripts in the newer format: on a game you don't upgrade yet, use
+`uv run rpgsync` in its `Scripts/`.
+
+
+## Learn more
+
+- [Writing scripts](https://github.com/oulianov/rpgsync/blob/master/docs/scripts.md):
+  events and pages, variables and switches by name, the database, the map tree, big
+  scripts as folders
+- [Checks and tests](https://github.com/oulianov/rpgsync/blob/master/docs/checks.md):
+  `rpgsync check`, the scripts' tests, resource files
+- [DynRPG and DynParams](https://github.com/oulianov/rpgsync/blob/master/docs/dynrpg.md):
+  plugin calls, and a variable wherever RPG Maker takes a number
+- [Patches](https://github.com/oulianov/rpgsync/blob/master/Patches.md): how each patch
+  shows in the scripts, and their settings
+- [Tested games](https://github.com/oulianov/rpgsync/blob/master/Tested_Games.md)
+- [Working on rpgsync](https://github.com/oulianov/rpgsync/blob/master/docs/development.md):
+  use your own rpgsync in a game, run its tests, release it
+- [Changelog](https://github.com/oulianov/rpgsync/blob/master/CHANGELOG.md)
+
+
+## License
+
+MIT, 2026: see [LICENSE](https://github.com/oulianov/rpgsync/blob/master/LICENSE). Source: https://github.com/oulianov/rpgsync

rpgsync-0.1.0/README.md

@@ -0,0 +1,257 @@
+# rpgsync
+
+A Python twin of your RPG Maker 2000/2003 game.
+
+**rpgsync** turns the events of your game into readable Python scripts, and keeps both sides in sync while you work.
+
+- Edit events in your favourite editor, with autocompletion, type checking, search and git.
+- Translate dialogs and database more easily
+- Implement automated tests to verify game mechanics
+- Improve your game using the modern developer's toolkit
+
+
+## Code example
+
+```python
+@event(10, "Jeremy", x=15, y=38)
+class Jeremy(Event):
+    sprite = ("heroes1", 1)  # the settings of every page
+    layer = "same"
+
+    def page_1(self):
+        """Greetings (stored in the game as the page's first comment)"""
+        text(r"\n[3] : Bonjour, je suis \c[2]Jeremy\c[0].")
+        this.move(move_up * 3, face_player, frequency=8)
+        Ulysse.move(move_up * 2)  # another event of this map, by name
+        if party.gold >= 100:
+            match show_choices("Payer", "Partir"):
+                case "Payer":
+                    # Take gold (this is stored in the events!)
+                    party.gold -= 100
+                    items[3].count += 1
+                case "Partir":
+                    return
+        else:
+            text("Reviens avec de l'or.")
+        variables[102] += 1
+
+    @page(when=variables[102] >= 1)  # the active page: the last one whose condition holds
+    def page_2(self):
+        text("Merci encore !")
+        Ulysse.page_1()  # runs Ulysse's page 1 (Call Event)
+
+
+@event(11, "Ulysse", x=10, y=42)
+class Ulysse(Event):  # The other event!
+    sprite = ("heroes1", 0)
+    layer = "same"
+
+    def page_1(self):
+        pass
+```
+
+Every command, option and value is typed and documented in
+[`rpgsync/dsl.py`](https://github.com/oulianov/rpgsync/blob/master/rpgsync/dsl.py): your
+editor shows the docs on hover and flags wrong values (a misspelled direction, a sprite
+index above 7, ...). [Writing scripts](https://github.com/oulianov/rpgsync/blob/master/docs/scripts.md)
+explains events and pages, variables by name, the database and the map tree.
+
+## Demo
+
+A Doom-like 3d game in RPGMaker using only pictures of vertical slices. The tedious, repetitive event code has been automatically generated.
+
+https://github.com/user-attachments/assets/9246ff34-b226-4ebc-b8a3-e55b3adcc5d5
+
+
+## Compatibility
+
+rpgsync works with **RPG Maker 2000 and 2003** games, both in old versions (1.08) and
+Steam version (1.12a). It was tested on EasyRPG's test suites and on complete games.
+[Learn more.](https://github.com/oulianov/rpgsync/blob/master/Tested_Games.md)
+
+**Supported Patches:** Everything! DynRPG, Maniac Patch, EasyRPG commands, Power Mode
+2003, Ineluki Key Patch... Patches with unknown commands are kept as raw. Patches that
+only change the engine don't matter for this module.
+
+
+## Getting started
+
+### 1. Install uv
+
+rpgsync uses [uv](https://docs.astral.sh/uv/) to manage Python:
+
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
+```
+
+(Windows: `powershell -c "irm https://astral.sh/uv/install.ps1 | iex"`)
+
+### 2. Install rpgsync
+
+```bash
+uv tool install rpgsync
+```
+
+This puts the `rpgsync` command on your PATH.
+
+### 3. Set up your game
+
+Run rpgsync in your game folder (the one containing `RPG_RT.ldb`):
+
+```bash
+cd /path/to/MyGame
+rpgsync
+```
+
+The first time, it asks, then writes your maps, database and common events as Python
+scripts in `Scripts/`, with tests and their own Python environment. It then keeps the
+game and the scripts in sync until Ctrl+C.
+
+Open the `Scripts` folder in your editor and select its `.venv` as the Python
+interpreter. You're seeing your Python clone!
+
+If the game is in git, commit `Scripts/` with it, `pyproject.toml` and `uv.lock`
+included: they pin the rpgsync version of the game (see
+[Sharing a game](#sharing-a-game)). Its `.gitignore` leaves out `.venv/` and rpgsync's
+own files (`.rpgsync/`).
+
+
+## Everyday use
+
+```bash
+rpgsync           # keep the game and the scripts in sync, until Ctrl+C
+rpgsync status    # what is pending, on which side
+rpgsync pull      # game -> scripts
+rpgsync push      # scripts -> game
+rpgsync check     # compile and check the scripts (types too), write nothing
+rpgsync clean     # delete the backups of overwritten files
+```
+
+- A command works on the game of the current folder (the game's or `Scripts/`), or of
+  the folder given: `rpgsync status /path/to/MyGame`.
+- `--map N` limits a command to one map. `check` also takes scripts and folders:
+  `rpgsync check Map0004.py database`.
+- `pull --force` overwrites scripts that have unsynced edits; `push --force` writes
+  every script, not only those changed since the last sync.
+- `rpgsync locate --map 4 --event 12` prints where the scripts write an event
+  (`FILE:LINE`).
+- `rpgsync COMMAND --help` lists a command's options.
+
+### With the EasyRPG Editor
+
+> [!TIP]
+> **The EasyRPG Editor is the recommended editor to use with rpgsync.** It stays open
+> while rpgsync runs, and merges your Python edits with the changes you make in it.
+
+In the [EasyRPG Editor](https://github.com/oulianov/Editor), turn on **rpgsync mode**
+(Settings). The Editor reloads the changes made on disk and shows them as well as it
+can, so it can stay open while `rpgsync` runs. When both sides change the same game,
+it merges what each changed and only asks when the same entry changed on both sides.
+
+### With the RPG Maker 2000/2003 editor
+
+```bash
+rpgsync pull     # game -> scripts
+# edit the Python files
+rpgsync push     # scripts -> game
+```
+
+then open the editor and keep editing there.
+
+> [!WARNING]
+> **Keep the RPG Maker editor closed while you edit the Python files.**
+> The editor keeps its own copy of your game in memory and ignores your Python
+> edits: its next save (a map, the database, or quitting) writes that copy back
+> over them.
+
+### Play-test with EasyRPG Player
+
+[EasyRPG Player](https://easyrpg.org/player/) runs RPG Maker 2000/2003 games on
+Windows, macOS, Linux and more, and is the quickest way to test your changes: start
+the game, play, quit, edit, start again.
+
+### Will this break my project?
+
+rpgsync is built so that **it should not**. If anything, you can always go back.
+
+- **Invalid scripts are never written.** A typo, a wrong value or a RPG Maker 2003
+  command in a 2000 game stops at the
+  [checks](https://github.com/oulianov/rpgsync/blob/master/docs/checks.md).
+- **Every overwritten file is backed up** (game files and scripts) in
+  `Scripts/.rpgsync/history/`, the last 50 syncs. `rpgsync clean` deletes them once
+  you no longer need them.
+- Only what you changed is written.
+- If the same event changed on both sides, the editor's version is kept and your
+  script is saved next to it as `MapXXXX.conflict-<time>.py` (in one file, for a
+  script split in files).
+
+Using git on the game folder and doing backups is still a good idea.
+
+
+## Sharing a game
+
+`Scripts/pyproject.toml` depends on the rpgsync release that set the game up
+(`rpgsync~=0.1.0`), and `Scripts/uv.lock` pins its exact version. Whoever clones the
+game runs that version, in `Scripts/`:
+
+```bash
+uv sync           # install the game's rpgsync, and the scripts' tools
+uv run rpgsync    # run it
+```
+
+A CI job does the same: `uv sync --locked`, then `uv run --locked rpgsync ...`.
+
+
+## Upgrading rpgsync
+
+The `rpgsync` command:
+
+```bash
+uv tool upgrade rpgsync
+```
+
+A game, in its `Scripts/` folder:
+
+- **A fix release** (0.1.0 → 0.1.3) writes the same scripts:
+
+  ```bash
+  uv sync --upgrade-package rpgsync
+  ```
+
+  then commit `uv.lock`.
+- **A new minor version** (0.1.x → 0.2.0) writes the scripts differently. With
+  nothing pending (`rpgsync status`):
+
+  ```bash
+  uv add "rpgsync~=0.2.0"
+  uv run rpgsync pull --force
+  ```
+
+  then commit `pyproject.toml`, `uv.lock` and the rewritten scripts together.
+
+[CHANGELOG.md](https://github.com/oulianov/rpgsync/blob/master/CHANGELOG.md) lists
+what each version changes. An `rpgsync` command newer than a game's version would
+rewrite its scripts in the newer format: on a game you don't upgrade yet, use
+`uv run rpgsync` in its `Scripts/`.
+
+
+## Learn more
+
+- [Writing scripts](https://github.com/oulianov/rpgsync/blob/master/docs/scripts.md):
+  events and pages, variables and switches by name, the database, the map tree, big
+  scripts as folders
+- [Checks and tests](https://github.com/oulianov/rpgsync/blob/master/docs/checks.md):
+  `rpgsync check`, the scripts' tests, resource files
+- [DynRPG and DynParams](https://github.com/oulianov/rpgsync/blob/master/docs/dynrpg.md):
+  plugin calls, and a variable wherever RPG Maker takes a number
+- [Patches](https://github.com/oulianov/rpgsync/blob/master/Patches.md): how each patch
+  shows in the scripts, and their settings
+- [Tested games](https://github.com/oulianov/rpgsync/blob/master/Tested_Games.md)
+- [Working on rpgsync](https://github.com/oulianov/rpgsync/blob/master/docs/development.md):
+  use your own rpgsync in a game, run its tests, release it
+- [Changelog](https://github.com/oulianov/rpgsync/blob/master/CHANGELOG.md)
+
+
+## License
+
+MIT, 2026: see [LICENSE](https://github.com/oulianov/rpgsync/blob/master/LICENSE). Source: https://github.com/oulianov/rpgsync

rpgsync-0.1.0/pyproject.toml

@@ -0,0 +1,95 @@
+[project]
+name = "rpgsync"
+version = "0.1.0"
+description = "A Python twin of your RPG Maker 2000/2003 game"
+readme = "README.md"
+license = "MIT"
+keywords = [
+    "rpg-maker",
+    "rpg-maker-2000",
+    "rpg-maker-2003",
+    "easyrpg",
+    "gamedev",
+    "dsl",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: 3.15",
+    "Topic :: Games/Entertainment :: Role-Playing",
+    "Topic :: Software Development :: Code Generators",
+    "Typing :: Typed",
+]
+requires-python = ">=3.11"
+dependencies = [
+    "pydantic>=2.14.0",
+    "rich>=15.0.0",
+    "ruff>=0.16.10",
+    "typer>=0.27.3",
+]
+
+[[project.authors]]
+name = "Nicolas Oulianov"
+
+[project.urls]
+Homepage = "https://github.com/oulianov/rpgsync"
+Repository = "https://github.com/oulianov/rpgsync"
+Issues = "https://github.com/oulianov/rpgsync/issues"
+Changelog = "https://github.com/oulianov/rpgsync/blob/master/CHANGELOG.md"
+
+[project.scripts]
+rpgsync = "rpgsync.cli:main"
+
+[build-system]
+requires = ["uv_build>=0.9,<0.14"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+module-root = ""
+source-include = [
+    "LICENSE",
+    "CHANGELOG.md",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-n auto"
+
+[tool.ruff]
+line-length = 120
+extend-exclude = [
+    "rpgsync/dbschema.py",
+    "rpgsync/db.py",
+]
+
+[tool.ruff.lint]
+select = [
+    "E",
+    "F",
+    "W",
+    "I",
+    "UP",
+    "B",
+]
+ignore = [
+    "E501",
+    "UP031",
+    "B008",
+    "B905",
+    "E741",
+]
+
+[dependency-groups]
+dev = [
+    "pytest>=9.1.1",
+    "pytest-xdist>=3.8.0",
+    "ruff>=0.16.10",
+    "ty>=0.0.85",
+]