Use Coroutines for TickTasks

[My-Name-Is-Jeff]

Could completely remove ticktask maybe?

[pull-request-quantifier-deprecated[bot]]

This PR has 149 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Medium Size : +95 -54 Percentile : 49.8% Total files changed: 34 Change summary by file extension: .java : +9 -1 .kt : +86 -53 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[My-Name-Is-Jeff]

The behavior changes from running every tick to running every game loop

How does coroutine work? I think they accomplish the same thing unless Minecraft is running behind on ticks

[Sychic]

The behavior changes from running every tick to running every game loop

How does coroutine work? I think they accomplish the same thing unless Minecraft is running behind on ticks

Well since the coroutine scope has a MC executor as a dispatcher, it's going to queue the tasks there. AFAICT, MC's addScheduledTask executes every game loop as opposed to every game tick.

[My-Name-Is-Jeff]

The behavior changes from running every tick to running every game loop

How does coroutine work? I think they accomplish the same thing unless Minecraft is running behind on ticks

Well since the coroutine scope has a MC executor as a dispatcher, it's going to queue the tasks there. AFAICT, MC's addScheduledTask executes every game loop as opposed to every game tick.

Delay behavior should be the same if each tick takes 50ms right? Should be fine because ticks also happen in game loop

[Sychic]

The behavior changes from running every tick to running every game loop

How does coroutine work? I think they accomplish the same thing unless Minecraft is running behind on ticks

Well since the coroutine scope has a MC executor as a dispatcher, it's going to queue the tasks there. AFAICT, MC's addScheduledTask executes every game loop as opposed to every game tick.

Delay behavior should be the same if each tick takes 50ms right? Should be fine because ticks also happen in game loop

I think game loops aren't aligned to ticks since game loops are also where the game renders each frame. The delay behavior makes sense but it wouldn't be synced to a tick to begin with.

[My-Name-Is-Jeff]

Superseded by 7a741404e010ba19f6b52477341b5720e31c04a7