/categories/knowledge/engagement/ Recent content in Knowledge/Engagement on Game Server Services | Docs Hugo en /design_knowledge/success/anniversary_event/ Mon, 01 Jan 0001 00:00:00 +0000 /design_knowledge/success/anniversary_event/ If you are celebrating the first anniversary of the launch of a game, the 100th day, or even the 2.5(!?) anniversary of a game, celebrate it as soon as you can. If there is a good time to celebrate, celebrate it actively. At these times, we can offer various initiatives such as “special login bonuses”, “10 free gacha draws every day”, “halving the stamina required to progress in quests”, “doubling the amount of experience gained” and so on. /design_knowledge/success/bring_change_game_every_week/ Mon, 01 Jan 0001 00:00:00 +0000 /design_knowledge/success/bring_change_game_every_week/ While it is important to have a system that changes every day to create a routine, weekly changes are also important to keep people playing the game for a year. Nevertheless, there are games that have cycles of a week or more. It is also important to consider how often the changes can be made in a way that fits with the development resources available, and then design the game accordingly. /design_knowledge/success/dont_play_too_much/ Mon, 01 Jan 0001 00:00:00 +0000 /design_knowledge/success/dont_play_too_much/ In order to get players to play for a long period of time, it is better not to let them play too much in a short period of time. Unlimited play will not only widen the gap between long-time players and short-time players, but also If the game is allowed unlimited play, it will not only widen the gap between long-time players and short-time players, but it will also make it necessary to listen to two voices: one from long-time players asking for something to be done about the lack of content, and one from short-time players asking for something other than lack of content. /design_knowledge/success/make_days_of_week_uniqueness/ Mon, 01 Jan 0001 00:00:00 +0000 /design_knowledge/success/make_days_of_week_uniqueness/ To encourage people to play every day of the week, it is effective to make it meaningful to play tomorrow instead of today. A good example of this would be “day-of-week quests”. On Mondays, there are “wind materials” and on Tuesdays, “fire materials”. Tuesday: “Materials for Fire” Wednesday: “Materials for Water” Thursday: “Materials for Ground” Friday: “In-game currency” Saturday: “Materials for Dark” Sunday: “Materials for Light” In this way, quests are prepared for each day of the week, and the rewards for these quests are materials for training characters with specific attributes. /design_knowledge/success/require_passage_of_time/ Mon, 01 Jan 0001 00:00:00 +0000 /design_knowledge/success/require_passage_of_time/ This feature is often implemented in games under a name such as “expedition”. This is an element that rewards the quests by waiting for real time to elapse, rather than in-game success or failure. By making it so that players are rewarded after 12 hours of starting a quest, a play cycle can be created in which players log in once a morning and once a night, or even once a day. /design_knowledge/success/time_limited_quest/ Mon, 01 Jan 0001 00:00:00 +0000 /design_knowledge/success/time_limited_quest/ A quest that can be attempted only once every day at a specific time (e.g., from 7:00 PM to 8:00 PM). The reward for this quest should be set to be attractive. It is also useful to combine mobile push notifications to notify players that they can save money if they play the game now. /design_knowledge/success/understand_amount_of_resources/ Mon, 01 Jan 0001 00:00:00 +0000 /design_knowledge/success/understand_amount_of_resources/ Monitor information such as how much of the resources used for training, such as materials and in-game currency, are held by players, and what is the balance between the amount of resources obtained and consumed. If the balance between resource acquisition and consumption is positive, you should consider content that consumes the resource. If the balance of resource availability/consumption is inversely related, you should consider content that emits the resource. However, if the game balance is designed with resources as valuable, it is preferable to leave the amount of emissions as they are, as intended.