cm. (DayZ)

RCon uses UDP to sent and receive commands. Obviously that makes it unreliable by default. It is programmed to disconnect after 10 seconds of having no message received. This will often occur if the server is too busy with handling player data (or is locked up etc) to send RCon information to clients (the client being the RCon console).

FYI you can just allow custom pbo with private bikeys and you can load up on the server whatever you want, hacks and all. Of course you'll still have to work around your own script restrictions (unless you want to use a bypass and risk a global banned). Good way to catch griefers. I've thought about it but cbf, I don't actually play the game so it would be of little use.

protip: log parser =/= "cheat". A good analogy for this: If your country was invaded by another, would you fight back with spears or bombs?

um, if you have your profile and BE folder in your arma 2 directory then yes it is very easy. This has been around for many many years and is intended. This is very basic arma 2 server security. I suggest you read the wiki on how it works to prevent it in the future.

A 2 second google will get you your answers.

no it's fine, this has been in how many threads now?

Your first section has nothing to do with spawning vehicles. The second is teleporting.

it would be the 142nd line, it starts at 0

did you actually re-do your file or did you just add "//new" ?

I'll just leave this here: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins&p=2192402&viewfull=1#post2192402 LOTS of servers will have 0 protection again scripts as the old file has become obsolete. They will need to be updated or it's scripters delight.

if you actually administer the server correctly and have half a brain you will be able to figure out how to use it to detect all kinds of scripters, including those with a bypass. I also just noticed there is another thread... can probably close this one.

eh, dunno what causes it then, it's obviously something else. Either way people will get kicked if you use it. Not many mind you so it's up to you whether to use it or not.

cool story

I would have to agree that it is quite ridiculous. Once 1.61 hits it should calm down quite a bit more.

Not really, We can detect non-public scripts and have added them to our servers list.

Read the wiki....

Yeah thanks for that blender, I figured out what was causing it. 2-3GB per day per server is a stupid size for a log file IMO.

This is the reason we don't share our scripts file. 1) The more people who get hold of the file, the more chance it has of being released to the public. Once it is released to the public it becomes easy to circumvent 2) Many admins do not know how to setup basic server security. This is not always their fault, as the info on the BI community wiki is a bit vague in some areas. The scripts file can be downloaded directly to a persons computer on an ill-configured server thus again becomes easy to circumvent. I am happy to help with other queries, however obviously our own servers come first. True. might be related to death from a helo then. Either way, people will definitely get kicked legitimately if you add that line to your files. Might have changed since they removed choppers.

Firstly, it's not called "hardcore" it's called expert. Secondly, ANZ5 has been on expert for quite some time now, It you are not near aus though you will probably get ping kicked.

Took me a while but i finally found out what was causing this. Should be all fixed now.

You guys seen this one before? pretty annoying, kicked the whole server. ] 19.07.2012 17:53:59: <removed> - #189 ffects_AirDestructionStage2",_int, _t]; processInitCommands; }; }; 19.07.2012 17:53:59: <removed> - #68 city _v select 1; _dir = abs(_xv atan2 _yv); _Crater= "CraterLong" createvehiclelocal [_pos select

okay but how massive are your log files then?

^ the man. the legend.

Cheers, I'll add it to a server and see what I can find.

can you give me a heads up on how "call compile format" is being used? I don't have a problem with large log files, ours automatically get parsed and zipped for archive so space is not a huge issue.