Minecraft server - Revision history

Azzy: /* Server Architecture and Technology */

2026-01-18T22:04:47Z

Server Architecture and Technology

← Older revision		Revision as of 18:04, 18 January 2026
Line 3:		Line 3:
	== Server Architecture and Technology ==		== Server Architecture and Technology ==
	{{See also\|Name of page=Player}}		{{See also\|Name of page=Player}}
	Inferris employs a hybrid data management approach, using a REST API~~-based microservice architecture~~ for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:~~MySQL~~\|~~MySQL~~]] serves as the primary ~~databases~~ for long-term data storage. The ~~servers also~~ maintain a local cache to improve performance. ~~Additionally, inter~~-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.		Inferris employs a hybrid data management approach, using a REST API for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:PostgreSQL\|PostgreSQL]] serves as the primary database for long-term data storage. The Minecraft server plugins maintain a local cache to improve performance. Inter-server [[wikipedia:Publish–subscribe_pattern\|Pub/Sub]] mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.

	=== Frontend ===		=== API ===
			The RESTful API is a Node 24 application written in TypeScript that employs the [[wikipedia:Express.js\|Express]] framework to serve requests to endpoints and managing data layers.

			It leverages both PostgreSQL and Redis databases to achieve its design goals. Of note, the API uses domain-driven design (DDD) as a major design pattern to benefit from bounded contexts and other derived principals related to domains, invariants, and guardrails inside the models.

			A non-exhaustive list of dependencies or libraries include, but is not limited to, Kysely (query builder), zod (validation), zod-to-openapi and Swagger UI for OpenAPI integration, ESLint and Prettier, Pino and PinoHTTP, Jest and Supertest for testing and mocks, and Docker.

			=== Frontend plugin ===
	The frontend architecture runs alongside a custom-modified version of [https://papermc.io/software/velocity Velocity], which functions as a proxy server to direct requests to the appropriate backend servers. When a player connects to the server, the plugin interacts with the API, which queries the Redis service. If no keys are found, it defaults to retrieving data from the databases. Once data is obtained from either source, the plugin generates and caches the new player data, then submits it via a POST request to the API for storage in both the databases and Redis. When this happens, the backend server, such as the lobby, is already well aware of such event and has already locally cached the needed data.		The frontend architecture runs alongside a custom-modified version of [https://papermc.io/software/velocity Velocity], which functions as a proxy server to direct requests to the appropriate backend servers. When a player connects to the server, the plugin interacts with the API, which queries the Redis service. If no keys are found, it defaults to retrieving data from the databases. Once data is obtained from either source, the plugin generates and caches the new player data, then submits it via a POST request to the API for storage in both the databases and Redis. When this happens, the backend server, such as the lobby, is already well aware of such event and has already locally cached the needed data.

	=== Backend ===		=== Backend plugin ===
	The backend plugins manage the playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot. The backend, like the frontend's capabilities, is capable of updating a player's data and transmitting the update to the proxy server plugin, which it then can locally cache to stay up to date. The transmission happens when the API receives a payload within the request body, representing the request server ID, to create a line trace of where the request should head while utilizing a publish–subscribe pattern to alert other instances to grab the new batch of data.		The backend plugins manage the playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot. The backend, like the frontend's capabilities, is capable of updating a player's data and transmitting the update to the proxy server plugin, which it then can locally cache to stay up to date. The transmission happens when the API receives a payload within the request body, representing the request server ID, to create a line trace of where the request should head while utilizing a publish–subscribe pattern to alert other instances to grab the new batch of data.

Azzy: /* Frontend */

2024-09-08T03:09:56Z

Frontend

← Older revision		Revision as of 23:09, 7 September 2024
Line 3:		Line 3:
	== Server Architecture and Technology ==		== Server Architecture and Technology ==
	{{See also\|Name of page=Player}}		{{See also\|Name of page=Player}}
	Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL ~~database~~]] serves as the primary ~~database~~ for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.		Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL]] serves as the primary databases for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.

	=== Frontend ===		=== Frontend ===
	The frontend architecture runs alongside a custom-modified version of [https://papermc.io/software/velocity Velocity], which functions as a proxy server to direct requests to the appropriate backend servers. When a player connects to the server, the plugin interacts with the API, which queries the Redis service. If no keys are found, it defaults to retrieving data from the ~~MySQL database~~. Once data is obtained from either source, the plugin generates and caches the new player data, then submits it via a POST request to the API for storage in both the ~~database~~ and Redis. When this happens, the backend server, such as the lobby, is already well aware of such event and has already locally cached the needed data.		The frontend architecture runs alongside a custom-modified version of [https://papermc.io/software/velocity Velocity], which functions as a proxy server to direct requests to the appropriate backend servers. When a player connects to the server, the plugin interacts with the API, which queries the Redis service. If no keys are found, it defaults to retrieving data from the databases. Once data is obtained from either source, the plugin generates and caches the new player data, then submits it via a POST request to the API for storage in both the databases and Redis. When this happens, the backend server, such as the lobby, is already well aware of such event and has already locally cached the needed data.

	=== Backend ===		=== Backend ===

Azzy: /* Backend */

2024-09-08T03:07:07Z

Backend

← Older revision		Revision as of 23:07, 7 September 2024
Line 10:		Line 10:
	=== Backend ===		=== Backend ===
	The backend plugins manage the playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot. The backend, like the frontend's capabilities, is capable of updating a player's data and transmitting the update to the proxy server plugin, which it then can locally cache to stay up to date. The transmission happens when the API receives a payload within the request body, representing the request server ID, to create a line trace of where the request should head while utilizing a publish–subscribe pattern to alert other instances to grab the new batch of data.		The backend plugins manage the playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot. The backend, like the frontend's capabilities, is capable of updating a player's data and transmitting the update to the proxy server plugin, which it then can locally cache to stay up to date. The transmission happens when the API receives a payload within the request body, representing the request server ID, to create a line trace of where the request should head while utilizing a publish–subscribe pattern to alert other instances to grab the new batch of data.

			The "Inferris" plugin is deployed across all backend servers, with its features, or modules, being dynamically enabled or disabled based on specific configurations and conditions. Primary modules include the display of player ranks and the activation of lobby mode. Additionally, each server has a unique blacklisted commands file. The plugin also supports chat logging for moderation, as well as configurable spawn settings, such as location, radius, and minimum/maximum height. It also manages API, Redis, and database connections for seamless integration.

	== Planned Features and Gameplay ==		== Planned Features and Gameplay ==

Azzy: Removed "actual"

2024-09-08T02:57:12Z

Removed "actual"

← Older revision		Revision as of 22:57, 7 September 2024
Line 9:		Line 9:

	=== Backend ===		=== Backend ===
	The backend plugins manage the ~~actual~~ playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot. The backend, like the frontend's capabilities, is capable of updating a player's data and transmitting the update to the proxy server plugin, which it then can locally cache to stay up to date. The transmission happens when the API receives a payload within the request body, representing the request server ID, to create a line trace of where the request should head while utilizing a publish–subscribe pattern to alert other instances to grab the new batch of data.		The backend plugins manage the playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot. The backend, like the frontend's capabilities, is capable of updating a player's data and transmitting the update to the proxy server plugin, which it then can locally cache to stay up to date. The transmission happens when the API receives a payload within the request body, representing the request server ID, to create a line trace of where the request should head while utilizing a publish–subscribe pattern to alert other instances to grab the new batch of data.

	== Planned Features and Gameplay ==		== Planned Features and Gameplay ==

Azzy: Reworded a few lines, clarified we now use a custom Velocity build

2024-09-08T02:56:19Z

Reworded a few lines, clarified we now use a custom Velocity build

← Older revision		Revision as of 22:56, 7 September 2024
Line 6:		Line 6:

	=== Frontend ===		=== Frontend ===
	The frontend architecture runs ~~on the~~ [~~[wikipedia~~:~~Proxy_server\|proxy server]~~], which ~~acts~~ as a ~~gateway, directing~~ requests to the appropriate backend ~~server~~. When a player connects to the server, the plugin interacts with the API, which queries the Redis service. If no keys are found, it defaults to retrieving data from the MySQL database. Once data is obtained from either source, the plugin generates and caches the new player data, then submits it via a POST request to the API for storage in both the database and Redis.		The frontend architecture runs alongside a custom-modified version of [https://papermc.io/software/velocity Velocity], which functions as a proxy server to direct requests to the appropriate backend servers. When a player connects to the server, the plugin interacts with the API, which queries the Redis service. If no keys are found, it defaults to retrieving data from the MySQL database. Once data is obtained from either source, the plugin generates and caches the new player data, then submits it via a POST request to the API for storage in both the database and Redis. When this happens, the backend server, such as the lobby, is already well aware of such event and has already locally cached the needed data.

	~~[https://papermc.io/software/velocity Velocity]~~ is ~~currently used to for~~ the ~~proxy's software~~.

	=== Backend ===		=== Backend ===
	The backend plugins manage the actual playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot.		The backend plugins manage the actual playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot. The backend, like the frontend's capabilities, is capable of updating a player's data and transmitting the update to the proxy server plugin, which it then can locally cache to stay up to date. The transmission happens when the API receives a payload within the request body, representing the request server ID, to create a line trace of where the request should head while utilizing a publish–subscribe pattern to alert other instances to grab the new batch of data.

	== Planned Features and Gameplay ==		== Planned Features and Gameplay ==
Line 23:		Line 21:

	==== Mini-games ====		==== Mini-games ====
	The mini-games server is currently in development. ~~We plan~~ to offer a variety of mini-games, including team-based and solo PvP options. In addition to traditional PvP, we will try to offer a range of cooperative mini-games that require teamwork and strategy. Our goal is to create a unique and enjoyable experience, free from toxicity, where our community can relax and have fun together.		The mini-games server is currently in development. Inferris plans to offer a variety of mini-games, including team-based and solo PvP options. In addition to traditional PvP, we will try to offer a range of cooperative mini-games that require teamwork and strategy. Our goal is to create a unique and enjoyable experience, free from toxicity, where our community can relax and have fun together.

	==== Survival ====		==== Survival ====
	The survival server is in the concept phase, aiming to offer a unique experience beyond traditional vanilla gameplay. [[User:Azzy\|Azzy]] is exploring features such as player home points, public warp points, player-owned shops, and an in-game economy, all powered by custom-built ~~plugins~~. Community feedback will play a crucial role in shaping the server's final direction, ensuring it aligns with the desires of the players.		The survival server is in the concept phase, aiming to offer a unique experience beyond traditional vanilla gameplay. [[User:Azzy\|Azzy]] is exploring features such as player home points, public warp points, player-owned shops, and an in-game economy, all powered by custom-built plugin systems. Community feedback will play a crucial role in shaping the server's final direction, ensuring it aligns with the desires of the players.

	== Development ==		== Development ==
	The development officially started some time in May of 2023, although its original concepts date back much earlier through different plugin iterations.		The development officially started some time in '''May of 2023''', although its original concepts date back much earlier through different plugin iterations.

Azzy: /* Frontend */

2024-09-06T02:31:49Z

Frontend

← Older revision		Revision as of 22:31, 5 September 2024
Line 4:		Line 4:
	{{See also\|Name of page=Player}}		{{See also\|Name of page=Player}}
	Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.		Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.

			=== Frontend ===
			The frontend architecture runs on the [[wikipedia:Proxy_server\|proxy server]], which acts as a gateway, directing requests to the appropriate backend server. When a player connects to the server, the plugin interacts with the API, which queries the Redis service. If no keys are found, it defaults to retrieving data from the MySQL database. Once data is obtained from either source, the plugin generates and caches the new player data, then submits it via a POST request to the API for storage in both the database and Redis.

			[https://papermc.io/software/velocity Velocity] is currently used to for the proxy's software.

	=== Backend ===		=== Backend ===
	The backend ~~plugin, which runs on~~ the ~~[[wikipedia:Proxy_server\|proxy server]]~~, ~~handles most of the API calls. When a player connects to the server~~, the plugin interacts with the API which queries the Redis service, and if no keys exist, it falls back to the MySQL database. Subsequentially, if data is present in either service, the plugin generates and caches the new player data, and feeds it to a "POST" request so that the API can store the in the database and ~~on Redis. [https://papermc.io/software/velocity Velocity] is currently used to act as a proxy.~~		The backend plugins manage the actual playable environments, or worlds, and operate on [https://papermc.io/software/paper Paper]'s server software, a performant-optimized fork of Spigot.

	~~=== Frontend ===~~
	~~The frontend plugins run~~ on [https://papermc.io/software/paper Paper], a ~~highly~~ optimized fork of Spigot, and they are the actual playable environments. The frontend plugins are designed to receive data from the backend, and, if needed, send data to the backend; this approach is highly useful to limit API requests.

	== Planned Features and Gameplay ==		== Planned Features and Gameplay ==

Azzy: /* Server Architecture and Technology */

2024-09-06T02:12:08Z

Server Architecture and Technology

← Older revision		Revision as of 22:12, 5 September 2024
Line 3:		Line 3:
	== Server Architecture and Technology ==		== Server Architecture and Technology ==
	{{See also\|Name of page=Player}}		{{See also\|Name of page=Player}}

	Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.		Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.

Azzy: /* Server Architecture and Technology */

2024-09-06T02:10:41Z

Server Architecture and Technology

← Older revision		Revision as of 22:10, 5 September 2024
Line 2:		Line 2:

	== Server Architecture and Technology ==		== Server Architecture and Technology ==
	{{See also\|Name of page=~~<nowiki>[[~~Player~~]</nowiki>~~}}		{{See also\|Name of page=Player}}

	Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.		Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.

Azzy: /* Server Architecture and Technology */

2024-09-06T02:10:18Z

Server Architecture and Technology

← Older revision		Revision as of 22:10, 5 September 2024
Line 2:		Line 2:

	== Server Architecture and Technology ==		== Server Architecture and Technology ==
	{{See also\|Name of page=Player ~~Data~~}}		{{See also\|Name of page=<nowiki>[[Player]</nowiki>}}

	Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.		Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.

Azzy: /* Server Architecture and Technology */

2024-09-06T02:04:17Z

Server Architecture and Technology

← Older revision		Revision as of 22:04, 5 September 2024
Line 2:		Line 2:

	== Server Architecture and Technology ==		== Server Architecture and Technology ==
			{{See also\|Name of page=Player Data}}

	Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.		Inferris employs a hybrid data management approach, using a REST API-based microservice architecture for data retrieval, updates, and management. [[wikipedia:Redis\|Redis]] is leveraged for fast access and temporary (TTL) storage, while [[wikipedia:MySQL\|MySQL database]] serves as the primary database for long-term data storage. The servers also maintain a local cache to improve performance. Additionally, inter-server Pub/Sub mechanisms are used to enable efficient communication between instances, ensuring that backend and frontend components stay synchronized by updating local data in real-time.