General Notice about your ban.cfg to server owners
1 replies, posted
Hi, I originally made this thread on steam discussions -- however the userbase ***[U][I]their[/I][/U]*** is not exactly educated.. anyway
Once I updated to the latest 'thursday patch' the one with the revolver and stuff, I started up the server and immediately noticed a familiar name on the player list........ a name with symbols ------- aka a cheater, same guy I banned several days ago for aimbotting.. and I thought, huh he got a new account? Looked at the profile and it was the same one........ razzle dazzled and confused I immediately copied his steam community link to vacbanned.com (that's the site I use to get the 64bit id) and did ban 64bitid then kick 64bitid and he/she/it was gone as usual.
Then it was time to investigate, I went back to my cfg folder and still saw my banlist.cfg and bans.cfg were there right next to server.cfg -- opened the file and still saw the banid 64bitid list and all the users were there....... so re-reading the post on the thursday patch the -datadir changed
Anyway long story short, you need to navigate over to myserverdata>cfg and in there you should see a file called bans.cfg in this file you'll need to copy your banid list from your old config into there and save it
Then you'll need to move your server.cfg into this cfg folder in my server data, your regular cfg folder that you use to use can now be deleted -- along with banlist.cfg (this file isn't used at all)
Hope this helps!
Also completely unrelated -- when I updated my in-game binds and mouse sensitivity were changed, I went into my steamapps rust folder into my config and noticed I now had two files in there, one was client.cfg and the other was config.cfg
I noticed the game was only reading one of them which was the defaults, and that one was client.cfg -- so I deleted config.cfg and changed my input.mousespeed from that file, then just changed my binds back in-game and everything was fine (I'm not sure if this happened to anyone else but it's good to let you know about this too!)
Thanks for the info!! Alot of ppl had this problem! Me was one of them... all tho I figured it out after a while :D
+1
Sorry, you need to Log In to post a reply to this thread.