Minetest 5.3.0

User avatar
sfan5
Moderator
Posts: 3924
Joined: Wed Aug 24, 2011 09:44
GitHub: sfan5
IRC: sfan5
Location: Germany

Minetest 5.3.0

by sfan5 » Post

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


User avatar
Hamlet
Member
Posts: 764
Joined: Sat Jul 29, 2017 21:09
IRC: H4mlet
In-game: Hamlet
Location: Lombardy, Italy

Re: Minetest 5.3.0

by Hamlet » Post

sfan5 wrote:
Thu Jul 09, 2020 20:24
Minetest 5.3.0 has been released.
Congratulations!
And thank you all for your work. :)
My repositories: Codeberg.org | My ContentDB's page | I'm on PureOS with XFCE

User avatar
LMD
Member
Posts: 908
Joined: Sat Apr 08, 2017 08:16
GitHub: appgurueu
IRC: appguru[eu]
In-game: LMD
Location: Germany
Contact:

Re: Minetest 5.3.0

by LMD » Post

Hamlet wrote:
Thu Jul 09, 2020 21:03
Congratulations!
And thank you all for your work. :)
Couldn't have said it any better.
My stuff: Projects - Mods - Website

q333
New member
Posts: 2
Joined: Thu Nov 07, 2019 20:05
In-game: q333

Re: Minetest 5.3.0

by q333 » Post

When is it getting put on the play store?

User avatar
rubenwardy
Moderator
Posts: 6192
Joined: Tue Jun 12, 2012 18:11
GitHub: rubenwardy
IRC: rubenwardy
In-game: rubenwardy
Location: United Kingdom
Contact:

Re: Minetest 5.3.0

by rubenwardy » Post

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

User avatar
Zughy
Member
Posts: 130
Joined: Thu Mar 26, 2020 18:23
GitHub: belongs_to_microsoft
In-game: Zughy
Location: Italy
Contact:

Re: Minetest 5.3.0

by Zughy » Post

Great job everyone! (and don't forget to celebrate :D)
My texture pack: Soothing 32 | Mods: Arena_lib, Panel_lib, Magic Compass | Donate

User avatar
Andrey01
Member
Posts: 2395
Joined: Wed Oct 19, 2016 15:18
GitHub: Andrey2470T
In-game: Andrey01
Location: Russia, Moscow

Re: Minetest 5.3.0

by Andrey01 » Post

Nice :) Will take a look at the play store for new version.

User avatar
TenPlus1
Member
Posts: 2800
Joined: Mon Jul 29, 2013 13:38
GitHub: tenplus1

Re: Minetest 5.3.0

by TenPlus1 » Post

w00t! thanks guys :)

User avatar
Linuxdirk
Member
Posts: 2554
Joined: Wed Sep 17, 2014 11:21
In-game: Linuxdirk
Location: Germany
Contact:

Re: Minetest 5.3.0

by Linuxdirk » Post

Nice! Will compile this evening and test through weekend! Thanks!

User avatar
KatzEyez
Member
Posts: 39
Joined: Tue Aug 08, 2017 18:24
GitHub: KatzPetz
IRC: LadyK
In-game: LadyK
Location: (IG: Depends) (RL: USA)

Re: Minetest 5.3.0

by KatzEyez » Post

Awesome! :D I love updates! Thanks for all your hard work.
I am working on my first mod. (If you want to be a jerk, do it in "reality", not behind a keyboard.)

Seirdy
New member
Posts: 0
Joined: Fri Jul 10, 2020 18:57
GitHub: Seirdy
IRC: Seirdy
In-game: Seirdy

Re: Minetest 5.3.0

by Seirdy » Post

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.

diazepam
New member
Posts: 0
Joined: Sat May 09, 2020 12:41
In-game: diazepam

Re: Minetest 5.3.0

by diazepam » Post

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

User avatar
Festus1965
Member
Posts: 1317
Joined: Sun Jan 03, 2016 11:58
In-game: Thomas Explorer Thailand
Location: Thailand - Chiang Mai (+5-6h to MEZ)
Contact:

Re: Minetest 5.3.0

by Festus1965 » Post

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
Last edited by Festus1965 on Sat Jul 11, 2020 06:45, edited 3 times in total.

User avatar
Wuzzy
Member
Posts: 3981
Joined: Mon Sep 24, 2012 15:01
GitHub: Wuzzy2
IRC: Wuzzy
In-game: Wuzzy

Re: Minetest 5.3.0

by Wuzzy » Post

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.
My creations. I gladly accept bitcoins: 17fsUywHxeMHKG41UFfu34F1rAxZcrVoqH

Astrobe
Member
Posts: 321
Joined: Sun Apr 01, 2018 10:46

Re: Minetest 5.3.0

by Astrobe » Post

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.

User avatar
Festus1965
Member
Posts: 1317
Joined: Sun Jan 03, 2016 11:58
In-game: Thomas Explorer Thailand
Location: Thailand - Chiang Mai (+5-6h to MEZ)
Contact:

Re: Minetest 5.3.0

by Festus1965 » Post

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
Last edited by Festus1965 on Sat Jul 11, 2020 21:59, edited 1 time in total.

Astrobe
Member
Posts: 321
Joined: Sun Apr 01, 2018 10:46

Re: Minetest 5.3.0

by Astrobe » Post

It would be nice if known compatibility issues were listed in the changelog.

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

User avatar
Wuzzy
Member
Posts: 3981
Joined: Mon Sep 24, 2012 15:01
GitHub: Wuzzy2
IRC: Wuzzy
In-game: Wuzzy

Re: Minetest 5.3.0

by Wuzzy » Post

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!
My creations. I gladly accept bitcoins: 17fsUywHxeMHKG41UFfu34F1rAxZcrVoqH

User avatar
Zughy
Member
Posts: 130
Joined: Thu Mar 26, 2020 18:23
GitHub: belongs_to_microsoft
In-game: Zughy
Location: Italy
Contact:

Re: Minetest 5.3.0

by Zughy » Post

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.
My texture pack: Soothing 32 | Mods: Arena_lib, Panel_lib, Magic Compass | Donate

Mineminer
Member
Posts: 105
Joined: Mon Mar 05, 2018 04:05

Re: Minetest 5.3.0

by Mineminer » Post

My favorite release yet, I fired up my server as result as the much needed chat font size was implemented. :)

User avatar
srifqi
Member
Posts: 557
Joined: Sat Jun 28, 2014 04:31
GitHub: srifqi
IRC: srifqi
In-game: srifqi
Location: Indonesia

Re: Minetest 5.3.0

by srifqi » Post

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
Saya dari Indonesia! · Terjemahkan Minetest! · my mods · My nickname in IPA: /es.rif.qi/

diazepam
New member
Posts: 0
Joined: Sat May 09, 2020 12:41
In-game: diazepam

Re: Minetest 5.3.0

by diazepam » Post

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!

redblade7
Member
Posts: 312
Joined: Sun Feb 15, 2015 07:14
IRC: redneonglow redblade7
In-game: redblade7 redblade7_owner

Re: Minetest 5.3.0

by redblade7 » Post

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")?
-redblade7, admin of: THE CREATIVE GARDENS (creative), THE VALLEYS (sandbox), and THE DIGITAL FARMS (farming/hunger/shops)

Nordal
Member
Posts: 113
Joined: Mon Jul 30, 2018 15:46
GitHub: Nordall
Location: Germany

Re: Minetest 5.3.0

by Nordal » Post

Thanks a lot for your work and your personal engagement!

User avatar
Walker
Member
Posts: 1126
Joined: Tue Oct 03, 2017 09:22
In-game: Walker

Re: Minetest 5.3.0

by Walker » Post

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

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests