Page 1 of 2

Minetest 5.3.0

Posted: Thu Jul 09, 2020 20:24
by sfan5
Minetest 5.3.0 has been released.

Highlights

  • Android support readded
  • Formspec improvements, including a scrolling GUI element
  • Performance improvements to the Server and API
  • Many bug fixes and small features
Changelog: https://dev.minetest.net/Changelog#5.2. ... 6.92_5.3.0
Source code: https://github.com/minetest/minetest/tree/5.3.0

Download


Re: Minetest 5.3.0

Posted: Thu Jul 09, 2020 21:03
by Hamlet
sfan5 wrote:
Thu Jul 09, 2020 20:24
Minetest 5.3.0 has been released.
Congratulations!
And thank you all for your work. :)

Re: Minetest 5.3.0

Posted: Thu Jul 09, 2020 21:10
by LMD
Hamlet wrote:
Thu Jul 09, 2020 21:03
Congratulations!
And thank you all for your work. :)
Couldn't have said it any better.

Re: Minetest 5.3.0

Posted: Thu Jul 09, 2020 21:24
by q333
When is it getting put on the play store?

Re: Minetest 5.3.0

Posted: Thu Jul 09, 2020 21:44
by rubenwardy
I've submitted the update to the play store. Last time, it took about 12 hours to get approved

I've also updated the PPA, and I'm attempting to update F-Droid

Re: Minetest 5.3.0

Posted: Thu Jul 09, 2020 22:54
by Zughy
Great job everyone! (and don't forget to celebrate :D)

Re: Minetest 5.3.0

Posted: Fri Jul 10, 2020 07:46
by Andrey01
Nice :) Will take a look at the play store for new version.

Re: Minetest 5.3.0

Posted: Fri Jul 10, 2020 09:49
by TenPlus1
w00t! thanks guys :)

Re: Minetest 5.3.0

Posted: Fri Jul 10, 2020 10:27
by Linuxdirk
Nice! Will compile this evening and test through weekend! Thanks!

Re: Minetest 5.3.0

Posted: Fri Jul 10, 2020 11:15
by KatzEyez
Awesome! :D I love updates! Thanks for all your hard work.

Re: Minetest 5.3.0

Posted: Fri Jul 10, 2020 19:01
by Seirdy
Yes! Can't wait till the Flatpak hits Flathub. The build is ready for publishing: https://flathub.org/builds/#/builders/32/builds/23521

If not manually published, it will be auto-published in 24 hours.

Re: Minetest 5.3.0

Posted: Fri Jul 10, 2020 20:14
by diazepam
Finally writing works on android 10!
thank you so much guys (:

(there is still the same problem when you have to repeat your password on the first login in a server, i know this is not the right place to ask but maybe is an easy fix)

Is someone working on osx releases?

ready for a weekend on MT <3

Re: Minetest 5.3.0

Posted: Fri Jul 10, 2020 20:23
by Festus1965
server "Asia Thailand" as of using [mod] playeranim and already player joined with 5.3.0 client ... changed successful upgraded to 5.3.0 stable

thanks for your work, team

* only the change from F9 to c/v knocked me out ...

new in terminal WARNING compare to last version ... happen during logins so far I see

Code: Select all

WARNING[ConnectionSend]: con(4/1) Packet quota used up for peer_id=19, was 1280 pkts
(MY .conf contains : max_packets_per_iteration = 10480 (not 1024))

update 3 hours later
need to get back to dev as of ...

Code: Select all

...
2020-07-11 04:52:33: ACTION[Server]: Janus places node xpanes:bamboo_frame_flat at (20214,2,23434)
2020-07-11 04:52:39: ACTION[Server]: Janus digs xpanes:bamboo_frame_flat at (20214,2,23434)
2020-07-11 04:52:39: ACTION[Server]: Janus digs default:wood at (20215,1,23434)
2020-07-11 04:52:49: ACTION[Server]: Janus places node default:wood at (20215,1,23434)
2020-07-11 04:52:52: ACTION[Server]: Janus places node xpanes:bamboo_frame_flat at (20216,2,23434)
2020-07-11 04:52:55: ACTION[Server]: Janus places node xpanes:bamboo_frame_flat at (20215,2,23434)
2020-07-11 04:53:01: ACTION[Server]: Janus places node xpanes:bamboo_frame_flat at (20216,3,23434)
2020-07-11 04:53:06: ACTION[Main]: Server: Shutting down
2020-07-11 04:53:06: ACTION[Server]: Siriphorn leaves game. List of players: 
[Showbones] Server shutting down, saved Showbones all player(s) data to db file.
2020-07-11 04:53:07: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod 'default' in callback luaentity_Step(): /usr/local/share/minetest/builtin/game/item_entity.lua:198: Collision info missing, this is caused by an out-of-date/buggy mod or game
2020-07-11 04:53:07: ERROR[Main]: stack traceback:
2020-07-11 04:53:07: ERROR[Main]: 	[C]: in function 'assert'
2020-07-11 04:53:07: ERROR[Main]: 	/usr/local/share/minetest/builtin/game/item_entity.lua:198: in function 'on_step'
2020-07-11 04:53:07: ERROR[Main]: 	...e/minetest/games/minetest_game/mods/default/item_entity.lua:43: in function <...e/minetest/games/minetest_game/mods/default/item_entity.lua:42>
"Collision info missing, this is caused by an out-of-date/buggy mod or game" - funny that this have not been detected during 5.3.0-RC testing ... tsts
and no sign what (mod, ...) caused and now every time player login, server crash again

Re: Minetest 5.3.0

Posted: Sat Jul 11, 2020 03:28
by Wuzzy
IMPORTANT NOTICE TO GAME MAKERS: Minetest 5.3.0 introduces a breaking change that changes the maximum possible breath value that players can have from max_breath+1 (11) to max_breath (10). This will mess up a lot of games and mods that relied on the old behavior.

This implies that all games that use the “hudbars” mod now need to update their hudbars mod.

Re: Minetest 5.3.0

Posted: Sat Jul 11, 2020 08:08
by Astrobe
Festus1965 wrote:
Fri Jul 10, 2020 20:23
"Collision info missing, this is caused by an out-of-date/buggy mod or game"ash again
Got that too, with my game based on a prior version of MTG. Just copy/paste default/item_entity.lua from the new MTG into your game's default mod.

Re: Minetest 5.3.0

Posted: Sat Jul 11, 2020 09:56
by Festus1965
Astrobe wrote:
Sat Jul 11, 2020 08:08
Got that too, with my game based on a prior version of MTG. Just copy/paste default/item_entity.lua from the new MTG into your game's default mod.
Thanks, my thoughts went this way, not sure if at 2am in the morning I took the right turn.
New test with sure new download 5.3.0 mts and game (+over my diffs) is running now ... waiting for the poor same player, got the problem in the morning, when I was at early morning market ... 4:30 - 7am and didn't see it.

The max_breath I found also, able to change it back to 11, if there is some problem, but checking the here used hunger hud mod, I found the variable, but there it was checked with "if > 10 then" so I guess that might not be a problem ...

I feel like the labor monkey ...

and added:
no, I teleport to this area, and there are 2 xpanes:bamboo_frame_flat,param2: 1
which I cant pass (walk through with old version, but stand in and crash with 5.3.0)

==> got same crash again ...
server back to 5.3.0-dev-....
I am the labor rat ... now

Re: Minetest 5.3.0

Posted: Sat Jul 11, 2020 10:51
by Astrobe
It would be nice if known compatibility issues were listed in the changelog.

Besides that, thank y'all for the good work.

Re: Minetest 5.3.0

Posted: Sat Jul 11, 2020 10:53
by Wuzzy
By the way: I like the increased speed of Minetest releases a lot. It allows games and mods to move forward much faster.
I am also quite happy with the changelog. But maybe I'm just biased because my name appears in it. *patsmyselfontheback*

I'm a little proud of the new Development Test (formerly “Minimal development test”), which has many new features. It's not interesting for players, obviously, but you don't realize how much work went into this. I hope it will prove useful in the future to find more bugs and maybe a little bit for mod development as well.

If you have any questions about this, feel free to ask!

Re: Minetest 5.3.0

Posted: Sat Jul 11, 2020 20:39
by Zughy
Wuzzy wrote:
Sat Jul 11, 2020 10:53
I'm a little proud of the new Development Test (formerly “Minimal development test”), which has many new features. It's not interesting for players, obviously, but you don't realize how much work went into this.
100% agree. I've started testing and submitting PRs a few weeks ago and one day I had to test something with the plain 5.2.0 release. Oh boy the Development Test compared to the one from 5.3.0... nope. Nope.

Re: Minetest 5.3.0

Posted: Sat Jul 11, 2020 22:12
by Mineminer
My favorite release yet, I fired up my server as result as the much needed chat font size was implemented. :)

Re: Minetest 5.3.0

Posted: Sun Jul 12, 2020 11:45
by srifqi
diazepam wrote:
Fri Jul 10, 2020 20:14
(there is still the same problem when you have to repeat your password on the first login in a server, i know this is not the right place to ask but maybe is an easy fix)
You can change its behavior in advanced settings:
Client -> Network -> Enable register confirmation

Code: Select all

#    Enable register confirmation when connecting to server.
#    If disabled, new account will be registered automatically.
#    type: bool
# enable_register_confirmation = true

Re: Minetest 5.3.0

Posted: Sun Jul 12, 2020 16:47
by diazepam
srifqi wrote:
Sun Jul 12, 2020 11:45
You can change its behavior in advanced settings:
Client -> Network -> Enable register confirmation

Code: Select all

#    Enable register confirmation when connecting to server.
#    If disabled, new account will be registered automatically.
#    type: bool
# enable_register_confirmation = true
Thank you so much!

Re: Minetest 5.3.0

Posted: Mon Jul 13, 2020 13:30
by redblade7
I see in the changelog that there is a new auth backend for PostgreSQL. Anything I should know before switching my servers to it? Also, what is the field in worlds.mt for the PostgreSQL auth database info (I'm guessing it's "pgsql_auth_connection")?

Re: Minetest 5.3.0

Posted: Wed Jul 15, 2020 16:40
by Nordal
Thanks a lot for your work and your personal engagement!

Re: Minetest 5.3.0

Posted: Fri Jul 17, 2020 11:24
by Walker
can I somehow turn off this annoying warning !?

is new from 5.3.0 ... and I don't want to increase my log level because it would affect all warnings -.-

Code: Select all

2020-07-17 12:17:02: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:03: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 64 pkts
2020-07-17 12:17:06: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:06: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:06: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:06: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:06: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:06: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:06: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:09: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:09: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:09: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:12: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:12: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:41: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:17:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=154, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:21:55: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:22:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:22:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:22:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:22:48: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 16 pkts
2020-07-17 12:23:00: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=152, was 32 pkts
2020-07-17 12:44:39: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:39: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:39: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:40: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:40: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:40: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:40: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:40: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:40: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:44:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:44:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:44:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:44:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:44:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:44:42: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:44:44: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:15: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:16: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:16: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:16: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:16: WARNING[ConnectionSend]: con(6/1) Packet quota used up for peer_id=160, was 64 pkts
2020-07-17 12:45:17: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:45:17: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:45:17: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:45:17: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:45:18: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64
2020-07-17 12:45:18: WARNING[ConnectionSend]: con(6/1) Packet quota used up after re-sending packets, max=64