xPaveway

Quick question: does everyone on the mission have to be in the same TS channel for this to work? Or can ACRE work over multiple TS channels.

I'm having problems with the AN/PRC 343, for some reason its blank white in areas. http://l6.imghost.us/FbU/ACREproblem.JPG I'm running the steam version of OA standalone. My mod line is -mod=@CBA_OA;@CBA;@ACRE;@jayarma2lib Any idea why this would happen?

What??

Nice description of the problem. Really have no idea what you are talking about.

Big Dawg, how is putting your rotors through trees supposed to make a chopper explode? This is a bad system, for all vehicles, not just choppers. For example: hummer in a lake = explode after 10 seconds. What?? It would be nice to actually survive a crash so that you could be rescued instead of omgwtfbbq explosion if you so much as touch a tree.

Will the G36 variants be updated? I noticed they still have the vanilla sound :( I love the gun by the vanilla sound is terribad. The G36C and C supressed have updated sounds, but G36A and G36K do not. I also noticed that some of the Mk16 are not updated with the new Mk16 sound, more specifically the Mk16 iron sight CQC version and CQC holo.

Because we all know just how smooth patching is, especially with the mixture of Steam, Retail, BAF, BAF lite and now beta patches.

Hey all, On our servers we're currently getting the error message when attempting to load a map, and then it dumps us back to choose a mission screen. This started happening after patch 1.54. Anyone else getting this error or know what it means?

Cool, what have you got so far?

How will you explain fact when car driver kills your friend??? It's of course fault of letting people drive! Ban cars now!

Ok thanks guys, we will let our server providers know they need to try getting BAF

And how easily I could circumvent your "anti-cheat".

/facepalm It's important to mention if you are using mods or not...

... Those two shots are at different times of day.

QFT I would like to see an official hotfix, this is becoming a pain to get this sorted out with our server provider.

What are your min and max ranges? 200m is ridiculously close for arty

... Artillery pieces have minimum ranges, you cannot fire closer than the minimum range. Ex: MLRS cant hit a target 20 meters in front of itself

What?

Hey all, After updating my server to 1.54 I couldn't get it to start up. The RPT file showed: Warning Message: Addon 'Warfare2Vehicles' requires addon 'CAWheeled2_Kamaz' And it stopped there. I removed the warfare2 pbos from the addons folder and the server was able to start correctly. Something may be bugged with the PBOs and configs.

Yeah but we can't tell who is spawning stuff. We can't just randomly hand out bans.

I came across this video... sound familiar?? :D

Hey all, Recently we've been having issues and people are saying that it's been people coming on to the servers and hacking. (We are playing Domination) For example: I've seen like 30 C130's crashed into the base. People are reporting that bombs are being dropped all over the map and people are randomly dying. I'm trying to get more detailed reports of what's going on, but how exactly can we see if people are hacking? Can hackers spawn vehicles and drop unlimited bombs? We're running Battleeye, which doesn't appear to help much. Nothing seems to appear in the server logs about a bunch of TKing or something strange, so I'm not really sure what exactly I can do to sniff out hackers. Really looking for advice here! Thanks

Anyway, lets just let this thread die now, not much else to talk about here. They've already caught wind of it and are getting a kick out of it. Don't bother name calling or suggesting some uber "anti-hack" technique lol. I agree with the previous posters suggesting closed door discussions at this point.

We need somewhere to discuss it, while I agree discussing the specifics of countermeasures in public is a big no-no, there isn't a lot of information about tools that admins can use to try and combat this stuff. The only thing we get is: run Sig Verification and BE, problem solved! Well it's clearly NOT problem solved, so we need some sort of outlet (private would be nice) to try and work on this problem. I don't know much about the BE dev, is it just a one man show over there? At any rate, the purpose of the thread initially was to understand if indeed we were experiencing hackers and if there are any other tools out there to help admins determine who's doing what. I think the main thing we need to get across to BIS is that we really need to start cracking down and implementing better admin tools for, at the very least, seeing who is doing what to the server. I think that the (already small) multiplier community that this game has could be much larger if we had proper administration tools and controls. ---------- Post added at 07:17 PM ---------- Previous post was at 07:05 PM ---------- And how are you going to cure the disease? The only real way to cure the "disease" is to either 1. Stop the griefers' drive 2. Rework the game engine for more security. SignatureVerification was a good step, but it's obviously not enough. BE attempts to help with this, but I would consider BE an attempt to cure the "symptom" as you put it, since really it's on BIS for core engine changes. Perhaps you are unaware of this, but it's a perpetual game of cat and mouse. For any game or piece of software out there, there WILL be people that will hack it and crack it, it's just the reality of life. Hacks and cracks continually evolve, and so must the countermeasures, it will never be "done". I think ANYTHING is a step in the right direction. Even if it's very small, such as logging createVehicle, but it will have to be able to eventually log other things etc. I'm not talking about a one stop solution to the problem. ---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ---------- On another note: Hell I would love to submit information to BE to aid them in preventing this stuff, but I don't really have any information I can gather from the server that would be useful.

This is NOT the solution. As said before, it's possible to bypass BE and sig. verification. ---------- Post added at 04:31 PM ---------- Previous post was at 04:25 PM ---------- If the mission is made properly, there really won't be a lot of spawning from the clients. I know that Domi does use locally spawned ammo boxes, but respawning of vehicles and whatnot is handled by the server (and should be for any good map). I'm not sure why you think createVehicle is constantly spammed by clients. Even if createVehicle was legitimately being used by local clients, you should be able to search through the log looking for people spawning "Bo_GBU_12" or whatever it is. The griefing scripts usually spawn thousands of objects in a very short amount of time. The objects are not typical and would easily stick out, when you see a log with a whole block of like 5000 lines of createVehicle GBU etc...