[!Caution]
When merged, deploy latest changes to server or otherwise campaign will break.
Closes #457
Motivation
We're currently processing all the campaigns that we get from the backend as if they belonged to the same supercampaign. This breaks the changes implemented in https://github.com/lambdaclass/mirra_backend/pull/614, that now sends two different supercampaigns to the client.
Summary of changes
Filter supercampaigns by name.
Now the Overworld scene sends the name of the Main Campaign when the Campaigns button is clicked, so the CampaignsManager knows which supercampaign to display (this is just a patch to allow the backend to merge, a better implementation is being implemented in https://github.com/lambdaclass/champions_of_mirra/pull/444)
How has this been tested?
Start the backend using this branch, and in the client go to campaigns, pick the first campaign and fight a level. Everything should still be working as usual.
Checklist
[X] I have tested the changes locally.
[X] I self-reviewed the changes on GitHub, line by line.
Closes #457
Motivation
We're currently processing all the campaigns that we get from the backend as if they belonged to the same supercampaign. This breaks the changes implemented in https://github.com/lambdaclass/mirra_backend/pull/614, that now sends two different supercampaigns to the client.
Summary of changes
Filter supercampaigns by name. Now the Overworld scene sends the name of the Main Campaign when the Campaigns button is clicked, so the CampaignsManager knows which supercampaign to display (this is just a patch to allow the backend to merge, a better implementation is being implemented in https://github.com/lambdaclass/champions_of_mirra/pull/444)
How has this been tested?
Start the backend using this branch, and in the client go to campaigns, pick the first campaign and fight a level. Everything should still be working as usual.
Checklist