PVPGN WOL LADDER crash #487

Open
opened 2023-12-02 22:30:46 -07:00 by behod · 7 comments
behod commented 2023-12-02 22:30:46 -07:00 (Migrated from github.com)

Dec 03 13:21:21 [info ] pvpgn::bnetd::conn_destroy: [1256] closed wladder connection
Dec 03 13:21:21 [debug] pvpgn::bnetd::handle_irc_common_line: [1836] got "" "PRIVMSG" ["matchbot"] "Match COU=-2, COL=-2, MBR=1, LOC=21, RAT=1, RES=800, ADR=-507200742, NAT=1, PRT=1264"
Dec 03 13:21:21 [debug] pvpgn::bnetd::anongame_wol_player_create: [** WOL ] annongame player created: 111111111
Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [
WOL ] got unknown tag MBR param 1
Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [
WOL ] got unknown tag LOC param 21
Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [
WOL ] got unknown tag RAT param 1
Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [
WOL ] got unknown tag RES param 800
Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [
WOL **] got unknown tag NAT param 1
Dec 03 13:21:21 [debug] WinMain: server exited ( return : -1 )

Dec 03 13:27:50 [error] pvpgn::bnetd::game_parse_info: bad gameinfo format (missing line1)

how fix it
it's crash

Dec 03 13:21:21 [info ] pvpgn::bnetd::conn_destroy: [1256] closed wladder connection Dec 03 13:21:21 [debug] pvpgn::bnetd::handle_irc_common_line: [1836] got "" "PRIVMSG" ["matchbot"] "Match COU=-2, COL=-2, MBR=1, LOC=21, RAT=1, RES=800, ADR=-507200742, NAT=1, PRT=1264" Dec 03 13:21:21 [debug] pvpgn::bnetd::anongame_wol_player_create: [** WOL **] annongame player created: 111111111 Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [** WOL **] got unknown tag MBR param 1 Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [** WOL **] got unknown tag LOC param 21 Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [** WOL **] got unknown tag RAT param 1 Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [** WOL **] got unknown tag RES param 800 Dec 03 13:21:21 [warn ] pvpgn::bnetd::anongame_wol_tokenize_line: [** WOL **] got unknown tag NAT param 1 Dec 03 13:21:21 [debug] WinMain: server exited ( return : -1 ) Dec 03 13:27:50 [error] pvpgn::bnetd::game_parse_info: bad gameinfo format (missing line1) how fix it it's crash
behod commented 2023-12-02 22:33:06 -07:00 (Migrated from github.com)

@RElesgoe

@RElesgoe
behod commented 2023-12-02 22:34:06 -07:00 (Migrated from github.com)

@Sora012

@Sora012
Sora012 commented 2024-02-20 03:13:24 -07:00 (Migrated from github.com)

This is quick match crashing, and not a ladder specific issue. Quick match is fully broken overall and not properly implemented for other games at all beyond RA2/YR, I have a private branch I have been making commits to that got it partially working for RA2/YR but its still got issues and its not ready.

This is quick match crashing, and not a ladder specific issue. Quick match is fully broken overall and not properly implemented for other games at all beyond RA2/YR, I have a private branch I have been making commits to that got it partially working for RA2/YR but its still got issues and its not ready.
Nahiida commented 2024-02-27 04:56:24 -07:00 (Migrated from github.com)

This is quick match crashing, and not a ladder specific issue. Quick match is fully broken overall and not properly implemented for other games at all beyond RA2/YR, I have a private branch I have been making commits to that got it partially working for RA2/YR but its still got issues and its not ready.

it's SOLO map
I successfully compiled 8.0
There are two BUGs now... One is that there will be a delay in the normal WOL connection.
How to increase speed and reduce network delay? Is there any implementation in the code?
And YR LADDER always automatically jumps to the COOP map

> This is quick match crashing, and not a ladder specific issue. Quick match is fully broken overall and not properly implemented for other games at all beyond RA2/YR, I have a private branch I have been making commits to that got it partially working for RA2/YR but its still got issues and its not ready. it's SOLO map I successfully compiled 8.0 There are two BUGs now... One is that there will be a delay in the normal WOL connection. How to increase speed and reduce network delay? Is there any implementation in the code? And YR LADDER always automatically jumps to the COOP map
Nahiida commented 2024-02-27 04:57:58 -07:00 (Migrated from github.com)

This is quick match crashing, and not a ladder specific issue. Quick match is fully broken overall and not properly implemented for other games at all beyond RA2/YR, I have a private branch I have been making commits to that got it partially working for RA2/YR but its still got issues and its not ready.
if you can
Can you PM me your discord? my EM jljm1231@163.com send your discord

> This is quick match crashing, and not a ladder specific issue. Quick match is fully broken overall and not properly implemented for other games at all beyond RA2/YR, I have a private branch I have been making commits to that got it partially working for RA2/YR but its still got issues and its not ready. if you can Can you PM me your discord? my EM jljm1231@163.com send your discord
Sora012 commented 2024-02-27 05:49:01 -07:00 (Migrated from github.com)

As far as I can tell the latency is likely due to PvPGN pinging the game while in a session.. I haven't got a fix for it yet, nor do have a way I can actually confirm it, but I have noticed the latency settles down over time, if you can manage the first 30 to 60 seconds of game play it tends to stabilize. Atleast on the dev branch of this repo in a LAN environment.

As for the quick match its fully broken in RA2/YR, not implemented for others. It has multiple bugs so far that I've seen after having tried to fix it. Everything from crashing the server to players not able to find each other, or getting into infinite loops, or even trying to join your own quickmatch lobby. Quickmatch code has a bug in its switch statement if I recall correctly that affects YR.

I can push the state of what I have fixed, used from older code bases, and used from other forks later. For discord, I dont really use it often. If you really want/need to chat, I put my steam profile in my links on my profile temporarily. I'm headed to bed for now.

As far as I can tell the latency is likely due to PvPGN pinging the game while in a session.. I haven't got a fix for it yet, nor do have a way I can actually confirm it, but I have noticed the latency settles down over time, if you can manage the first 30 to 60 seconds of game play it tends to stabilize. Atleast on the dev branch of this repo in a LAN environment. As for the quick match its fully broken in RA2/YR, not implemented for others. It has multiple bugs so far that I've seen after having tried to fix it. Everything from crashing the server to players not able to find each other, or getting into infinite loops, or even trying to join your own quickmatch lobby. Quickmatch code has a bug in its switch statement if I recall correctly that affects YR. I can push the state of what I have fixed, used from older code bases, and used from other forks later. For discord, I dont really use it often. If you really want/need to chat, I put my steam profile in my links on my profile temporarily. I'm headed to bed for now.
Nahiida commented 2024-02-27 06:02:41 -07:00 (Migrated from github.com)

i add you steam my name is Nahida
 

www.scpwiki.com
@.***

 

------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2024年2月27日(星期二) 晚上8:49
收件人: @.
>;
抄送: @.>; @.>;
主题: Re: [pvpgn/pvpgn-server] PVPGN WOL LADDER crash (Issue )

As far as I can tell the latency is likely due to PvPGN pinging the game while in a session.. I haven't got a fix for it yet, nor do have a way I can actually confirm it, but I have noticed the latency settles down over time, if you can manage the first 30 to 60 seconds of game play it tends to stabilize. Atleast on the dev branch of this repo in a LAN environment.

As for the quick match its fully broken in RA2/YR, not implemented for others. It has multiple bugs so far that I've seen after having tried to fix it. Everything from crashing the server to players not able to find each other, or getting into infinite loops, or even trying to join your own quickmatch lobby. Quickmatch has a bug in YR code that breaks the switch statement if I recall correctly.

I can push the state of what I have fixed, used from older code bases, and used from other forks later. For discord, I dont really use it often. If you really want/need to chat, I put my steam profile in my links on my profile temporarily. I'm headed to bed for now.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

i add you steam my name is Nahida   www.scpwiki.com ***@***.***   ------------------ 原始邮件 ------------------ 发件人: ***@***.***>; 发送时间: 2024年2月27日(星期二) 晚上8:49 收件人: ***@***.***>; 抄送: ***@***.***>; ***@***.***>; 主题: Re: [pvpgn/pvpgn-server] PVPGN WOL LADDER crash (Issue #487) As far as I can tell the latency is likely due to PvPGN pinging the game while in a session.. I haven't got a fix for it yet, nor do have a way I can actually confirm it, but I have noticed the latency settles down over time, if you can manage the first 30 to 60 seconds of game play it tends to stabilize. Atleast on the dev branch of this repo in a LAN environment. As for the quick match its fully broken in RA2/YR, not implemented for others. It has multiple bugs so far that I've seen after having tried to fix it. Everything from crashing the server to players not able to find each other, or getting into infinite loops, or even trying to join your own quickmatch lobby. Quickmatch has a bug in YR code that breaks the switch statement if I recall correctly. I can push the state of what I have fixed, used from older code bases, and used from other forks later. For discord, I dont really use it often. If you really want/need to chat, I put my steam profile in my links on my profile temporarily. I'm headed to bed for now. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Techwizz/pvpgn-server#487
No description provided.