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

AA3 Fixes #101

Open
10 of 17 tasks
nmadadair opened this issue Dec 13, 2022 · 3 comments
Open
10 of 17 tasks

AA3 Fixes #101

nmadadair opened this issue Dec 13, 2022 · 3 comments

Comments

@nmadadair
Copy link
Contributor

nmadadair commented Dec 13, 2022

  • Fix api-05-get-patch validation error that incorrectly states that the player's repaired inscription is wrong (will likely require a push to the twilioquest/server repo)
  • Lovelace statue on lovelacehallway map should be replaced with non-cobweb version; the pug file name should be updated too.
  • Bowls on dining tables in Lovelace tower are not layered correctly and appear under plates.
  • When the player enters lovelace_tower default from the lovelacehallway, the exclamation point appears even though the player cannot interact
  • Fredric note in library needs zIndex to be below player (it is currently rendering above)
  • Show notification to the player after they've completed all of the new API Academy content
  • Disable spellable/interactable properties from stools in the back of the catacombs
  • Add text explaining the parsing of text data from fetch responses to the api-03-fetch objective
  • Make the validation error for api-02-async-await clearer
  • Reward the player with the spell_lovelace_divination item for completing api-04-remote-and-local
  • The books on the lovelace_tower/default pedestals may be on the wrong layer. Right now it sort of looks like they render behind the pedestal, instead of on top
  • Articia's portrait in Lovelace_Tower and Inside_Perimeter is blurry
  • Grant player "disappear spell" item after getting the spell from the groundskeeper (may require additional art assets, and also not required for the AA3 release)
  • Transition between inside_perimeter default map and courtyard before it is enabled should have more narrative context (i.e. something blocking the path or a magical explanation for why the player cannot progress).
  • Lovelace door portrait leading to the lovelace library should be resized and/or as we think about a different UI for "talking magical objects" we should update this Lovelace portrait in some way
  • Gene's dialogue on the Potions Club has an oddly formatted ellipsis (Inside_Perimeter)
  • Bug's dialogue on beta testing has an oddly formatted ellipsis (Inside_Perimeter)
@MarvelProgramming
Copy link
Contributor

Transition between inside_perimeter default map and courtyard before it is enabled should have more narrative context (i.e. something blocking the path or a magical explanation for why the player cannot progress).

How do we feel about using the same approach as the obstacle notifications in lovelace_tower? Or we could even double down on the debris approach that's used to obstruct the entrance to the catacombs, and prevent the player from removing them until after they've gotten the pledge scroll

@nmadadair
Copy link
Contributor Author

How do we feel about using the same approach as the obstacle notifications in lovelace_tower? Or we could even double down on the debris approach that's used to obstruct the entrance to the catacombs, and prevent the player from removing them until after they've gotten the pledge scroll

I think we could definitely flesh out something along these lines. I do think we can wait until 2023 if you all feel similarly on this.

@MarvelProgramming
Copy link
Contributor

MarvelProgramming commented Dec 13, 2022

Articia's portrait in Lovelace tower is blurry

Took some screenshots to compare the differences!

No blurriness
avatar-blurry-example1

Blurry
avatar-blurry-example2

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

No branches or pull requests

2 participants