Packs
You have spent hours building a repertoire, putting together a set of exercises, collecting annotated games. A pack lets you hand all of it over at once, in a single file, to a student or a whole team.
The file carries the .regence extension. Whoever receives it double-clicks, and Régence shows them what is about to happen before anything is written.
Creating a pack
File > Create a pack… opens the composer.
It follows your own filing rather than imposing its own: three tabs — studies, exercises, games — with your folders on the left. Ticking a folder takes everything in it.
Two buttons save you from ticking boxes one by one:
| Button | What it does |
|---|---|
| Select all / Deselect all | Across the whole tab |
| Select only what the list shows | Respects your search and filters |
Your folder tree travels with the file: it is rebuilt identically for whoever installs it. So are your tags.
There is a shortcut for the most common case: the context menu of a study folder offers Create a pack from this folder…, and that of an exercise set Create a pack from this set…. The pack comes pre-filled.
Before saving, a few fields describe the pack: a title, a description, your author name and an optional link to your site or club. They are shown to whoever installs it.
Installing a pack
A double-click on the file is enough. Otherwise: File > Import > Install a pack…
The install screen announces, item by item, what it is about to do:
| Verdict | What it means | What happens |
|---|---|---|
| New | You don’t have it | Installed |
| Update | The author published a newer version | The content is replaced |
| Unchanged | You already have it, as is | Nothing moves |
| Modified by you | You have edited it since | Nothing moves, you are asked |
The last case is the only one that asks a question — and the most important one. You annotated the study, added a variation, fixed a line. Three choices:
- Keep my version — the pack skips that item. This is the default.
- Take the pack’s version — overwrites, after explicit confirmation.
- Install alongside — both coexist, the new one suffixed “(pack)”.
[!IMPORTANT] When in doubt, Régence does not destroy. A pack update that wiped a student’s work is the kind of accident you never recover from — so your version wins until you say otherwise.
What an update never touches
Even on a clean update, four things belong to you and stay put:
- Your progress in training — the spaced-repetition boxes stay where they are;
- The tags you added — the pack’s tags are added to yours, they don’t replace them;
- The folder you filed the item in — if you moved it, you meant to;
- Analyses already computed — they are expensive to redo.
A pack tag with the same name as one of yours merges into it: you won’t end up with two “Beginner”.
Republishing an update
Fixed a line, added three exercises? Reopen the composer and choose Republish an update.
Régence recognises the items already published and sends only what actually changed. Your students get the correction without the rest of their work being touched.
Worth knowing
- The format is deliberately easy to produce. An external tool can build a valid pack without knowing anything about Régence.
- A pack that brings nothing tells you so: “You already have everything in this pack — there is nothing to install.”
- If an item in the file is unreadable, it is set aside and named, rather than failing the whole installation.