Architectural Summary: Unity → PHP API → MySQL

The core architecture of Battlestrike is built on a structure that clearly separates the client (Unity) and the server side. While the Unity client manages the visual/interaction layer of the game, user data, sessions, purchases, and competitive systems are controlled by the API on the server side.

Briefly, the flow works like this:

1. Unity client initiates a process (login, match result, purchase, etc.).
2. The request goes to the relevant endpoint on the PHP API.
3. The API applies authentication, authorization, and validation steps.
4. Necessary data is read/written via MySQL.
5. The result returns to Unity and is reflected to the user on the client side.

This structure is important for both ease of maintenance and security. In a competitive game, it is risky to make critical decisions (ranking, rewards, bans, etc.) on the client side; therefore, the "rules" of the business reside on the server.

What does the API layer manage?

All operations such as player registration, login, ranking, purchases, and the ban system pass through this API layer. Thus, a single "source of truth" is created for in-game processes, and inconsistencies are prevented.

• Registration & login: User creation, session management, token generation, device verification.
• Player profile: Inventory, cosmetics, progress data, statistics.
• Ranking system: Processing match results, score calculation, seasonal data.
• Purchases: Transaction verification, recording, adding to inventory, and rollback flows in case of potential errors.
• Ban / moderation: Rule violation detection, ban durations, appeal mechanism (in later stages).
• Logging & monitoring: System logs and metrics for fast diagnosis of issues.

The goal here is to make critical in-game operations secure while keeping them fast and stable. Even the slightest delay on the mobile player side disrupts the "feel"; therefore, performance is our primary criterion in endpoint design.

One structure, multiple channels: Game + admin panel + website

The same API infrastructure is used not only by the Unity client but also by the management panel and the official website. This choice provides us with three major advantages:

• Consistency: The game and the panel process the same data with the same rules. Problems like "what appears on the panel is different from what appears in the game" are reduced.
• Operational speed: We can move faster in live operations (seasonal settings, content management, balancing parameters).
• Ease of maintenance: While developing a new feature, a capability added to the API can be integrated into both the game and the web/panel.

Security & performance approach

Requests from Unity are processed through endpoints designed with a focus on security and performance. At this point, specifically:

• Authorization: Every request is authenticated; critical operations are not left to the client.
• Validation: Sent data is checked (incomplete, incorrect, manipulated data is blocked).
• Rate limiting logic: Protection against abuse and attack attempts (we will detail this in later stages).
• Optimized queries: Correct indexes and fast query design on the MySQL side.
• Cache / fast response: Strategies to reduce latency for frequently used data (to be implemented as needed).

Each of these headings is critical for closing vulnerabilities that could create an "unfair advantage" in a competitive game and for keeping the player experience stable.

What will we share on this blog?

Under the heading of Battlestrike Technical Infrastructure, we will share more technical articles from time to time. We want to produce practical content that will benefit developers, not just "general ideas."

• Database schema: Role of tables, relationships, sample data flows.
• API endpoint samples: Request/response formats, error management, sample scenarios.
• Unity integration samples: Token management, async request structures, retry strategies.
• Security notes: Client manipulation, core protection approaches, practical measures.
• Sample scenes: Especially demo scenes and code snippets for Unity developers.

We specifically plan to prepare detailed documentation and sample scenes for Unity developers. In this way, a more sustainable development process will be created for our own team, and players/developers with technical curiosity in the community will be able to see a clearer picture.