Leaderboard Merger - Revision history

Matt: /* Configuration file */

2025-12-16T12:46:38Z

Configuration file

← Older revision		Revision as of 14:46, 16 December 2025
Line 54:		Line 54:
	=== Configuration file ===		=== Configuration file ===

	File <code>Data/serials.json</code> is required.		Notice: As of 2025-12-16, the configuration file can only be created and deployed by the producer. Operator-side configuration tools are still under development.

			File <code>Data/serials.json</code> is required for operation in the Global scenario. It defines the list of arcade machine serial numbers whose leaderboard data will be collected and merged.

	Example content of the file:		Example content of the file:

Matt: /* Configuration file */

2025-12-16T12:43:22Z

Configuration file

← Older revision		Revision as of 14:43, 16 December 2025
Line 54:		Line 54:
	=== Configuration file ===		=== Configuration file ===

	~~TODO~~		File <code>Data/serials.json</code> is required.

			Example content of the file:

			{
			"_version": 1,
			"serials": [
			"1111222233334444",
			"5555666677778888"
			]
			}

	=== Access Point Mode ===		=== Access Point Mode ===

Matt at 12:34, 16 December 2025

2025-12-16T12:34:00Z

← Older revision		Revision as of 14:34, 16 December 2025
Line 20:		Line 20:
	* No internet connection is required.		* No internet connection is required.
	* All devices must be in the same WLAN.		* All devices must be in the same WLAN.
	* Data refresh interval is 5 seconds.		* Data refresh interval is '''5 seconds'''.
	* This mode is recommended for on‑site installations such as arcades, bars, or live events.		* This mode is recommended for on‑site installations such as arcades, bars, or live events.

Line 41:		Line 41:
	* Data is retrieved via a remote server		* Data is retrieved via a remote server
	* Configuration file with machine serial numbers is required		* Configuration file with machine serial numbers is required
	* Data refresh interval is 60 seconds		* Data refresh interval is '''60 seconds'''
	* This mode is suitable for aggregating leaderboards from geographically distributed locations		* This mode is suitable for aggregating leaderboards from geographically distributed locations

Matt: /* Connection Scenarios */

2025-12-16T12:14:31Z

Connection Scenarios

@@ Line 28: / Line 28: @@
 * Event-based setups
 * Temporary locations without internet access
 === Global Scenario ===
@@ Line 59: / Line 49: @@
 * Distributed tournaments
 * Global or regional rankings

Matt at 12:11, 16 December 2025

2025-12-16T12:11:04Z

← Older revision		Revision as of 14:11, 16 December 2025
Line 10:		Line 10:
	* Global		* Global

	Each scenario defines how the device communicates with arcade machines and how frequently the ~~data~~ is refreshed.		Each scenario defines how the device communicates with arcade machines, how the data is obtained, and how frequently the leaderboard is refreshed.

	=== Local Scenario ===		=== Local Scenario ===

	In the local scenario, the Leaderboard Merger and all arcade machines must be connected to the same local wireless network (WLAN).		In the local scenario, the Leaderboard Merger and all arcade machines must be connected to the same local wireless network (WLAN).

			Key characteristics:

	* No internet connection is required.		* No internet connection is required.
	* Data refresh interval is 5 seconds.		* All devices must be in the same WLAN.
	* This mode is recommended for on‑site installations such as arcades, bars, or events.		* Data refresh interval is 5 seconds.
	* Typical use cases: ~~single~~ venue~~, event installation, temporary~~ locations without internet access		* This mode is recommended for on‑site installations such as arcades, bars, or live events.

			Typical use cases:

			* Single venue installations
			* Event-based setups
			* Temporary locations without internet access

			==== Access Point Mode ====

			If no existing WLAN is available at the location, the Leaderboard Merger can be configured to create its own wireless access point.

			In this setup:

	~~Notice: If no existing WLAN is available at the location, the Leaderboard Merger can be configured to create its own wireless access point. In this setup:~~
	* Leaderboard Merger acts as the Wi‑Fi access point		* Leaderboard Merger acts as the Wi‑Fi access point
	* Arcade machines connect directly to this network		* Arcade machines connect directly to this network
			* No external network infrastructure is required

	=== Global Scenario ===		=== Global Scenario ===
Line 29:		Line 43:
	In the global scenario, the Leaderboard Merger and arcade machines communicate over the internet.		In the global scenario, the Leaderboard Merger and arcade machines communicate over the internet.

	In this ~~scenario~~ Leaderboard Merger requires a configuration file containing a list of machine serial numbers. Only machines listed in this file will be queried for leaderboard data. This ~~mechanism~~ allows precise control over which machines participate in the merged leaderboard (for example: machines ~~located in~~ a ~~single~~ venue, ~~hall~~, or event ~~zone~~).		In this mode, the Leaderboard Merger requires a configuration file containing a list of machine serial numbers. Only machines listed in this file will be queried for leaderboard data. This allows precise control over which machines participate in the merged leaderboard (for example: machines belonging to a specific venue, region, or event).

	Key characteristics:		Key characteristics:

	* Each device connects to an internet‑enabled WLAN.		* Each device connects to an internet‑enabled WLAN
	* Devices do not need to be on the same local network.		* Devices do not need to be on the same local network
	* Data is retrieved via remote server.		* Data is retrieved via a remote server
	* Configuration file is required.		* Configuration file with machine serial numbers is required
	* Data refresh interval is 60 seconds.		* Data refresh interval is 60 seconds
	* This mode is suitable for aggregating leaderboards from geographically distributed locations.		* This mode is suitable for aggregating leaderboards from geographically distributed locations
	* Typical use cases: ~~chain~~ locations~~, distributed~~ tournaments~~, global~~ or regional rankings.
			Typical use cases:

			* Chain locations
			* Distributed tournaments
			* Global or regional rankings

Matt: /* Global Scenario */

2025-12-16T12:02:26Z

Global Scenario

← Older revision		Revision as of 14:02, 16 December 2025
Line 29:		Line 29:
	In the global scenario, the Leaderboard Merger and arcade machines communicate over the internet.		In the global scenario, the Leaderboard Merger and arcade machines communicate over the internet.

	In this scenario Leaderboard Merger requires a configuration file containing a list of machine serial numbers. Only machines listed in this file will be queried for leaderboard data.		In this scenario Leaderboard Merger requires a configuration file containing a list of machine serial numbers. Only machines listed in this file will be queried for leaderboard data. This mechanism allows precise control over which machines participate in the merged leaderboard (for example: machines located in a single venue, hall, or event zone).
	This mechanism allows precise control over which machines participate in the merged leaderboard (for example: machines located in a single venue, hall, or event zone).

	Key characteristics:		Key characteristics:

Matt at 12:01, 16 December 2025

2025-12-16T12:01:30Z

← Older revision		Revision as of 14:01, 16 December 2025
Line 2:		Line 2:

	The device operates independently from the arcade machines and periodically synchronizes data according to the selected connection scenario.		The device operates independently from the arcade machines and periodically synchronizes data according to the selected connection scenario.

	~~== Machine List Configuration ==~~

	~~Leaderboard Merger requires a configuration file containing a list of machine serial numbers. Only machines listed in this file will be queried for leaderboard data.~~
	~~This mechanism allows precise control over which machines participate in the merged leaderboard (for example: machines located in a single venue, hall, or event zone).~~

	== Connection Scenarios ==		== Connection Scenarios ==
Line 21:		Line 16:
	In the local scenario, the Leaderboard Merger and all arcade machines must be connected to the same local wireless network (WLAN).		In the local scenario, the Leaderboard Merger and all arcade machines must be connected to the same local wireless network (WLAN).

	* No internet connection is required		* No internet connection is required.
	* Data refresh interval is 5 seconds.		* Data refresh interval is 5 seconds.
	* This mode is recommended for on‑site installations such as arcades, bars, or events.		* This mode is recommended for on‑site installations such as arcades, bars, or events.
Line 33:		Line 28:

	In the global scenario, the Leaderboard Merger and arcade machines communicate over the internet.		In the global scenario, the Leaderboard Merger and arcade machines communicate over the internet.

			In this scenario Leaderboard Merger requires a configuration file containing a list of machine serial numbers. Only machines listed in this file will be queried for leaderboard data.
			This mechanism allows precise control over which machines participate in the merged leaderboard (for example: machines located in a single venue, hall, or event zone).

	Key characteristics:		Key characteristics:

	* Each device connects to an internet‑enabled WLAN		* Each device connects to an internet‑enabled WLAN.
	* Devices do not need to be on the same local network		* Devices do not need to be on the same local network.
	* Data is retrieved via remote ~~servers~~		* Data is retrieved via remote server.
			* Configuration file is required.
	* Data refresh interval is 60 seconds.		* Data refresh interval is 60 seconds.
	* This mode is suitable for aggregating leaderboards from geographically distributed locations.		* This mode is suitable for aggregating leaderboards from geographically distributed locations.
	* Typical use cases: chain locations, distributed tournaments, global or regional rankings		* Typical use cases: chain locations, distributed tournaments, global or regional rankings.

Matt at 11:46, 16 December 2025

2025-12-16T11:46:19Z

← Older revision		Revision as of 13:46, 16 December 2025
Line 1:		Line 1:
	Leaderboard Merger is a standalone hardware device responsible for collecting leaderboard data from a defined set of ~~boxer~~ machines, merging those results into a single ranking, and presenting the combined leaderboard on its own display.		Leaderboard Merger is a standalone hardware device responsible for collecting leaderboard data from a defined set of arcade machines, merging those results into a single ranking, and presenting the combined leaderboard on its own display.

	The device operates independently from the ~~boxer~~ machines and periodically synchronizes data according to the selected connection scenario.		The device operates independently from the arcade machines and periodically synchronizes data according to the selected connection scenario.

	== Machine List Configuration ==		== Machine List Configuration ==
Line 15:		Line 15:
	* Global		* Global

	Each scenario defines how the device communicates with ~~boxer~~ machines and how frequently the data is refreshed.		Each scenario defines how the device communicates with arcade machines and how frequently the data is refreshed.

	=== Local Scenario ===		=== Local Scenario ===

	In the local scenario, the Leaderboard Merger and all ~~boxer~~ machines must be connected to the same local wireless network (WLAN).		In the local scenario, the Leaderboard Merger and all arcade machines must be connected to the same local wireless network (WLAN).

	* No internet connection is required		* No internet connection is required
Line 28:		Line 28:
	Notice: If no existing WLAN is available at the location, the Leaderboard Merger can be configured to create its own wireless access point. In this setup:		Notice: If no existing WLAN is available at the location, the Leaderboard Merger can be configured to create its own wireless access point. In this setup:
	* Leaderboard Merger acts as the Wi‑Fi access point		* Leaderboard Merger acts as the Wi‑Fi access point
	* ~~Boxer~~ machines connect directly to this network		* Arcade machines connect directly to this network

	=== Global Scenario ===		=== Global Scenario ===

	In the global scenario, the Leaderboard Merger and ~~boxer~~ machines communicate over the internet.		In the global scenario, the Leaderboard Merger and arcade machines communicate over the internet.

	Key characteristics:		Key characteristics:

Matt: Created page with "Leaderboard Merger is a standalone hardware device responsible for collecting leaderboard data from a defined set of boxer machines, merging those results into a single ranking, and presenting the combined leaderboard on its own display. The device operates independently from the boxer machines and periodically synchronizes data according to the selected connection scenario. == Machine List Configuration == Leaderboard Merger requires a configuration file containing a..."

2025-12-16T11:42:18Z

Created page with "Leaderboard Merger is a standalone hardware device responsible for collecting leaderboard data from a defined set of boxer machines, merging those results into a single ranking, and presenting the combined leaderboard on its own display. The device operates independently from the boxer machines and periodically synchronizes data according to the selected connection scenario. == Machine List Configuration == Leaderboard Merger requires a configuration file containing a..."

New page

Leaderboard Merger is a standalone hardware device responsible for collecting leaderboard data from a defined set of boxer machines, merging those results into a single ranking, and presenting the combined leaderboard on its own display.

The device operates independently from the boxer machines and periodically synchronizes data according to the selected connection scenario.

== Machine List Configuration ==

Leaderboard Merger requires a configuration file containing a list of machine serial numbers. Only machines listed in this file will be queried for leaderboard data.
This mechanism allows precise control over which machines participate in the merged leaderboard (for example: machines located in a single venue, hall, or event zone).

== Connection Scenarios ==

Leaderboard Merger supports two operating modes:

* Local
* Global

Each scenario defines how the device communicates with boxer machines and how frequently the data is refreshed.

=== Local Scenario ===

In the local scenario, the Leaderboard Merger and all boxer machines must be connected to the same local wireless network (WLAN).

* No internet connection is required
* Data refresh interval is 5 seconds.
* This mode is recommended for on‑site installations such as arcades, bars, or events.
* Typical use cases: single venue, event installation, temporary locations without internet access

Notice: If no existing WLAN is available at the location, the Leaderboard Merger can be configured to create its own wireless access point. In this setup:
* Leaderboard Merger acts as the Wi‑Fi access point
* Boxer machines connect directly to this network

=== Global Scenario ===

In the global scenario, the Leaderboard Merger and boxer machines communicate over the internet.

Key characteristics:

* Each device connects to an internet‑enabled WLAN
* Devices do not need to be on the same local network
* Data is retrieved via remote servers
* Data refresh interval is 60 seconds.
* This mode is suitable for aggregating leaderboards from geographically distributed locations.
* Typical use cases: chain locations, distributed tournaments, global or regional rankings