Game Server Go issueshttps://gitlab.akamu.de/akamu/game-server-go/-/issues2020-12-29T15:33:49+01:00https://gitlab.akamu.de/akamu/game-server-go/-/issues/48Add generic feedback endpoint2020-12-29T15:33:49+01:00Julien SchröterAdd generic feedback endpointEndpoint will send an email to a configured feedback email address.
Username/UserID can be fetched from **optional** session-token.Endpoint will send an email to a configured feedback email address.
Username/UserID can be fetched from **optional** session-token.Julien SchröterJulien Schröterhttps://gitlab.akamu.de/akamu/game-server-go/-/issues/37Allow titles to be unlocked by title.unlock_win2020-12-29T15:41:28+01:00Julien SchröterAllow titles to be unlocked by title.unlock_winThe field `unlock_win` defines the count of questions to answer correctly answered questions of a subject for unlocking the title.
Partially correctly answered questions such as swipe questions are not counted as correctly answered in t...The field `unlock_win` defines the count of questions to answer correctly answered questions of a subject for unlocking the title.
Partially correctly answered questions such as swipe questions are not counted as correctly answered in the sense of `unlock_win`.Julien SchröterJulien Schröterhttps://gitlab.akamu.de/akamu/game-server-go/-/issues/25Get Single Title Object Endpoint2020-07-14T17:53:01+02:00Maurice KrausGet Single Title Object EndpointTo be consistent with the rest of the endpoints (duel, round, user, #24)) and since the iOS app would really benefit from it, it would make sense to have such an endpoint to fetch a single title with id=x `GET /title?id=1`.To be consistent with the rest of the endpoints (duel, round, user, #24)) and since the iOS app would really benefit from it, it would make sense to have such an endpoint to fetch a single title with id=x `GET /title?id=1`.https://gitlab.akamu.de/akamu/game-server-go/-/issues/24Get Single Avatar Object Endpoint2020-07-14T17:53:01+02:00Maurice KrausGet Single Avatar Object EndpointTo be consistent with the rest of the endpoints (duel, round, user, #25) and since the iOS app would really benefit from it, it would make sense to have such an endpoint to fetch a single avatar with id=x `GET /avatar?id=1`.To be consistent with the rest of the endpoints (duel, round, user, #25) and since the iOS app would really benefit from it, it would make sense to have such an endpoint to fetch a single avatar with id=x `GET /avatar?id=1`.https://gitlab.akamu.de/akamu/game-server-go/-/issues/71Enable invited users to discard duel2024-01-11T12:22:00+01:00Julien SchröterEnable invited users to discard duelSet `running`=0Set `running`=0https://gitlab.akamu.de/akamu/game-server-go/-/issues/70Duel answer 500 on repeated answer submit2023-02-02T16:28:08+01:00Frederik WegnerDuel answer 500 on repeated answer submit![akamu-gameserver-log-duel-answer-500](/uploads/4ac64056c896e6cc2be7a463d940d546/akamu-gameserver-log-duel-answer-500.png)
Log from the dev server.
Multiple duel/answer requests for the same question were submitted before and may be th...![akamu-gameserver-log-duel-answer-500](/uploads/4ac64056c896e6cc2be7a463d940d546/akamu-gameserver-log-duel-answer-500.png)
Log from the dev server.
Multiple duel/answer requests for the same question were submitted before and may be the cause for the issue.
In any case the server should not return 500.Julien SchröterJulien Schröterhttps://gitlab.akamu.de/akamu/game-server-go/-/issues/69Wrong api spec /duel/pool, remove field 'selected'2022-04-28T17:19:27+02:00Frederik WegnerWrong api spec /duel/pool, remove field 'selected'The field 'selected' is not and should not be returned by /duel/pool.
'selected' should be removed from the /duel/pool spec.The field 'selected' is not and should not be returned by /duel/pool.
'selected' should be removed from the /duel/pool spec.https://gitlab.akamu.de/akamu/game-server-go/-/issues/68Real Friend feature2022-04-05T14:19:17+02:00Frederik WegnerReal Friend featureA friendship should be agreed upon by both parties involved. Currently the 'friend' relation is unidirectional.A friendship should be agreed upon by both parties involved. Currently the 'friend' relation is unidirectional.1.4.0-previewFrederik WegnerFrederik Wegnerhttps://gitlab.akamu.de/akamu/game-server-go/-/issues/67Get users of pool2022-02-15T19:35:33+01:00Frederik WegnerGet users of poolTo start a duel coming from a pool selection, we need a list of users that have this pool selected too, so we can send them the request.To start a duel coming from a pool selection, we need a list of users that have this pool selected too, so we can send them the request.1.4.0-previewhttps://gitlab.akamu.de/akamu/game-server-go/-/issues/66Open a duel request with a preset pool2022-02-15T19:33:54+01:00Frederik WegnerOpen a duel request with a preset poolThe new app has a flow where a duel is started coming from a pool selection.
To make this possible the duel request needs to contain the previously selected pool.The new app has a flow where a duel is started coming from a pool selection.
To make this possible the duel request needs to contain the previously selected pool.1.4.0-preview2022-02-28https://gitlab.akamu.de/akamu/game-server-go/-/issues/65database error upon set/unset pool2022-02-15T19:22:48+01:00Frederik Wegnerdatabase error upon set/unset pool1.3.2-previewFrederik WegnerFrederik Wegner2022-02-19https://gitlab.akamu.de/akamu/game-server-go/-/issues/60Enable creation of random duels2021-03-23T19:15:54+01:00Julien SchröterEnable creation of random duelsImplement ability to create a duel against a random user.
The creating user should play a round of this duel before trying to match the duel to another user. This is proposed in order to guarantee users the ability to play a duel when op...Implement ability to create a duel against a random user.
The creating user should play a round of this duel before trying to match the duel to another user. This is proposed in order to guarantee users the ability to play a duel when opening the app.
Duels should be matched to other users using the "random-duel" feature. Make sure that both players have at least 1 pool in common.
Note: Since questions can be assigned to universities but pools can't, it's not enough to check if users have pools in common, but you also have to check that pools have >=2 questions both users can access. You may use https://gitlab.akamu.de/akamu/game-server-go/-/blob/development/endpoint/pool/query.go#L831.4.0-previewMax GranzowMax Granzowhttps://gitlab.akamu.de/akamu/game-server-go/-/issues/56Remove /user/all endpoint2021-01-07T18:29:56+01:00Julien SchröterRemove /user/all endpoint1.4.0-previewhttps://gitlab.akamu.de/akamu/game-server-go/-/issues/53Duel submit answer endpoint api spec inconsistent. Field useranswer.2020-12-29T17:37:52+01:00Frederik WegnerDuel submit answer endpoint api spec inconsistent. Field useranswer.https://gitlab.akamu.de/akamu/game-server-go/-/issues/21Add logout endpoint2020-12-29T15:42:41+01:00Julien SchröterAdd logout endpointCreate a logout endpoint invalidating the session and removing the firebase-token.
Since firebase-tokens are assigned to a specific device, not a specific user, users (B) may receive other users (A) push notifications after logging out ...Create a logout endpoint invalidating the session and removing the firebase-token.
Since firebase-tokens are assigned to a specific device, not a specific user, users (B) may receive other users (A) push notifications after logging out from account A and logging in with account B.
Calling this this logout endpoint will prevent user B receiving user A's push notifications even though the firebase-token has not been changed.https://gitlab.akamu.de/akamu/game-server-go/-/issues/19End sessions after password has been changed2020-09-08T17:55:14+02:00Julien SchröterEnd sessions after password has been changedRemove open sessions from session table or invalidate them after a user changed the password in order to get rid of sessions used by potential attackers.
This should not include the session used to change the password.Remove open sessions from session table or invalidate them after a user changed the password in order to get rid of sessions used by potential attackers.
This should not include the session used to change the password.