Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading Overworld scene starts a new web socket connection #448

Open
tkz00 opened this issue May 13, 2024 · 2 comments · May be fixed by #489
Open

Loading Overworld scene starts a new web socket connection #448

tkz00 opened this issue May 13, 2024 · 2 comments · May be fixed by #489
Assignees

Comments

@tkz00
Copy link
Collaborator

tkz00 commented May 13, 2024

Every time the user enters the Overworld scene a new web socket connection is started and a request to the backend for the user is made, this shouldn't be like this, but was implemented this way since it wasn't defined how to update the user data from the backend when a change to it is made, for example when winning a battle, the campaign progress changes on the backend an so should the user data in the client, but there isn't currently a way to update data granularly, that's why a request for the complete user is made, but it shouldn't.

@lotuuu lotuuu added this to the Pre-Alpha - Basic Features milestone May 13, 2024
@ncontinanza ncontinanza self-assigned this May 24, 2024
@ncontinanza
Copy link
Collaborator

In this task let's just focus on the multiple SocketConnection instances, and we'll discuss about the user's data to be sent in a future issue.

@lotuuu lotuuu linked a pull request Jun 11, 2024 that will close this issue
8 tasks
@lotuuu lotuuu assigned lotuuu and unassigned ncontinanza Jun 11, 2024
@lotuuu
Copy link
Collaborator

lotuuu commented Jun 11, 2024

Stealing this task!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants