The Elder Scrolls Online journeys back into Skyrim with the latest Chapter - Greymoor. Where eveything both above and below ground, is not what it seems.
The Elder Scrolls Online Greymoor and the Journey Back to Skyrim
We sit down with members of the development team to talk about the past, present, and future of Hearthstone.
Blizzard on Hearthstone’s Massive Year of the Phoenix
After the excellent Resident Evil 2 remake from last year the third game in the series gets a similarly impressive visual makeover.
Resident Evil 3 Review - Action-Packed Remake Falters
We've taken a stab at our 10 best games to play when in the middle of a crisis. From recent hits to gems we keep coming back to.
The Good Place - Finding Your Videogame Comfort Zone
Banning a Player Via startup.txt
Towley
Sydney, New South Wales
51 posts
I have banned a player in Procon

this is his EA GUID (which is publicly viewable through our GameMe http://bf4banditos.gameme.com/bfiv

however it recognises this as PB Guid but GameMe says it his

But I wish to make it permanent because Procon loses this information sometimes so I think it should be in the startup.txt
or banlist.txt

What is the format/syntax to do this and which file should it be put in?
12:40pm 25/11/13 Permalink
system
Internet
--
12:40pm 25/11/13 Permalink
Towley
Sydney, New South Wales
52 posts
I have worked this out by reading the documentation
02:44am 27/11/13 Permalink
anthnyjb
Brisbane, Queensland
21 posts
can you link me i am looking to do this too?
09:34pm 28/11/13 Permalink
max
Mackay, Queensland
48 posts
you don't use the startup.txt like wtf
you use banlist.txt or just use procon to ban

Ban system by banlist.txt
The game server has an internal ban system. This system is independent from PunkBuster’s banlist.
At startup, ban entries are read from the file named banlist.txt. During runtime, the banList.* commands can be used to manipulate the banlist.
Players can be banned either on their soldier name, or on their EA GUID.
Banning someone on their soldier name is not particularly effective – if it’s a determined “griefer” then he/she will just create a new soldier and return.
Banning someone on their EA GUID is much more effective.
To find out someone’s EA GUID, perform admin.serverInfo while that person is playing on your server.
Or – inspect the AdminLog.
People can be banned either for a few seconds, until the end of the current round, or permanently.
The banlist can contain up to 10.000 entries

banlist.txt format
Each entry in the banlist occupies 5 lines.
The first line specifies what the ban is on:
guid – ban on EA GUID name – ban on soldier name ip – ban on game client IP address
The second line specifies the GUID/name/IP that the ban applies to
The third line specifies the duration of the ban:
perm – permanent round – until the end of the current round seconds – until the given time is reached
The fourth line contains the timestamp for a “seconds”-type ban; otherwise it is unused.
The fifth line contains the reason for being banned. Max length 80 characters.
11:36pm 28/11/13 Permalink
SnotGoblin
New Zealand
13 posts
LOL startup.txt is for your server startup and config....ban list has always been separate for BF based games?

The procon ban list is ok, but be warned they have a tendancy to "die" if you run multiple servers and have lots of bans ;)

Best bet is to use a plugin like Adkats or Metabans for managing your bans, especially if you run multiple servers :)

Never ban by Player name, as its 2 mins work for them to change it, and be straight back on your server..... Always ban via EA GUID.
Metabans and PBbans make it easy to track players who change their in game names as well....
You can also watch players, and add admin notes for other server admins....

<3 Metabans :)
07:51am 29/11/13 Permalink
Towley
Sydney, New South Wales
62 posts
Well I have banned these players from our server


http://bf4banditos.gameme.com/ban_list/bfiv
07:20pm 29/11/13 Permalink
system
Internet
--
07:20pm 29/11/13 Permalink
AusGamers Forums
Show: per page
1
This thread is archived and cannot be replied to.