What do you want to see in the API?
Add server-side daily task progress tracking for LETTING_GO_OF_THE_OLD.
The task should progress when a player successfully proposes a clan item for sale through the flea market flow and this action starts a clan voting for selling that item.
Task description in Finnish:
Avaa klaanin äänestys. Valitse vaihtoehto ja anna äänesi. Huomaa, miten oma valintasi vaikuttaa yhteiseen päätökseen.
How do you think this should work?
When a player successfully starts a FLEA_MARKET_SELL_ITEM voting, the backend should emit a daily task event for:
ServerTaskName.LETTING_GO_OF_THE_OLD
The task should only progress after the voting has been created successfully. If item validation, permission checks, or voting creation fails, the daily task must not progress.
Expected behavior:
- The task progresses only for the player who proposed the item.
- The item/voting must belong to the player’s current clan.
- The task is server-tracked, not manually completed by the client.
- Completing the task should use the existing daily task completion flow.
- This task should represent starting the “sell this clan item” voting, not voting in an existing vote and not adding an already accepted item to the flea market.
Any additional info?
This should stay separate from related voting/flea market daily tasks:
YOUR_VOICE = vote in an existing clan voting
RECYCLING_EXPERIENCES = add an already accepted item to the flea market
ServerTaskName.LETTING_GO_OF_THE_OLD already exists in the server task enum, but it may still need to be added to generated server task types and title generation.
Also check the daily task generation and startup refresh logic. LETTING_GO_OF_THE_OLD should be available as a generated server-tracked task. It needs to be included in the generated server task type list and in title generation. The startup refresh service may also need the same task type and title support so old daily task pools can be rebuilt consistently.
What do you want to see in the API?
Add server-side daily task progress tracking for
LETTING_GO_OF_THE_OLD.The task should progress when a player successfully proposes a clan item for sale through the flea market flow and this action starts a clan voting for selling that item.
Task description in Finnish:
How do you think this should work?
When a player successfully starts a
FLEA_MARKET_SELL_ITEMvoting, the backend should emit a daily task event for:The task should only progress after the voting has been created successfully. If item validation, permission checks, or voting creation fails, the daily task must not progress.
Expected behavior:
Any additional info?
This should stay separate from related voting/flea market daily tasks:
YOUR_VOICE= vote in an existing clan votingRECYCLING_EXPERIENCES= add an already accepted item to the flea marketServerTaskName.LETTING_GO_OF_THE_OLDalready exists in the server task enum, but it may still need to be added to generated server task types and title generation.Also check the daily task generation and startup refresh logic.
LETTING_GO_OF_THE_OLDshould be available as a generated server-tracked task. It needs to be included in the generated server task type list and in title generation. The startup refresh service may also need the same task type and title support so old daily task pools can be rebuilt consistently.