-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
Yup, this looks like a big update. TH11 and a bigger map.
You should all expect serious downtime on the bot, as this is likely going to take me a while to accommodate these changes into the code. I…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…
-
```
Currently the periodic update is scheduled after a connectivity change
broadcast is received. This leads to situations when the periodic update is not
run at all.
I have refactored the code, so…