[aron9forever]

though mostly unrelated, consider that a much simpler workaround is to just slay the player if he spawns too late in the round
g_canspawn = true

at round start, set a task to set g_canspawn = false after some time you consider they shouldn't be able to spawn anymore

on ham_spawn post, check if g_canspawn, and if it's false, slay the player (you might want to do this with a slight delay, say, a 1 second task)



as a side-note, is this maybe possible (and simpler) with reAPI?

[Spirit_12]

Originally Posted by aron9forever though mostly unrelated, consider that a much simpler workaround is to just slay the player if he spawns too late in the round g_canspawn = true at round start, set a task to set g_canspawn = false after some time you consider they shouldn't be able to spawn anymore on ham_spawn post, check if g_canspawn, and if it's false, slay the player (you might want to do this with a slight delay, say, a 1 second task) as a side-note, is this maybe possible (and simpler) with reAPI?

In that case, you would have to reset their deaths as well. Orpheu method is much simpler than that.

[ZEDD_Intensity]

Originally Posted by Spirit_12 Usually, I don't get involved this much with plugin threads, but your way with words made me change my mind. Add -condebug parameter to your server's startup line. This will create a log of everything that happens in your console and save it in your cstrike folder in console.log file. Bring us the output and we can further analyze and pin point the problem.

Greetings,

Uncommenting the bugged plugin, I awaited an extensive log file in /cstrike/ folder as you mentioned, which never appeared. Confirming that there is no console.log file in cstrike/, nor in cstrike/logs.

It took the server, less than 10 minutes to crash as my server has a bit of a traffic 24/7, as soon as a player tried to connect, it went off. Also confirming that cstrike/addons/amxmodx/logs has created nothing suspicious as well. I was expecting it to create an error log for the crash, but unfortunately, it didn't.

I thought it'd be a good idea to paste my StartServer Command Line here for an additional clarity.

PHP Code:

#!/bin/bash
screen -A -m -d -S csserver ./hlds_run -console -game cstrike +ip XX.XXX.XX.XX -port 27015 +maxplayers 32 -pingboost 1 -autoupdate -condebug -autorestart +map de_dust > /dev/null >&1 & 


Please let me know if it needs any change at this point.

Regards,
ZEDD

[aron9forever]

Originally Posted by Spirit_12 In that case, you would have to reset their deaths as well. Orpheu method is much simpler than that.

user_silentkill() blocks deathmsg then calles user_kill() with flag 1, meaning it will not update the score

[iguaan]

IIRC this is an error with the brr_nokill plugin.

I think I did these changes and it started working:

Originally Posted by Valer4 For work! CS 1.6, Linux, server build 6153: /addons/amxmodx/configs/orpheu/functions/InstallGameRules 19 line - "value" : "_Z16InstallGameRulesv" /addons/amxmodx/configs/orpheu/virtualFunctions/CGameRules/FPlayerCanRespawn 30 line - "value" : 20

EDIT: Tested it by changing the '20' back to '22', server crashed with Segmentation Fault whenever someone tried to abuse 'retry'

EDIT2: Just had the same error and orpheu "error" was the last message aswell. The issue is NOT with orpheu, it's just the last thing game shows before crashing. My issue was with some plugins (throw c4, bazooka, rainysnow). I had to compile the plugins myself on local pc, the auto-compiled versions didn't work for some reason.