University-of-Basel-Studentprojects/Programmierprojekt
Archived
1
0
Fork 0
Code Issues 17 Pull Requests Actions Wiki Activity

Add serverside STATUS-command #43

New Issue
Closed
opened 2026-04-01 13:48:14 +02:00 by lars.winzer · 7 comments
lars.winzer commented 2026-04-01 13:48:14 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

Task

Summary

Adds parsers and handlers relevant to get the status of the server for displaying it to the server.

Context

CommandParser, Request, CommandHandler and StatusResponse

Current Progress

  • StatusCommandParser
  • StatusRequest
  • StatusCommandHandler
  • StatusResponse

Notes

Request

STATUS

Response

The exact context still needs to be discussed, but it should contain general informations about the server and its overall state:

  • Current player count
  • Current active running games
  • Current active games that have not started yet
  • And other aspects relevant to the user

Checklist

  • I outlined checkpoints describing phases of my work related to this task
  • I added relevant labels
  • I linked to other issues or branches that must be completed first
## Task <!--The reccommended type is: Task--> ### Summary Adds parsers and handlers relevant to get the status of the server for displaying it to the server. ### Context CommandParser, Request, CommandHandler and StatusResponse ### Current Progress - [ ] StatusCommandParser - [ ] StatusRequest - [ ] StatusCommandHandler - [ ] StatusResponse ### Notes #### Request ``` STATUS ``` #### Response The exact context still needs to be discussed, but it should contain general informations about the server and its overall state: * Current player count * Current active running games * Current active games that have not started yet * And other aspects relevant to the user ### Checklist - [x] I outlined checkpoints describing phases of my work related to this task - [x] I added relevant labels - [x] I linked to other issues or branches that must be completed first
lars.winzer commented 2026-04-01 13:48:23 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

marked this task as related to #37

marked this task as related to #37
lars.winzer commented 2026-04-01 13:48:28 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

marked the checklist item I linked to other issues or branches that must be completed first as completed

marked the checklist item **I linked to other issues or branches that must be completed first** as completed
lars.winzer commented 2026-04-07 12:23:16 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

removed the relation with #37

removed the relation with #37
lars.winzer commented 2026-04-07 12:24:45 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

Moved this task to %"Milestone 5" as this command is part of another feature I have in mind.

Its not required for this ( %"Milestone 4" ) milestone.

Moved this task to %"Milestone 5" as this command is part of another feature I have in mind. Its not required for this ( %"Milestone 4" ) milestone.
lars.winzer commented 2026-04-07 12:24:56 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

mentioned in task #37

mentioned in task #37
lars.winzer commented 2026-04-27 01:12:06 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

Task will be moved to Milestone 6

Task will be moved to Milestone 6
lars.winzer commented 2026-05-17 10:40:12 +02:00 (Migrated from git.scicore.unibas.ch)
Copy Link
Copy Source

This command would have been used in combination with the advertisement of the server in the local network, due to limited time of my team members, this will not be finished.

This command would have been used in combination with the advertisement of the server in the local network, due to limited time of my team members, this will not be finished.
lars.winzer (Migrated from git.scicore.unibas.ch) closed this issue 2026-05-17 10:40:12 +02:00
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
achievement
Tasks related to milestone achievements
 bug
Issues related to programming errors on both client and server
 ci
Issues related to problems with the gitlab ci (incorrect or missing jobs)
 client
Issues (To-Dos and tasks) related to the client
 commands
Issues and tasks related to commands and thier infrastructure (CommandHandler, CommandParser, ...)
 documentation
Issues related to the documentation (for new or unclear, incorrect or incomplete entries)
 enhancement
Issues related to enhancements (also known as feature-requests)
 game-engine
Issues related to the game engine (incorrect state transitions or move validations)
 linting
Issues related to linting i.e. false detections, too generous linting, ...
 messages
Issues and tasks related to the messages and chats
 network
Issues and tasks related to the network (SessionReader / SessionWriter, Parser, ResponseBody, ...)
 outreach
Issues and tasks related to the outreach website and everything directly related to it
 server
Issues (To-Dos and tasks) related to the server
 task
Issues outlining and discussing a general task or implementation
 templates
Issues related to GitLab templates
 ui
Issues and tasks related to the client-side ui
 unit-test
Issues related to missing or already planned unit tests
 user
Issues and tasks related to the user management
No Label network server task
Milestone
No items
No Milestone Milestone 6
Assignees
Clear assignees
lars-winzer (Lars Winzer)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: University-of-Basel-Studentprojects/Programmierprojekt#43
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?