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

Extended logging #17

Closed
Dode123 opened this issue Aug 24, 2019 · 4 comments · Fixed by #235
Closed

Extended logging #17

Dode123 opened this issue Aug 24, 2019 · 4 comments · Fixed by #235

Comments

@Dode123
Copy link

Dode123 commented Aug 24, 2019

A more detailed log should be available where you can see the all the movements/combat resolutions. This is especially important in non-live games where you might need to check other players previous combats and movements to remember what your next move was.

@Longwelwind
Copy link
Owner

Highjacking this issue to make some notes to myself about how a revamp of game logs will probably need to be done:

At the moment, game logs are prepared sent by the server in its full text. Markdown can be used to make bold or italic texts. This present multiple issues:

  • If a typo is made in the code, we can fix the typo for new game logs, but it would be hard to retro-actively change the game logs that were already generated.
  • Adding interactive parts to the game logs is harder (e.g. the game logs that says that both players have chosen their house cards could show these 2 house cards and make them zoomable by hovering on them, the same way it works in the lower-left panel of the UI). A solution is to add Markdown special syntax that the server can use, and that the client can render. It's a bit cumbersome.

Instead, we could define a game log a data structure like:

{
  "type": "house-card-chosen",
  "houseCards": [
    ["lannister", "tywin-lannister"],
    ["stark", "eddard-stark"]
  ]
}

This structure would be sent to the client. On the client, we can define a React component for each type of log (here, for house-card-chosen).

With this system, fixing a typo would done by simply changing the code, and would be applied retro-actively.

@gereon77
Copy link
Collaborator

gereon77 commented Jan 13, 2020

missing log notifications:

  • westeros: game of thrones result
  • retreats and their casualties
  • casualties from battle
  • wildling result for every house (discarded card, killed unit, nothing, etc)
  • Result of Resolve Consolidate Power Phase for all houses
  • CoK biddings

@Longwelwind
Copy link
Owner

Longwelwind commented Jan 29, 2020

On top of the list above:

  • Most House cards miss game logs for their actions.

@gereon77
Copy link
Collaborator

Log for Patchface is missing

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