Add mining delay

[nebula161]

#309

[nebula161]

Have to figure out what to do about the test fail, but the results seem more correct

[nebula161]

Might have fixed #311 in the last commit

[nebula161]

Passes tests now with the second commit @mat-1

[mat-1]

Nice!

I think mining used to flag anticheats on occasion, if it's not too much of a bother, could you install GrimAC locally and test if this fixes it?

I'll merge this regardless soon anyways, but it'd be nice to know.

[nebula161]

Well, not only does it still get flagged on my paper server with Grim, but it reproduces 311 (without ever switching items)

[22:00:14 INFO]: Grim » Raeders failed FastBreak (x4) diff=58.0ms, balance=1058.0ms, type=deepslate
[22:00:16 INFO]: Grim » Raeders failed FastBreak (x9) diff=56.0ms, balance=1056.0ms, type=deepslate
[22:00:17 INFO]: Grim » Raeders failed FastBreak (x12) diff=45.0ms, balance=1045.0ms, type=deepslate
[22:00:21 INFO]: Grim » Raeders failed FastBreak (x19) diff=56.0ms, balance=1056.0ms, type=deepslate
[22:00:24 INFO]: Grim » Raeders failed FastBreak (x24) diff=56.0ms, balance=1056.0ms, type=deepslate
etc...

It fails fastbreak even when it fails to break the block????? On my LAN server, it mined for layers and layers, but now my bot can barely get through a row without getting stuck.

I don't understand what the alert messages mean to be able to debug this yet

[nebula161]

I should really make a reproduction bot at some point. I've just kind of tested with my end use

[nebula161]

bump

[mat-1]

I'm hesitant to merge this for now, since this creates more anticheat issues than I originally thought (Azalea doesn't flag while mining as often as I believed it did). I would like mining to be more correct, but it's gonna take a bit longer for this to be able to be merged.