We bring you useful information and news from Hive! Greetings from Hive Platform!
During game service operations, various policy violations may occur, including abusive language, exploiting, and the use of unauthorized programs.
If responses to such violations are delayed or applied inconsistently, it can reduce service trust and increase operational risk and administrative burden.
What matters is responding quickly and consistently based on defined policies, and establishing an operational environment where enforcement processes can be managed efficiently.
In this Insight, we introduce the Hive Suspension feature, covering everything from defining enforcement criteria to applying actions and reflecting them on the game server. |
|
|
π‘οΈ Consistent Standards, Efficient Enforcement |
|
|
1. Register Suspension Types |
|
|
Each game has different acceptable standards and operational policies.
Even for the same violation, the guidance method and display format may vary depending on the nature of the game.
With the "Register Suspension Type" feature, you can predefine enforcement categories and display messages tailored to your game. |
|
|
β Use Cases
- Since abusive chat and in-game exploiting differ in nature, you can configure separate notification messages for each type.
- When clear guidance based on operational policy is required, you can use the fixed-format "Operational Policy Restriction" pop-up that displays the CS code and suspension period.
- When flexible messaging is needed depending on the situation, you can choose the "Temporary Restriction" pop-up, which allows you to freely set the title and message.
|
|
|
2. Register Suspended Users |
|
|
Once enforcement types are defined,
operations must allow adjustment of enforcement levels based on the severity and history of violations.
The "Register Suspended User" feature
enables you to set enforcement scopes that scale from individual users to large groups.
β Use Cases
- You can apply the suspension level and duration based on the user's past enforcement history.
- In addition to suspending individual users, you can restrict access based on IP address.
- Instead of applying an immediate suspension, you can first send a warning message to encourage behavioral change.
- By uploading a CSV file, you can apply actions in bulk for up to 200,000 cases, enabling rapid response to large-scale issues.
|
|
|
3. Exclude Suspended Users from the Service |
|
|
In addition to blocking gameplay through suspension, the user's records must also be prevented from affecting the game service.
By using the Suspended User Information Delivery API, the game can receive suspended user data in real time from the Hive Console and apply it to the game service.
β Use Cases
- You can immediately exclude suspended users from rankings, events, and season rewards.
- In matchmaking, you can prevent them from entering the matchmaking queue or ensure their PvP records and competitive results are not reflected.
|
|
|
π― Benefits of Using Hive Services |
|
|
βοΈ Predefine Suspension Types
Predefined enforcement types and notification messages help establish clear policy standards. |
|
|
βοΈ Respond to Large-Scale Issues
Bulk enforcement and automatic release allow fast response to major incidents. |
|
|
βοΈ Service Integration
Suspended users can be excluded from game rankings and matchmaking targets. |
|
|
βοΈ Transparent Enforcement History Management
All enforcement actions are recorded and can be used as a basis for operational decisions. |
|
|
Com2us Platform
cs-platform@com2us.com
131, Gasan digital 1-ro, Geumcheon-gu, Seoul, Korea
Β© Com2uS Platform Corp. All Rights Reserved
This email is for informational purposes to guide service usage.
If you no longer wish to receive emails, please click here to unsubscribe.
|
|
|
|
