Official product documentation

Chess-Publisher
User Manual

A detailed guide for organizers and arbiters: installation, tournament setup, player management, pairings, results, standings, Chess-Results, the new Online Tournament Hub beta, Organizer Token access, schedules, regulations, backups and tournament-day operation.

Manual edition 2.0 Current stable release: v1.05.01 Online Tournament Hub: Beta
PlatformWindows 10 / 11

64-bit desktop application with local tournament storage.

Pairing workflowGacrux 1.9.57

Local Swiss Dutch pairing generation with independent verification options.

PublishingLocal-first + optional online

Your tournament remains locally operable even when the Online Hub is unavailable.

01

About this manual

Understand what belongs to the stable desktop core and what belongs to the beta online platform.

Chess-Publisher is a local-first tournament management application. The active tournament is shared across the application tabs, so changing the active event changes the working tournament everywhere in the interface.

The program can be used entirely as a local Windows tournament tool. Online publishing is optional. The classic Chess-Results integration and the new Chess-Publisher Online Tournament Hub are separate publication paths.

Online Hub status: the Chess-Publisher Hub is currently a beta feature. It is being distributed and improved alongside upcoming stable Chess-Publisher updates until the full ecosystem is ready for a final release.
Do not confuse credentials. Organizer Tokens are personal publishing credentials for the Chess-Publisher Hub. Tournament-management credentials are handled by the application for individual tournaments. Never share your Organizer Token publicly.

Main application areas

  • Tournament Setup
  • Lists & Players
  • Pairings and result entry
  • Standings
  • Tournament Schedule
  • Regulations
  • Chess-Results
  • Online Hub (beta builds)
  • DGT Boards
  • Other / Export
02

Installation and first launch

Use the installer for normal use or the portable ZIP for testing and controlled deployments.

Windows installer

  1. Download the latest Windows installer from the official Chess-Publisher site or GitHub Release.
  2. Run the installer and follow the Windows setup steps.
  3. Start Chess-Publisher from its desktop or Start Menu shortcut.
  4. Create a new tournament or open an existing one.

Portable ZIP

  1. Download the correct portable ZIP.
  2. Extract the complete archive to a normal writable folder.
  3. Keep the application, local service, pairing engine and support files together.
  4. Start Chess-Publisher from the extracted folder.
Tournament files: normal tournament data is stored separately from the application in the Chess-Publisher tournament-storage area under the Windows Documents known folder. Updating the application should not replace your normal tournament files.
Never run one isolated executable or script directly from inside the ZIP. Always extract the package first.
03

Interface overview

The active tournament, menus, tabs, Autosave and status information form the normal working environment.

Chess-Publisher Tournament Setup interface
Tournament SetupThe central event configuration workspace.

Title bar and save state

The title area shows the current version and save state. Keep Autosave enabled during normal tournament work unless you have a specific reason to control saves manually.

Files menu

Use Files to create, open, save and close tournaments, access recent tournaments and use supported import/export paths.

Pairings menu

The Pairings menu gives quick access to generation, manual pairing, pairing standings, player status for the next round, round review and related export tools.

Historical rounds: earlier rounds should be treated as tournament history. Review them through Round / History; avoid unnecessary changes after a round has been completed and published.
04

Tournament Setup

Complete the event definition before importing the final player list or generating Round 1.

Create a new event

  1. Choose Files → New Tournament.
  2. Enter the tournament name and core event information.
  3. Select the tournament format, number of rounds and time control.
  4. Complete dates, city, federation and rating information as applicable.
  5. Review schedule and regulations before public publication.
  6. Save the tournament before starting the pairing workflow.

Important fields

FieldPurpose
Tournament NamePublic and internal event name used throughout reports and publishing.
Tournament FormatDefines the competition format. Set it correctly before pairing.
RoundsTotal planned rounds for the event.
Time ControlDisplayed in tournament information and public publication where available.
Start / End DateUsed by event information, schedule and public display.
FIDE Event IDOptional FIDE identifier; also available to the Chess-Results publication path.
Before Round 1: verify format, rounds, time control, dates and rating type. Correct setup is easier before any pairing history exists.
05

Lists & Players

Build the participant list, verify FIDE data and prepare the Starting Rank List.

Chess-Publisher Lists and Players interface
Lists & PlayersImport, search, editing and starting-list preparation.

Import players

The unified Players Import workflow supports organizer formats such as Chess-Results XLSX, registration CSV, Swiss-Manager XML, TRF16/TRF26/TRF(x), TUNx and BAK where supported by the current release.

FIDE data

Use the local FIDE rating database tools to search and complete identity, federation and rating information. Confirm that the selected rating list matches the intended rating type of the event.

Manual entry

Manual entry is useful for late registrations or players missing from an imported list. Enter names consistently and use the FIDE ID when one exists.

Starting Rank List / Resort

Before Round 1, review the final starting order. If players were added after an initial import, use the appropriate re-sort/resort action so the starting numbers reflect the configured ranking rules.

After pairing starts: starting numbers and player identity keys are tournament history. Avoid changing identity information in a way that could break round history.
06

Pairings and result entry

The Pairings tab is the main round-control workspace.

Chess-Publisher Pairings and result entry interface
PairingsGenerate, review and record the round from one workspace.

Generate the next round

  1. Confirm that all required results from the previous round are entered.
  2. Review unavailable players, withdrawals, byes and late-entry status.
  3. Generate the next pairing from the Pairings tab or Pairings menu.
  4. Review board order, colors and player status.
  5. Use independent validation tools when required by your workflow.
  6. Publish only after the arbiter has accepted the pairing.

Enter results

Record results in the current editable round. A completed result immediately becomes part of the tournament history used by subsequent standings and pairing preparation.

Public Hub behavior

On the new Chess-Publisher public platform there is no separate Results tab. Pairings includes the results: the same board row shows the players, board number and result. The selected round can also display its matching date/time information from the published Tournament Schedule.

Pairing search: the public Pairings view includes search so visitors can quickly find a player, federation, board, rating, FIDE ID or visible result in the selected round.
07

Standings and tie-breaks

Review rankings after completed rounds and before final publication.

The Standings tab displays current/final ranking data, points and configured tie-break values. Tie-break order should match the tournament regulations.

Independent tie-break validation

The optional Gacrux/FIDE Tie-Break Checker is independent from pairing generation. Use it to validate completed-round ranking output without changing the tournament's pairing logic.

Public standings

When the tournament is published to the Hub, all tie-break columns contained in the published snapshot can be displayed to spectators. The Hub does not calculate tie-breaks itself; it displays the values produced by Chess-Publisher.

Exports and prizes

Use the available final-standings, TXT/PDF and FIDE rating exports as appropriate. Special-prize/category tools should be reviewed against the official tournament regulations before prizes are awarded.

08

Tournament Schedule

Publish a clear timetable for players and spectators.

Chess-Publisher Tournament Schedule
Tournament ScheduleRound times and event-program information.

Enter dates, times and descriptions for registration, opening, rounds, prize ceremony and other event activities. Keep naming consistent, especially for entries such as Round 1, Round 2 and so on.

Online Hub: when a public visitor selects a round in Pairings, the Hub can match that round with the corresponding Round entry in the current Schedule and show the date/time information above the pairing table.

Update the schedule before publishing if round times change. A later Hub publish updates the public event snapshot.

09

Regulations

Keep the public rules and organizer information attached to the event.

Tournament Setup can include structured regulations information such as entry fee, registration deadline, maximum players, FIDE information, prize fund, main prizes, special/category prizes and additional regulations.

Regulations file

Beta builds with Online Hub support can upload a regulations attachment from Tournament Setup / Additional Regulations or the Online Hub area. The supported Hub workflow accepts a file up to 20 MiB and preserves Unicode/Cyrillic filenames.

After a successful regulations-file upload, the current Hub workflow publishes the latest Regulations, Schedule and attachment metadata so the public page can expose the updated file without requiring a separate second publication step.

Check the public page after upload. Confirm that the Regulations tab shows both the structured information and the expected attachment before you distribute the tournament link.
10

Chess-Results publishing

The existing Chess-Results workflow remains separate from the Chess-Publisher Online Hub.

Chess-Publisher Chess-Results publishing interface
Chess-ResultsCreate or update the external Chess-Results tournament through the dedicated integration.

Create / publish

Use the Chess-Results tab for the official Chess-Results integration. The Live Publish Log reports the current publication status and helps diagnose failures.

TNR handling

After the tournament is created, Chess-Publisher keeps the returned tournament reference so subsequent publishes update the same Chess-Results event.

Useful actions

  • Open Tournament
  • Open Admin
  • Open Upload Section
  • Open calendar / tournament links where available
Separate systems: a Chess-Results publish and a Chess-Publisher Hub publish are independent. A temporary Hub problem must not prevent normal local tournament work or the established Chess-Results publication workflow.
11

Online Tournament Hub and Organizer Token

How organizer access works during the controlled beta.

Public visitors do not need a token to browse published tournaments. A token is required only for organizers who want to publish and manage their own tournaments through the beta Hub.

Request an Organizer Token

  1. Contact Kyamran Bilyal at kyamranbilyal@gmail.com.
  2. Include your first name and last name.
  3. Optionally include your FIDE ID and club/organization.
  4. You will receive an individual Organizer Token for your own Chess-Publisher installation.
Why controlled access? Organizer Tokens are issued individually during the beta so publishing rights can be managed and abusive or unauthorized publishing can be disabled without affecting normal public viewing.

Activate the token in Chess-Publisher

  1. Open the Online Hub area in a beta build that supports the Hub.
  2. Find Organizer Account.
  3. Paste the Organizer Token into the Organizer Token field.
  4. Press Verify & Save Securely.
  5. After successful verification, the application stores the credential securely for the current Windows user.
Keep it private: the Organizer Token identifies your publishing account. Do not publish it in screenshots, tournament regulations, websites or public chat. If you believe it has been exposed, contact the project owner so it can be revoked and replaced.

What not to enter

Do not enter a tournament-management credential in the Organizer Token field. Per-tournament management credentials are handled by Chess-Publisher as part of the tournament publication workflow.

12

Publish a tournament to the Online Hub

Use the desktop application as the authoritative source; the Hub displays its published snapshot.

Before first publication

  • Verify Tournament Setup
  • Verify player list and starting order
  • Complete current Schedule
  • Review Regulations
  • Enter completed results
  • Review current Standings

First publish

  1. Open the tournament you want to publish.
  2. Open the Online Hub tab.
  3. Confirm your Organizer Token is verified.
  4. Press Publish.
  5. Wait for the Hub log to confirm the public revision was published.
  6. Use the public tournament link to verify the result in a browser.

The first successful publication creates the online tournament identity for that local event. Later publishes update the same Hub tournament rather than creating a new public event each time.

Publish after each important change

Publish again after a new pairing, result batch, standings update, schedule change or regulations update that spectators should see online.

Current beta safeguard: the Hub integration synchronizes the current Tournament Setup fields before building the publication snapshot so recently edited Schedule and Regulations data are included in the publish.

Hub log

Use the Hub log as the first diagnostic source. A successful publication should show a new Hub revision. If an upload or publish fails, do not change pairing or tie-break logic to fix an online transport problem.

Local-first operation: Chess-Publisher continues to operate locally if the Hub is unavailable. The Hub consumes the tournament state and does not calculate your pairings or tie-breaks.
13

How to use the public Chess-Publisher platform

A guide for organizers, players, parents and spectators.

Tournament directory

Open chess-publisher.org/tournaments to browse events published through the Hub. The directory can be searched by tournament, city or federation and filtered by status where available.

Public tournament page

TabWhat visitors see
OverviewEvent summary, current round, player count, format, time control and other published event information.
Starting ListPublished starting order and player information.
PairingsRound selector, board pairings and results in the same view. For a scheduled round, its matching Schedule information appears above the pairing list. Search helps locate a player or board quickly.
StandingsCurrent/final ranking with published points and tie-break columns.
ScheduleThe event program and round times published by the organizer.
RegulationsStructured regulations and, when uploaded, the tournament regulations attachment.

Mobile use

The public Hub is designed for phones as well as desktop browsers. Pairings and standings adapt to smaller screens so players can check a board or result in the tournament hall without needing the desktop application.

What the public platform does not do

The website does not independently generate pairings, change results or calculate tie-breaks. It presents the latest tournament snapshot published by the organizer's Chess-Publisher application.

Share one link: after verifying the public page, distribute the tournament URL to players. They can follow later rounds from the same event page as the organizer publishes new revisions.
14

DGT Boards

Hardware discovery, mapping and diagnostics for DGT e-Boards.

Chess-Publisher DGT Boards diagnostics interface
DGT BoardsDirect serial/USB diagnostics and board mapping foundation.
  1. Connect and power the DGT hardware.
  2. Open the DGT Boards tab.
  3. Enter the expected number of boards if useful.
  4. Press Connect / Detect and review detected Windows/DGT devices.
  5. Use the diagnostic information to verify board mapping and connectivity.
Current scope: the DGT section is a diagnostics/mapping foundation. Do not treat it as an independent source of official tournament results unless a future release explicitly documents that workflow.
15

Other / Export and interoperability

Use exports for reporting, publishing and exchange with other tournament tools.

Telegram

Where configured, publish selected tournament information such as players, pairings, program, regulations and standings to the chosen Telegram channel.

TXT / PDF

Generate organizer-friendly print and PDF outputs for event information, starting lists, schedules, regulations and standings where available.

TRF / Swiss-Manager interoperability

Use the appropriate TRF and supported exchange actions for the specific workflow. A Starting List export before Round 1 is not the same as a full tournament-history export after rounds have been played.

System Log

Use the System Log when diagnosing a reproducible application problem. It is more useful than a generic screenshot when reporting a technical issue.

16

Save, backup and recovery

Protect the event with several independent recovery layers.

Autosave

Keep Autosave enabled during normal tournament operation and use manual Save before critical transitions such as generating or publishing a new round.

Per-tournament storage

Each event is stored in the application's tournament-storage area under Windows Documents, separate from the installed program files.

TRF backup

Where available, automatic/latest TRF backups provide an additional interoperable recovery path.

Complete Backup / Restore

Use the dedicated Backup / Restore tools to create a complete Chess-Publisher backup before major tournament changes or software testing.

Do not rely on only one copy. For important tournaments keep at least one additional copy on another drive or trusted storage location.
17

Recommended tournament-day workflow

A practical end-to-end checklist for a Swiss event.

  1. Open the correct tournament and verify the application version.
  2. Review Tournament Setup: dates, rounds, time control, format, rating type and event identifiers.
  3. Prepare the player list: imports, FIDE data, attendance, late entries and final starting order.
  4. Complete Schedule and Regulations before distributing public links.
  5. Generate Round 1, review and validate it before publication.
  6. Publish through the channels you actually use: local print/PDF, Telegram, Chess-Results and/or Online Hub.
  7. Enter results as games finish and verify the round before generating the next pairing.
  8. Review standings and tie-breaks after each completed round.
  9. Generate the next round only after the previous round state is correct.
  10. Publish the Hub revision after each new pairing/result/standings update that should be public.
  11. Back up the event at suitable checkpoints.
  12. Before prizes, verify final results, standings, tie-break order and special-prize categories.
18

Troubleshooting

Start with the narrowest safe check and keep local tournament logic separate from online transport problems.

ProblemFirst checks
Cannot find a tournamentUse Files → Recent Tournaments or Open Tournament. Confirm the tournament folder still exists under the Chess-Publisher tournament-storage area in Windows Documents.
Pairing will not generateCheck round state, missing results, player availability, byes/withdrawals and the visible pairing log. Do not change the pairing engine merely to fix an unrelated UI or online issue.
Chess-Results publish failsRead the Chess-Results Live Publish Log, verify event data and internet connectivity, then retry only after identifying the cause.
Organizer Token rejectedConfirm you entered the personal Organizer Token exactly, without extra spaces or quotes. If it has been revoked or exposed, contact the project owner for replacement.
Hub publish failsRead the Hub log first. Verify Organizer Token status, internet connection and that the selected tournament is the intended one. Local tournament operation can continue while the Hub issue is investigated.
Regulations not publicConfirm the upload succeeded, a new Hub revision was published and the public Regulations tab is showing the latest revision. Check the attachment after publication.
Public pairing is oldConfirm the latest round was published to the Hub and refresh the public page. The website only shows the most recently published snapshot.
DGT board not detectedCheck Windows device visibility, drivers, cabling and power, then run Connect / Detect again.

When reporting a bug

Include the exact Chess-Publisher version, tournament format, round number, precise steps to reproduce, visible error/status text and the relevant log excerpt. If the issue concerns the public Hub, include the public tournament link but never include your Organizer Token.

19

Contact, support and Organizer Token requests

Direct project contact for organizers, arbiters, access requests and technical feedback.

Requesting an Organizer Token

Email kyamranbilyal@gmail.com with the subject Chess-Publisher Organizer Token Request. Include your first name, last name and, when available, FIDE ID and club/organization.

Organizer access is personal. Each organizer should use their own issued token. Do not reuse another organizer's credential and do not share your token with participants.

For technical support, include the application version, tournament format, round number, exact steps to reproduce and the relevant status/error message. For project updates and release announcements, follow the official Chess-Publisher Telegram channel.

To make a voluntary contribution to the open-source project, see the Support Chess-Publisher page.

Federation tournament directory

The Online Tournament Hub groups public tournaments by federation. Use the federation index or selector on the Tournaments page to open a federation-specific list, for example Bulgaria (BUL). Federation views can be bookmarked and shared through the ?fed=XXX URL parameter.