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

Async condition task handling #2795

Closed
2 tasks done
Condordito opened this issue May 16, 2024 · 3 comments
Closed
2 tasks done

Async condition task handling #2795

Condordito opened this issue May 16, 2024 · 3 comments
Labels
Bug A bug in the code or in a documentation.

Comments

@Condordito
Copy link
Contributor

Condordito commented May 16, 2024

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

BetonQuest version: 2.1.2-DEV-4
Server version: git-Paper-462 (MC: 1.20.4)

Hooked into: Citizens (2.0.33-SNAPSHOT (build 3365)), EffectLib (10.2), MMOCore (1.12.1-SNAPSHOT), MMOItems (6.10-SNAPSHOT), MythicLib (1.6.2-SNAPSHOT), MythicMobs (5.6.2-SNAPSHOT-7679d6a3), PlaceholderAPI (2.11.5), ProtocolLib (5.2.0-SNAPSHOT-679), Vault (1.7.3-CMI)

Expected behaviour

Conversations should run asynchronously without any problems

Actual behaviour

When interacting with the NPC the conversation is cached but does not start

Steps to reproduce

This usually happens randomly a few minutes after starting the server. I haven't found any way to reproduce it

Error, Warning, Exception or Thread Dump

No response

Additional information

It gets stuck on Conversation#selectOption if conditions are evaluated asynchronously. The same thing happens when login out, where if Conversation#endConversation is run in another thread, it doesn't remove the player from its cache

Additionally, when the player disconnects again, the cached instance is no longer the same as the current one, causing it to no longer try to remove its listeners

https://youtu.be/G520uFf8hko

@Condordito Condordito added the Bug A bug in the code or in a documentation. label May 16, 2024
@Wolf2323
Copy link
Member

What conversation IO do you use?

@Condordito
Copy link
Contributor Author

menu

@Wolf2323
Copy link
Member

As we are not able to reproduce this, and it is probably a bug caused by maybe an other plugin or so, i close this now. once we have a reproducable setup we can reopen this.

We also discussed this a bit in discord, and can continue there until we have found the setup to reproduce

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.
Projects
Archived in project
Development

No branches or pull requests

2 participants