GS2-MegaField API Reference

Efficient player position synchronization in large 3D spaces

This service is designed to hold the location data of over 100,000 players and update it up to 5 times per second to share with other players.

A Namespace can consist of multiple areas, with one area consisting of multiple layers. For spaces where players do not clearly intersect, it is recommended to divide the area and separate layers for each type of player and drop items, etc. If you want to place drop items or enemies in a space, you need to prepare a separate daemon to manage their status.

The only data this service can share is the three-dimensional position, the three-dimensional vector representing the orientation, and the radius of interest. No other data can be shared. If you want to share other data, please consider combining other GS2 services.

This service is extremely communication-intensive. Sending location information 3 times per second generates approximately 10,000 communications per hour, which costs more than USD 2. Even if you are considering using the Individual plan, if the average number of requests per month exceeds 10 requests, you will be excluded from the plan and will not be able to use the service. Please note that if you send your location 3 times per second, you will fall under the exclusion if you have an average of 3.3 people online.


GS2-MegaField SDK for Game Engine API Reference

Specifications of models and API references for GS2-MegaField SDK for Game Engine

GS2-MegaField SDK API Reference

Specification of models and API references for GS2-MegaField SDK for various programming languages

GS2-MegaField Deploy/CDK Reference

The template format used when creating stacks with GS2-Deploy, and implementation examples of template output in various languages using CDK

GS2-MegaField Master Data Reference

Reference for the master data format and the models to be imported