Feature request: Update and expand the MQTT messaging system to be properly connected to the events happening in server and send messages to the clients.

[BillTheBeast]

What do you want to see in the API?

My understanding is that there is an MQTT system implemented in the server for sending update messages to the clients that has made some time back.

This also has some documentation about the potential topics/endpoints to connect to this system in the GitHub wiki pages.

I would like to see the Messages shown there to be checked and updated as needed so that they can actually be used by the client.

This is the order in which the topics should be made available:

1. Voting and JukeBox topics.

• These should have most of the related base work already completed in serverside and should easily be usable in testing this.
• Voting
  • New poll is created.
  • New vote is added to the poll
  • Poll ends.
• Jukebox
  • Jukebox playlist changes.

2. DailyTask (Whenever DailyTask API is finished/updated properly.)

• Task state advances.
• Task completes.
• Other players task completes.
• Milestone is reached.

3. Changes to the clan status

• Player joins or leaves the clan.
• Clan base info is updated.

4. Stock status

• If furniture are bought or gained through various mains.
• Furniture is bought from the clans stall (Ie. it no longer belongs to the clan.)

5. SoulHome (Whenever soulhome API updates are ready.)

• TBA

6. Friend status and requests

• New requests are sent.
• Request is accepted or declined.

7. Match invites

• Should include a new endpoint where this invite is sent to server which then handles the delivery to the correct player.

[tickBit]

I finished today (28.5.2026) Voting and jukebox topics part.

The work is in the branch related to the issue.

[tickBit]

I finished today (3.6.2026) the DailyTask part of the issue.

Locally all the tests regarding the DailyTask part are green.

Edit: The work is in the related branch.

Edit 2: Some documentation of the implementation:

Shared result for daily task update:

• DailyTaskProgressResult
  • status: 'advanced' | 'completed'
  • task
  • completedByPlayerId
  • clanId
  • completedAmount
  • previousAmountLeft
  • currentAmountLeft`
  • reachedMilestones?: number[]

Method               | MQTT topic path                                   | Description                                    | Payload
-------------------------------------------------------------------------------------------------------------------------------------------
taskReceived         | /player/{player_id}/daily_task/{task_type}/new    | Player got new daily task.                     | TTask
taskUpdated          | /player/{player_id}/daily_task/{task_type}/update | Daily task was advanced (some part of a task). | TTask
taskError            | /player/{player_id}/daily_task/{task_type}/error  | Error in task.                                 | APIError
taskCompleted        | /player/{player_id}/daily_task/{task_type}/end    | Player completed a task.                       | TTask
taskCompletedForClan | /clan/{clan_id}/daily_task/{task_type}/end        | Member of a clan completed a clan's task       | { task: TTask, completedByPlayerId: string }`
milestoneReached     | /clan/{clan_id}/daily_task/milestone/update       | A clan achieved new milestone                  | { task: TTask, completedByPlayerId: string, reachedMilestones: number[] }

[tickBit]

I fixed today two broken test files to DailyTask part. Somehow I didn't notice those earlier.
Work is in the related branch.

[tickBit]

I finished today (5.6.2026) the Changes to the clan status part of the issue.
Work is in the related branch.

Edit: Some documentation:

MQTT topic path is in the form /clan/{clanId}/member/{join|leave}/{new|update}

Payload consists of playerId and event info.

In the code join topic for MQTT is implemented in the following way:

memberJoin(clanId: string, playerId: string) {
    const topic = `/clan/${clanId}/member/join`;
    NotificationSender.buildNotification()
      .addGroup(this.group, clanId)
      .addResource(this.resource, 'join')
      .send(NotificationStatus.NEW, {
        topic,
        playerId,
        event: 'join',
        ts: Date.now(),
      });
  }

[tickBit]

With reference to today's meeting, part 7 of this issue could be implemented after part 3, followed by the others in order.
Currently parts 1-3 are implemented and a PR has been made of their implementation.