Implement blocks ticking per world API

[ShockedPlot7560]

Introduction

We already support to change the random tick speed in server, however we can't control which world or change it at runtime. This PR fix that by providing an API and adding new configuration key.

Relevant issues

• Fixes API for random tick speed #6173

Changes

API changes

Adding the following functions to World:

• setTickedBlocksPerSubchunkPerTick
• getTickedBlocksPerSubchunkPerTick

Adding a new event WorldTickedBlocksChangeEvent which is fired when the value of tickedBlocksPerSubchunkPerTick change (not at the initialisation).

Backwards compatibility

No

Follow-up

Change the configuration nested the worlds per-tick and the default value under a blocks-per-subchunk-per-tick

[dktapps]

I feel like the method names are too esoteric for anyone to ever actually use them. Can we simplify these names at all without losing the meaning?

[ShockedPlot7560]

Can we simplify these names at all without losing the meaning?

The only names i see would be:

• initTickedBlocksPerSubchunkPerTick → initSubchunkTicks
• setTickedBlocksPerSubchunkPerTick → setSubchunkTicks
• getTickedBlocksPerSubchunkPerTick → getSubchunkTicks

But we will need any docs to precise this is the number of block ticked inside each subchunk each tick. But for now, I don't see any shorter name.

[dktapps]

I feel like those are too ambiguous too.

[ShockedPlot7560]

I can't think of any other name without losing the original meaning of the function.

[dktapps]

Perhaps the issue here is that we're exposing something that is too "internal". "Random tick speed" would be the most intuitive name, but the problem is that, because of its usage, the values don't map onto what users would expect.

We could expose a random tick speed that is just this value divided by 3, but we'd probably have to make it a decimal value to allow the level of granularity that the current setting has. This then exposes all kinds of edge cases like what happens if somebody sets a tick speed of 1.5. We can't tick 4.5 blocks per tick without a lot more complexity.

[ShockedPlot7560]

Come to think of it, isn't it possible to add a warning in the console if the final value is a decimal, saying that it has been rounded up or down?

[dktapps]

No one reads warnings, and even if they do, they won't know why it's being emitted if a plugin triggers it.