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

MenuConversationIO invalid ChatPageination. #2005

Open
2 tasks done
SaltyAimbOtter opened this issue Sep 2, 2022 · 1 comment
Open
2 tasks done

MenuConversationIO invalid ChatPageination. #2005

SaltyAimbOtter opened this issue Sep 2, 2022 · 1 comment
Labels
Bug A bug in the code or in a documentation. Confirmed Something is confimed.

Comments

@SaltyAimbOtter
Copy link
Member

Confirm the following

  • I use the latest release or dev-build. I also checked that this problem hasn't already been fixed in a newer dev-build.
  • There are no open or closed issues that are related to my problem.

BetonQuest version information

Both 1.12 and 2.0. are affected.

Expected behaviour

Options must be shown when the user scrolls down.

Actual behaviour

grafik

Steps to reproduce

Talk with the NPC and select the options to get to the long answers.
FirstQuest.zip

Error, Warning, Exception or Thread Dump

None

Additional information

No response

@SaltyAimbOtter SaltyAimbOtter added Bug A bug in the code or in a documentation. Confirmed Something is confimed. labels Sep 2, 2022
@SaltyAimbOtter SaltyAimbOtter self-assigned this Sep 18, 2022
@SaltyAimbOtter SaltyAimbOtter removed their assignment Oct 9, 2022
@Wolf2323
Copy link
Member

I had now the time to investigate this in depth.

The way it currently works, is the intended way, back when it was implemented. I don't like that way, but for the moment we need to accept this behaviour.

The current behaviour is that we can not scroll the NPC text, we can only scroll the answers of the player.
Because of that a NPC text is not allowed to be too long.


During investigating this, i also found an issue with an answer, that is 3 lines long, and cause that no arrow up is printed while there is an option above.
But the code there is so bad, that we have decided, that we will fix all ugly behaviours, when we rework the conversations system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug in the code or in a documentation. Confirmed Something is confimed.
Projects
Status: Todo
Development

No branches or pull requests

2 participants