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

Murder mystery: notepad only saves one predefined note fetched from Toto #42

Open
nikolay-panovski opened this issue Jan 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@nikolay-panovski
Copy link
Collaborator

Steps to reproduce the problem

  1. Open the app with an implementation of "Murder mystery" featured (, MM-notepad branch, or any derivative or merger).
  2. Go to the character card in "Murder mystery" quest (see Murder mystery notepad #40 for details).
  3. Go back out to quest view. Solve at least 2 of the newly opened tasks.
  4. Go to the notepad in the character card.

Expected Behavior

A note is displayed in the upper dedicated area, corresponding to the first found clue from a solved task. Clicking on the left/right arrows around it scrolls through other clues and displays another one as a note.

Actual Behavior

A note is displayed in the upper dedicated area, corresponding to the first found clue from a solved task. Clicking on the left/right arrows does nothing. Inspecting localStorage (via dev tab > Application > see mm_notes_predefined) or the Toto user variable (via console logging after getting session info > see MMystery_Notes) shows a string with one element ID and a comma afterwards; this should be multiple / all solved IDs separated by commas.

Possible Solution

The problem is suspected to be on Toto's end, with parsing the user variable. The code in this app only accesses the variable to read it. Maybe the concatenation of the clue from the newly solved task needs to be done in the same way but with different syntax than
String({{variable}}) + {{elementId}}.

@nikolay-panovski nikolay-panovski added the bug Something isn't working label Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant