> For the complete documentation index, see [llms.txt](/llms.txt)

# GS2-Limit API Reference

Number of times limit feature




Service to realize limit processing

This service is not used alone, but is used in other services to realize the limit function.

A counter is an entity used to represent the number of times a player has acted.
The count limit is achieved by a mechanism that specifies the maximum acceptable value when raising the counter and attempting to count up; if the maximum value would be exceeded, the count-up fails, causing subsequent processing to fail as well.
A distinctive feature is that there is no maximum value on the counter itself; rather, the maximum is set on each count-up action.

For example, consider the process of recovering stamina.
In many games there is an upper limit on how many times per day stamina can be recovered.
And the more you recover, the higher the amount of money required for the recovery becomes.

By using `anchorTimestamp`, flexible scheduling such as resetting every N days from an event start date is possible.

By integrating with GS2-Buff, you can use buffs to adjust the `maxValue` of `CountUp`/`CountUpByUserId`, temporarily increasing or decreasing the upper limit.
This is useful when implementing event-based easing measures such as "for a limited time, double the number of gacha pulls allowed per day".

[Introduction to Microservices / GS2-Limit](../../microservices/limit)



- [GS2-Limit Buff Reference](/api_reference/limit/buff/)
  
- [GS2-Limit Deploy/CDK Reference](/api_reference/limit/deploy/)
  
- [GS2-Limit Master Data Reference](/api_reference/limit/master_data/)
  
- [GS2-Limit Script Trigger Reference](/api_reference/limit/script/)
  
- [GS2-Limit SDK API Reference](/api_reference/limit/sdk/)
  
- [GS2-Limit SDK for Game Engine API Reference](/api_reference/limit/game_engine/)
  
- [GS2-Limit Transaction Actions](/api_reference/limit/stamp_sheet/)