[Maxximou5]

I got sometime before I got to get to work, if you want me to take a look personally, add me on steam by my name here and I can see about fixing this issue for you. As it seems you've done everything else correct, but for some odd quirky reason it's not getting the parameters correct.

[veli]

i am not sure you have saw it but there is a little space in your srcds.exe

In yours startline is this;
src ds.exe

check that and try again. Sometimes a solution is in little detail .

And creat autoexec.cfg and add your +sv_setsteamaccount xxxxxxxxxxxxxxxxxxxxx in there. Remove +sv_setsteamaccount xxxxxxxxxxxxxxxxxxxxx from your startline. It can be the issue too.
I am sure it will work after doing this.

[Maxximou5]

VALVe recommends using the startline parameter rather than the autoexec.cfg as it causes issues on being executed too late. Not that enough people have that problem, but less problems occur from doing it the startline parameters. Of course, do what is easiest for you, but the recommended way is to continue using the method he is already doing.

[veli]

i know that but i tryed it in a script that i used for installing my gameserver and all the values after that line broken. No idea why. So i added it in autoexec.cfg and my problem was solved.

Maybe he have same issue. Thats why i advice him to do that.

But you are right, valve advice it but autoexec.cfg works great too.

[Crowii]

Originally Posted by veli i am not sure you have saw it but there is a little space in your srcds.exe In yours startline is this; src ds.exe check that and try again. Sometimes a solution is in little detail . And creat autoexec.cfg and add your +sv_setsteamaccount xxxxxxxxxxxxxxxxxxxxx in there. Remove +sv_setsteamaccount xxxxxxxxxxxxxxxxxxxxx from your startline. It can be the issue too. I am sure it will work after doing this.

In regards to the space, there isn't one, I must've accidently hit a space somewhere after posting my starting target:
C:\Users\John\Desktop\SteamCMD\csgoserver\src ds.exe -game csgo -console -usercon +game_type 0 +game_mode 0 +map surf_greatriver_xdre4m_mp +sv_lan 0 -port 27015 +host_players_show 2 -condebug +sv_setsteamaccount xxxxxxxx -tickrate 128

[Crowii]

Would putting my xxxxxxxxx in the autoexec AS WELL as my launchs paras create an issue?
I'm just thinking in terms of keeping double the safeness if I muddle something up in the future.

Regardless, the 64tick persists...
Would it be wise for me to upload my server.cfg (ofc removing my token) for you guys too look at and possibly spot a mistake?

[Maxximou5]

You should choose one or the other, because if you change tokens for some reason you might forget you did both and it'll cause issues then. Best bet is to stick with what you have.

You can post your server.cfg with the code tags, but the server.cfg doesn't come into play with what the problem is; however, you can post it for us to review because there may be issues with it anyways.

[Crowii]

I fixed it!

I got frustrated and pasted my tickrate settings from server.cfg into my gamemode comptetitive.cfg and that fixed it.
I don't think... That should've fixed it... but I'm not complaining at this moment in time.

Now I just need to get FastDL working but I can save that for after Christmas.

[Jakeey802]

!knife. how to get your server blacklisted real quick

[Potato Uno]

I would HIGHLY RECOMMEND you remove "!knife" (and possibly "!hats") from your hostname if you don't want Valve's auto-blacklisting system to ban you.