Skip to content

Feature request: Implement daily task RECYCLING_EXPERIENCES #976

Description

@tickBit

What do you want to see in the API?

Add server-side daily task progress tracking for RECYCLING_EXPERIENCES.

The task should progress when a player successfully adds a clan item to the flea market after it has already been approved for sale through clan voting.

Player-facing task instruction in Finnish:

Avaa klaanin kirpputori. Valitse äänestyksessä myytäväksi hyväksytty tavara ja lisää se myytäväksi. Katso, miten muut reagoivat ja miltä tuntuu kun tavara alkaa liikkua pelaajien välillä.

How do you think this should work?

When a player successfully lists an approved clan item on the flea market, the backend should emit a daily task event for:

ServerTaskName.RECYCLING_EXPERIENCES

The task should only progress after the flea market item has been created/listed successfully. If validation, permission checks, approval checks, or item creation fails, the daily task must not progress.

Expected behavior:

  • The task progresses only for the player who lists the item.
  • The item must belong to the player’s current clan.
  • The item must have already passed the clan sell-item voting flow.
  • 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 listing an approved item for sale, not proposing an item for sale and not voting in an existing vote.

Any additional info?

This should stay separate from related voting/flea market daily tasks:

  • LETTING_GO_OF_THE_OLD = propose an item for sale and start the sell-item voting
  • YOUR_VOICE = vote in an existing clan voting

ServerTaskName.RECYCLING_EXPERIENCES already exists in the server task enum, but it may still need to be added to generated server task types and title generation.

Check the daily task generation and startup refresh logic. RECYCLING_EXPERIENCES 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature to add

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions