[ReHLDS] PF_MessageBegin_I msg77 Investigation - AFK Control Code Review

[zlajasql]

Pozdrav svima,

Želio bih čuti neka mišljenja o AFK Controlu i mogućoj interakciji s mojim trenutnim okruženjem.

Serversko okruženje:

ReHLDS:
3.14.0.857-dev
Build 4002
27. ožujka 2025.

ReGameDLL:
5.28.0.756-dev
27. ožujka 2025.

AMX Mod X:
1.9.0.5303

Trenutni problem:

Povremeno se server ruši/ponovno pokreće s:

PF_MessageBegin_I: Nova poruka je započeta kada poruka '77' još nije poslana

Najnoviji primjeri:

10/06/2026 - 15:37:02 (de_inferno)
10/06/2026 - 03:31:07 (de_dust2)
10/06/2026 - 01:57:29 (de_westwood)

Nedavno sam počeo testirati AFK Control 1.2 i volio bih recenziju koda od iskusnih korisnika ReHLDS/ReAPI-ja.

Pitanja:

1. Vidi li itko išta opasno u implementaciji AFK Controla?
2. Postoji li nešto što bi moglo neizravno generirati nalete TeamInfo / ScoreInfo podataka prilikom premještanja igrača u gledatelja?
3. Može li dodatak doprinijeti problemima s PF_MessageBegin_I msg77?
4. Je li itko uspješno koristio ovaj plugin na prometnom javnom serveru s 32 slota?

Relevantni dodaci koji komuniciraju s timovima, gledateljima ili stanjem igrača:

• AFK kontrola 1.2
• Admin Spectator ESP 1.4_beta
• BCS Nevidljivi promatrač 0.4.3
• Oživljavanje suigrača 2.3.17
• CSR Napredna pomoć pri ubijanju 0.9
• BCS VIP MySQL
• BCS HUD oštetitelj

U prilogu:

• afk_control.sma
• sys_error.log
• popis dodataka

Svaka povratna informacija je dobrodošla.
Hvala vam.

 

[zlajasql]

Logs

 

[zlajasql]

bump?

 

[fl0wer]

Hard to read. Please use English.

 

[sTe]

Hi, try this plugin.

 

[zlajasql]

Hard to read. Please use English.

Hello everyone,

I would like to hear some opinions on AFK Control and its possible interaction with my current environment.

Server Environment:

ReHLDS:
3.14.0.857-dev
Build 4002
March 27, 2025

ReGameDLL:
5.28.0.756-dev
March 27, 2025

AMX Mod X:
1.9.0.5303

Current Issue:

Intermittent server crashes/restarts with:

PF_MessageBegin_I: New message started when message '77' has not been sent yet

Latest examples:

10/06/2026 - 15:37:02 (de_inferno)
10/06/2026 - 03:31:07 (de_dust2)
10/06/2026 - 01:57:29 (de_westwood)

I recently started testing AFK Control 1.2 and I would like a code review from experienced ReHLDS/ReAPI users.

Questions:

Does anyone see anything dangerous in the AFK Control implementation?
Is there anything that could indirectly generate TeamInfo / ScoreInfo data bursts when moving players to spectator?
Could the plugin contribute to the PF_MessageBegin_I msg77 issues?
Has anyone successfully used this plugin on a busy 32-slot public server?
Relevant plugins that communicate with teams, spectators, or player state:

AFK Control 1.2
Admin Spectator ESP 1.4_beta
BCS Invisible Spectator 0.4.3
Teammate Revive 2.3.17
CSR Advanced Kill Assist 0.9
BCS VIP MySQL
BCS HUD Damager
Attachment:

afk_control.sma
sys_error.log
list of plugins
Any feedback is welcome.
Thank you.

Сообщение автоматически объединено: Сегодня в 14:39

Hi, try this plugin.

Hi,


Regarding your modified AFK Control plugin:


For a public server that is usually 30–32/32 players, would you keep afk_min_spec_players 30 or lower it to 28?


I'm trying to optimize spectator cleanup without being too aggressive towards legitimate spectators.


What would be your recommended setting?