semipr0

I know WHY its duping, its because vehicles and tents aren't saving their child inventories correctly and haven't been for several weeks now. I DO save my tent after I use it. I save it like 8 times. If I have a vehicle I tend to spam saves on that at least 20 times cause I want to ensure its there when I get back. Every time, regardless of how many times I've tried to save my tent/vehicle state, when the server is restarted, the inventory reverts to a state previous to me actually having taken anything out of it. I've got a camp I only visit once in a small while due to its location. But just like my other tents I always save it after I've gone by it to grab something I might need cause I was in the area. And every time I go by the inventory is exactly the same, regardless of what I've used previously.

Actually no I'm just sorta discussing this at the moment. Trying to see what others feel about it. I think it sucks, so I'm putting my opinion forward on it and saying what I feel would fix it. Doesn't really mean I'm making a suggestion as such. Someone else might have a better counterpoint to my argument and render any suggestion made invalid.

I'll stop duping when I stop logging in with the stuff I put in my tent. Ergo, I'm not trying to dupe. I don't know why my tent has the stuff I put in it....and I still have it. Every time our server resets, everything I have taken out of my tent to use....is back in it to use again. Its not my fault, I didn't write this SQL system. The only thing I could possibly do is forget where my tent is and stop storing items entirely and just wander across Chernarus living off the land and never putting anything in a tent or a vehicle.

Because for every 1 person thats actually looking to help there are about 19 other jackasses looking to dupe someone into trusting them so they can lulz about it after they fraps it all and put it on the internet. DayZ was supposed to be a hardcore post apocalyptic survival simulation. What its turned into is.......COD with annoying zombies that get in the way. Its not even a case of people just not being able to trust any more cause they've been burned too many times.....its an established fact at this point that the largest contingent of DayZ players are simply killing other players for something to do...cause the whole "Survival" part of the simulation didn't get a lot of work and its not very fun. So most people just end up killing other players cause its the only thing to do. And a good handful of those people also do it because they think its hilarious. And its not like some new spawn on the coast isn't aware of the reputation this community has. When I first played DayZ I got chewed up by zombies in Cherno pretty bad, some guys with assault rifles came through where I was, killed the zeds, and actually gave me a transfusion and a morphine shot and got me back on my feet. But that was the last act of unsolicited kindness I've seen in DayZ. Since then...everyones a hunter. Everyone wants to be a bandit. Everyone that isn't you or your people is KOS. Its getting tiresome. I can get deathmatch in any number of games and most of them do it better than DayZ.

Recently during our absolutely joyous romp through Hackamania on our server I've been noticing something coincidental in regards to every situation. We had a clan that was on our server a few days ago. Two members of the clan were banned after we caught them driving Black SUV's up the north east highway north of Solnichy. Now we didn't ban every member of the clan that was on, just the drivers of the SUV's. Now for the last 3 days our server has been constantly attacked by hackers, and every time a member of the clan that we banned from our server, that isn't banned, is just idling in the lobby of the server. They're not logged into the game environment at all. As an experiment, after a particularly bad hack which teleported everyone into the wilderness and turned them into cows, I decided to ban the idling clan member that was in the lobby at the time. Server went completely quiet after that for several hours and normal play appeared to resume and I thought nothing of it. Lo and behold though about 3 hours later a new member of the clan we had problems with connected to the server and was just idling in the lobby. I kept an eye on it for about 30 minutes and then....bam, everyone on the server teleports to the top of the hotel in Chernogorosk, I quickly disconnect, check my Arma 2 Rcon...and the individual is still in the lobby. After reviewing my RPT, server_console.log and scripts.log, the teleport to the top of the hotel literally grabbed everyone that was actively playing the game on the server. There wasn't anyone that was left out of the mass setPos change. The only person that wasn't in the list, was the new clan member that had been idling in the lobby for around 30 minutes before the event occurred. Is it possible to run some scripts from the lobby? Without even having joined the game?

Yes there was a ban wave. No it wasn't big enough. Least over here on the US side of the network it wasn't.

Lucky you, he was too stupid to be running a bypass.

Not to argue with you directly but I don't believe the refined server hosting rules say I have to leave my server up 24 hours a day, 7 days a week. Locking it is against the rules, but what leads you to believe I am required to leave the server up 24 hours a day? I'm simply asking because we can barely keep control of our server environments even when we have active admins on and available. What we just leave it up when there are no admins at all and let our monthly payment fund a hacker free for all so we can log back in to a flaming mountain of helicopters and parachuting cows? Seems a little unreasonable to me.

RPT is full of this crap lately. Not sure what is generating it either.

Half the people running servers are running servers that were set up by HFB, Vilayer and Host Altitude. I don't think the blame for this being possible lies in the hands of the administrators that have rented these servers that were configured non-optimally. Also given that they're probably not all dedicated boxes, attempting to move outside the server root directory isn't exactly childs play for someone new to server administration. These major host resellers are the ones to blame for most of these improper installations....because they did think it was as simple as installing the game and in some cases they won't allow their clients to have the access required to make the changes....and the hosts have damn sure not gotten on the ball with reconfiguring these file locations.

Hive wipe.....I'm all for it. Between the exploiters and the normal users, my server has so much cat wire and sandbag blockage around the critical buildings of the major towns that new players are lucky if they can even get into a hospital or a critical supplies spawn even after surviving all the zombies. We can't send out a maintenance crew to take all this crap down every time the server restarts after all. And its making new player chances on our server pretty rough. They have to go much farther inland to enter most critical supplies locations and its because they have no access to the ones closest to them at coastal spawns due to mass amounts of area denial emplacements THAT NEVER GO AWAY EVEN IF YOU REMOVE THEM. Fix the Hive reporting of objDestroy, do a total wipe for all instance ID's and lets try this out in a situation where area denial emplacements and tents don't respawn every time a server resets.

I've been up all night dealing with exploits and parsing these obtuse goddamn logs trying to find the people messing with our server. After multiple mass teleports, vehicle teleports, illegally spawned vehicles (I've identified at least three illegitimate helicopter spawns today), and god knows what else.....when my clan mates reported that their player models suddenly started dancing...with absolutely no input from them at all, and they had zero key control of their characters...after logging in and confirming it with my own eyes, I shut down the server and I'm seriously considering just leaving it down. So...anyways we're certainly not "hiding our camps" cause every motherfucker with ESP has gang raped our camps for a week now. I'm just taking the server down cause I want to GET SOME FUCKING SLEEP. So have a nice day and play somewhere else.

All I can say is I wish that tool was fucking legal. It would make my life a lot fucking easier.

What do the server admins think about perhaps collaborating a single day server black out for as many DayZ servers as we can rightfully shut down as we run them and pay for their services? Overall the idea would be to demonstrate that we're tired of the state of script abuses and generalized hacking. And to demonstrate that within the rights that we have, we do not have to sit here and tolerate it. Keep in mind this isn't an idea that is being put forward to attempt to make some kind of "DayZ sucks" statement. We're hosting servers because we like the game. But I know that myself and several other admins I'm acquainted with are very tired of our nearly every single day in DayZ being a constant battle against hacks and hackers. Even if we can only shut down 60% of the active servers we will have made a statement that says "Without us, try hosting 75,000 players concurrently." and perhaps, we could at least get a little more understanding from the DayZ team what our love for their mod is costing us......and I'm not even talking about the money. Most of us hosting servers have the money to be doing it. Money isn't the issue, but consistently having our servers raped and compromised by hackers has become a near to daily affair. BattlEye can't stop it, it can only give us short reprieves. So if we take down a good percentage of the hosted servers that we do, as admins, have the legal right to shut down and leave down for as long as we like, we could potentially make a stronger statement in regards to pleading our case for stronger allowances for individual server control and autonomy, with the DayZ team, than consistently attempting to argue the point here on the forums where we receive very little in regards to attention to our concerns, and the rules keep stacking up against us, rather than in our favor. I am not, by the way, arguing for password protecting servers, private whitelisting or anythng else. I'm simply saying, if we blackout the network for just one day, and spend that day doing, I dunno, something that doesn't involve dealing with at least 18 separate and individual incidences of major exploit that have disrupted our entire servers legit player base, perhaps we can start a more constructive dialog with how servers are managed and reassert some rights, within the rules, of the server administrator that Bohemia Interactive Software seems to have no issue with allowing its private server admins to have. Again, just a thought. I'm not saying I'm right, or this is the right course of action. But, perhaps it could be a step in a larger direction. Feel free to share your opinions or vote on the poll.

Heres what we need. I'm currently up at 3:30 AM in the morning, because my public teamspeak was poking me like crazy and a clan mate called me and woke me up. We had, since midnight tonight, 2 mass leg break events, two black SUV's spotted by players, one mass teleport which dropped everyone from 60m in the air and killed them, and another mass teleport to the NW Airfield before I finally brought the server down because I was in the middle of already trying to make heads or tails of my logs as it was. Heres the problem, we got names on the guys that had the SUV's, there is nothing in scripts.log that shows them spawning them....hooray for the BE bypass, right? Second problem, my logs are literally reporting an hour behind real time at this time. The mass teleport events I can't even investigate yet, I keep refreshing my FTP and the timestamp went from 12:57AM to 1:11AM in about 30 minutes, its currently 3:30 as stated, our server runs on CST, and I can't even BEGIN to prove my case against the two mass teleports that just occurred in the last 30 minutes. The refined/updated rules are largely fine, the issue though is they require me to prove all this stuff occurred. I can't prove these black SUV's were spawned....the people that were in them have nothing in my scripts.log whatsoever. The people DO however show up in my RPT. Along with a constant spam in regards duplicate clips in someones secondary weapon slot that are spamming through my RPT in a fashion that I can't even tell who they originate from. You know as well as I do and BE does that we're in the middle of one of the largest and most disruptive hack waves that DayZ has seen. The refined rules need a very simple addition. 1.) In regards to major disruptive events. You may shoot first and ask questions later. Cause you know I am more than happy to admit that I may have banned someone in error, but right now, every time our server gets hit I have to spend an inordinate amount of time parsing logs and we're getting hit every day, multiple times a day. Its easy for me to remove a ban that I mistakenly applied, its not quite as easy for me to conclusively prove EVERY single case of a major disruptive event because the three files we have that mean diddly squat to this process are frustratingly hard to work with, and in the case of scripts.log, hilariously easy to circumvent. I am not looking to ban anyone. I don't WANT to ban anyone, I want to play DayZ on my server and enjoy it. But I'm spending every day sifting through these obtuse logs with absolutely no administrative tool suites that make them easier to parse and identify provided as part of our server tools, and I'm only able to prove half these hacks by a process of elimination. If my server logs update here soon, I MIGHT be able to prove who did the mass teleports by doing a process of elimination by cross comparing server_console.log and my RPT to see who wasn't teleported during the event that was logged into the server at the time, but even that is hardly 100%. You guys want us to have proof for the bans we place. How about loosening up the rules in regards to the burden of proof? If you can't do that how about adding a cross comparative tool that analyzes these files more effectively so we can load in the logs, find the events we're looking for without having to GUESS at them, and upload a ban report directly to a central server. In short, a lot of servers are in a near constant state of emergency right now, due to script exploitation, esp hacks and god knows what else. Perhaps the server administrators should be given the right, at least temporarily, to shoot on sight, cause these exploiters aren't giving us a break at all.

Well seeing as Hammerpoint turned this into a dick measuring contest, I am going to assume that whatever the stand alone puts out will be at least twelve inches longer than whatever Hammerpoint comes up with. Its like an axiom of competition in game development.

Completely off topic I wonder if that Rocket quote will change now that he has the resources.

Script.log doesn't appear to update past the 2MB mark. You need to basically take any 1.9+MB script.log, add a date you cycled it out to the name, and let a new one start generating.

Its not really about being an asshole. As I said I'm happy for Rocket, taking a mod to full on stand alone game status is seriously awesome. I'm just in DILLIGAF mode cause its not like this was unexpected. BIS would have to have been insane to ignore the money DayZ has made them, and it was only a matter of time before they inked this deal. Regardless of the red tape and lawyers involved. What I'm waiting for is engine details, expansionary plans to make all three "S" factors of the current game dynamic flesh out and be rewarding...yanno, the stuff thats going to make me decide to drop whatever the game is going to cost in the til. I'm sure those details will come, just saying, jumping around like a schoolgirl cause we found out something we were already aware was likely to happen is sorta pointless.

Yanno I'm like...totally happy for Rocket and all that. But til I hear some engine details, what their plans are for fleshing this out and "taking it to the next level" I simply could not be bothered to give a fuck. We knew this was coming. All that mattered was the when, and now all that matters is the details....which we don't have.

Lets all post a post about it. Just in case anyone misses it.

Long as the server doesn't blindly execute client script injections...I'm all for it.

Flying a chopper is all about mastering mouse piloting once you get it in the air. I can run a UH1H like a Corvette at 250kmh at < 30m like a boss. I don't use my keys at all other than for altitude adjustments and thats only if I need to add a bit more torque to my ascent/descent or I'm simply taking off or landing. UH1H is a bad ass piece of hardware while you can keep it. Unfortunately I've lost like 4 on our server so far to Script Restriction #55 errors. But its alpha, it'll get sorted out eventually.

We have three competent admins for our US server. Theres nothing that I am aware of that can detect a script being executed except BattlEye...we just don't have the tools to see things coming before they happen. So I'm not sure its down to better security on DE and UK servers, there are cheat reports for DE and UK servers in the cheat reporting section, as well as NL and US and just about everywhere else. You're just getting lucky really. Enjoy it while it lasts. Sometimes we get a few days with no hacking events on our servers too. Yesterday was almost entirely hack free til around 2am and all we dealt with then was a mass teleport event that I quickly sorted out via our server logs. Unfortunately there is no way to stop that kind of thing til BattlEye can detect it. If the UK and DE servers you're on have some kind of top secret BattlEye replacement, I'd love to buy it.

1:53:08 Player Gapetto kicked off by BattlEye: Script Restriction #55 1:53:08 Player Michael kicked off by BattlEye: Script Restriction #55 1:53:08 Player Chip Chipperson kicked off by BattlEye: Script Restriction #55 1:53:08 Player Michael disconnected. 1:53:09 Player Chip Chipperson disconnected. 1:53:09 Player Gapetto disconnected. 1:53:09 Player Charlii kicked off by BattlEye: Script Restriction #55 1:53:09 Player Cuervo kicked off by BattlEye: Script Restriction #55 1:53:09 Player Esproc kicked off by BattlEye: Script Restriction #55 1:53:09 Player Warranty45 kicked off by BattlEye: Script Restriction #55 1:53:09 Player [saH] WalkingDead kicked off by BattlEye: Script Restriction #55 1:53:09 Player Smallock kicked off by BattlEye: Script Restriction #55 1:53:09 Player Jano kicked off by BattlEye: Script Restriction #55 1:53:09 Player ADM Kiko kicked off by BattlEye: Script Restriction #55 Thats directly from my server console log after a player I have identified in the log used a script to transport my entire server population into the inaccessible second floor room of the inaccessible large church in Chernogorosk at approximately 1:52AM CST this morning. None of these people were in vehicles at the time. The scripts.log shows entries for Effects_AirDestructionStage2 in regards to all the BE #55 kicks. Everyone had been teleported to this inaccessible location, half the server was kicked by the BE #55 error, the other half immediately drop logged to avoid the intentions of the individual that teleported everyone to the location (And yeah I know who it was and yeah I won't be dealing with that asshole again). Regardless of that, point of the post is, I've got the latest BEServer installed, I also installed the BE released #55 patch fix...and it doesn't seem to have done anything but make the #55 error even more common, and its coming up constantly now even in conjunction with situations that involve no vehicles or vehicle explosions. Lost our chopper to it as well. Oddly enough I WAS flying the chopper, and I was not kicked for #55, I was simply teleported to the room. Chopper must have gone down over where I was flying at the time. So...GG..try again please?