[asdfxD]

i got console spam by this message.

sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.
sv: Lag comp - full interp info doesn't match target time, using target time instead.

is there a metamod plugin to blocks this message?

[root88]

Doesn't look hard to do

[AnimaVillis]

Originally Posted by root88 Doesn't look hard to do

Did you start sourcemod and metamod on cs2 server?

[asdfxD]

Originally Posted by root88 Doesn't look hard to do

can you code this? really annoying to read console cause of this spam.

[Taraman]

Originally Posted by cyberdeath Yes, rcon seems to be different with CS2 as opposed to CS. There are some online that I've stumbled across. The one I currently use is: https://github.com/gorcon/rcon-cli/releases/latest Here is another one: https://github.com/fpaezf/CS2-rcon-tool This is a web-based tool but I've had issues with it crashing my servers when sending commands (YMMV): https://github.com/shobhit-pathak/cs2-rcon-panel

I figured it out.
There are no more multipacket answers from the CS2 server. Only NodJS was the limit with 64K/packet, so I had to reassemble them.
Also the CS2 server does not seem to send two packets on authentication, but only the real authentication-response.

So I could update my Server API to run with Linux CS2 dedicated.
If anyone wants to have a look:
https://github.com/Taraman17/nodejs-cs2-api

[asdfxD]

for some reason if i install cs2 steamrt3 in pterodactyl, i cannot access my cs2 server with rcon tools.

[NomisCZ]

Originally Posted by asdfxD for some reason if i install cs2 steamrt3 in pterodactyl, i cannot access my cs2 server with rcon tools.

Try this Pterodactyl egg, RCON works fine - https://raw.githubusercontent.com/pa...--strike2.json

[asdfxD]

Originally Posted by NomisCZ Try this Pterodactyl egg, RCON works fine - https://raw.githubusercontent.com/pa...--strike2.json

i did. fresh install auf ptero, fresh install of dedicated server.

with your egg i got this:

Failed to initialize Steamworks SDK for gameserver. Failed to load module '/home/container/.steam/sdk64/steamclient.so'
0 Failed to initialize Steamworks SDK for gameserver. Failed to load module '/home/container/.steam/sdk64/steamclient.so'
container@pterodactyl~ Server marked as offline...
[Pterodactyl Daemon]: ---------- Detected server process in a crashed state! ----------
[Pterodactyl Daemon]: Exit code: 139

dunno where the /home/container/ location is

it's not server/home/...

edit: i got it working, now rcon is working from outside and external tools.

[elmuchogrumpy]

I'm having issues with my dedicated server and the following commands not working. I want to use these to clear smoke and rethrow flashes. All other commands seem to work just fine.

ent_fire smokegrenade_projectile kill
sv_rethrow_last_grenade

Anyone else having issues with these commands?

[asdfxD]

still have issues that the player skins aren't working after some hours of uptime, restarting the server solves this.... so annoying.