/tags/tech/ Recent content in Tech on Game Server Services | Docs Hugo en /articles/tech/error/pattern/ Mon, 01 Jan 0001 00:00:00 +0000 /articles/tech/error/pattern/ In network feature implementation using GS2, error handling directly impacts game stability and user experience (UX). Here are some practical implementation patterns that go beyond simple exception catching. 1. Error Classification and Handling Policy GS2 exceptions can be broadly classified into three categories based on their nature. Category Applicable Exceptions (Example) Handling Policy Transient Errors InternalServerError, ServiceUnavailable, RequestTimeout Automatic Retry. If it fails after several attempts, display an error dialog. Logic/Configuration Errors BadRequest, NotFound Errors to be resolved during development. /articles/tech/cache/ Mon, 01 Jan 0001 00:00:00 +0000 /articles/tech/cache/ The GS2 game-engine SDKs (GS2 SDK for Unity, GS2 SDK for Unreal Engine, and so on) have a built-in cache that keeps data fetched from the server inside the SDK. Understanding this cache helps you reduce the number of API calls and improves both responsiveness and cost. Basic behavior When you fetch data through a Domain object (an access pattern such as gs2.Inventory.Namespace(...).Me(...).Inventory(...)), the fetched data is stored in the SDK’s internal cache. /articles/tech/cost/ Mon, 01 Jan 0001 00:00:00 +0000 /articles/tech/cost/ Since GS2 uses a pay-as-you-go pricing model, usage fees can vary significantly depending on the game’s design. This section explains key design points to keep costs down while maintaining performance. 1. Reduction of API Call Count A large portion of GS2 fees is determined by the number of API requests. Utilize SDK Caching Mechanism The GS2 SDK has a built-in caching mechanism. When the same data is retrieved multiple times in a short period, it is designed to return the data from the cache without sending a request to the server.