Skip to content

fix: Tasks do no longer get marked as failed after being marked as completed (fixes #30)#33

Open
stchigel wants to merge 2 commits into
Terasology:developfrom
stchigel:quest-fail-fix
Open

fix: Tasks do no longer get marked as failed after being marked as completed (fixes #30)#33
stchigel wants to merge 2 commits into
Terasology:developfrom
stchigel:quest-fail-fix

Conversation

@stchigel
Copy link
Copy Markdown

@stchigel stchigel commented Jun 8, 2026

The original problem was that sometimes a task that had already been completed would get marked as failed after some time
The problem in the code was that, when the quest was completed, some tasks of the quest would still have timers running, and if these timers ran out it would send a task failed event, making it so the quest would be marked as failed.
The proposed solution is that when a quest complete event is triggered, it removes the timers from every task that's part of that quest

@stchigel
Copy link
Copy Markdown
Author

stchigel commented Jun 8, 2026

It didn't auto tag in the title but this is the issue: #30

@Cervator
Copy link
Copy Markdown
Member

Cervator commented Jun 8, 2026

Hi @stchigel and welcome!

Would you mind writing a proper description of the PR please? Both for clarity now and in the future. This sounds like a good bug fix, but how did you find it and how does the fix exactly work?

There are also associated unit tests that now appear to break - see https://jenkins.terasology.io/job/Terasology/job/Modules/job/T/job/Tasks/job/PR-33/1/testReport/

@stchigel
Copy link
Copy Markdown
Author

stchigel commented Jun 8, 2026

Hello @Cervator! Sorry about that, I'll write the description now.

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 this pull request may close these issues.

2 participants