KField86

I fixed this today it seems with the new files that were posted this morning. The new scripts.txt, remoteexec.txt and createvehicles.log. These ones.. http://dayzmod.com/f...es/#entry684746 Not getting kicked for 98 anymore. Although I've seen about 15 people in the last 2 hours getting kicked for createvehicle/remoteexec violations. lmao.

Actually. since I can edit those files, being scripts.txt createvehicle.txt and remoteexec.txt ... can I just copy & paste the new information in, while deleting the old stuff and it should work fine? I'm using the ones posted this morning for all 3 files. Will this stop the script restriction kicks? I wouldn't care if it's just doing it to one person, but it kicks the entire server at the same time. I'll start my server up and see what happens.

It's kicking everyone from the server for the same thing. It's a Vilayer server so I can't upload it to the cfgdayz\battleye folder myself since I don't have permission to move files around. I can upload but not move it into the proper folder. Is anyone else with a vilayer server experiencing the same thing. I'm using the one Dwarden posted yesterday. I didn't update the remoteexec folder or anything like that.

Bahaha. Someone get the tiny violin.

Really need to figure out what to do for those of us who are renting from a hoster like Vilayer. I can upload the new file, but cannot do any moving of files in the manager. So I cannot get the new scripts.txt file into my cfgdayz\battleye folder. Anyone else with Vilayer please send me a PM if you've gotten this fixed. I sent in a ticket but I don't know if they'll answer it tonight.

Not true. This happened to me today. I even have it in the server logs. Someone logged in last night on my server, logged into admin, and then restarted the server and changed the slot count. I got a message from Vilayer today that my server would be shut off until I reverted the slot count to 40. I was asleep and I'm the only one with my rcon password. Scanned my computer multiple times for any sign of like a keylogger or anything. It hasn't happened again, and I changed my password..but casey at vilayer told me the same thing.. that there are scripts users can run for malicious intents that allows them to pull the beserver_active.cfg which contains rcon password. Let's hope this doesn't happen again.

Ok, so I have a vilayer game server. I'm still new to the adminning stuff, but can someone else who has a vilayer server tell me how to get this new scripts.txt file once it's uploaded into the cfgdayz\battleye folder? It lets me upload the file, but it won't let me move the file into the proper folder nor will it let me rename the scripts_old.txt file. So right now I'm effectively blind, and it would be the same if I just deleted the damn thing. Is this something Vilayer has to do?

I've done this every time I was teleported with that "To the moon, Alice." hack. I hit abort, and hover over the "Yes/Confirm" button. About half a second before I hit the ground, I press abort, and then when I relog I'm prone on the ground, safe and sound. No damage received.

Dear god shut the fuck up you self entitled twat.

It's definitely not related to server providers. You're all running the same mission, and running off the same hive. This is a problem with the hive, and the new patch code. US 1313 / Vilayer Beta 95883 1.7.2.5. Tents not saving.

Ok, people. Most of you who are stuck at loading are updating their game via six launcher or DayZ commander. This is not the right way to go about it as the new patch/beta hasn't even been seeded to Six Launcher yet by rocket & crew. So here is what you need to do. First thing you want to do, is actually run six launcher. Let it update and verify. Once it is finished and you're at the point where you can select a server and join, manually apply the files into your @DayZ/Addons folder for the 1.7.2.5 patch. Copy & Overwrite everything. Once that is finished, download the 95883 beta and install those files. Now, next step is important. Goto battleye's website and download the latest BEClient.DLL file. Once that is finished, place that DLL file in the steamapps/common/arma 2 oa/expansion/battleye folder. Overwrite the file here. Do this same thing in your USER/APPDATA(This is a hidden folder, so you're going to need to make sure you're not hiding any files/folders) folder. You will find a battleye folder there as well. Overwrite the file inside with the beclient.dll you just downloaded. Now, go back to sixlauncher, find a server and try connecting. Come back and tell me if you're still stuck on loading. Me and my squad (7 guys) all just went through this process exactly, and not a single one of us is experiencing the stuck at loading that everyone is experiencing. We're getting into multiple 1.7.2.5/95883 servers, including our own, very quickly. If not quicker than before. By doing this, you're overwriting what six-launching is updating with the PROPER files. This should fix the problem for you. From that point on, I'd recommend launching thru steam or using dayz commander and avoiding any updating. Feel free to test this out on my server running 1.7.2.5/95883 if you'd like. US 1313. Also, here's another link to a thread with the same exact instructions as me, although maybe it's broken down a bit better lol. http://dayzmod.com/forum/index.php?/topic/68463-attention-fix-for-six-launcher-users-regarding-new-patch/#entry659564

Yes, I checked the logs a while ago when you were first brought up and never saw anything that made me suspect you were cheating. Karou on the other hand was teleporting and spawning in items to himself and others so he was banned. As far as the tent duping goes, unfortunately I can't control that and I never will be able to until it's fixed and unfortunately that will not be the case until DayZ goes stand-alone. I don't know if you're aware but 1313 is now running in NY instead of Florida. Same instance ID and everything, so everything should be where it was saved at. Shitty thing is, this new patch isn't saving things properly to the hive, so things you save in tents disappear on restart. That will halt the duping process a little bit, but the thing is any tents that had duped items in them prior to the update, will always keep spawning back even if destroyed and saved on the next restarts, with the same items in them. I admit, I've duped a few items before but it hasn't been on purpose. I've duped backpacks by putting on ghillies plenty of times, and I'll usually just leave the backpack on the ground to rot away when the server restarts, or maybe someone will get lucky and find it. Also, since we're a squad, sometimes we've ended up with copied items in the past, since we all share tents(spread out around the map. We do not have any camps with multiple tents near each other) and if we put an item in the tent and save it, and then later on someone took that item out and forgot to save the tent, we'd end up with a copy when the server restarts. THANKFULLY this method of duping doesn't work anymore, which in my opinion was the main way to dupe when it came to tents in 1.7.2.4. Lately we've been pretty good with saving every time an item is taken out, but like I said it doesn't matter anymore since the "states" aren't really being saved properly. I can say with utmost certainty that the items I've collected in my 3 tents spread out around the map are legitimate, either found or taken off bodies. You wouldn't believe how many pairs of NVGs I've taken off bodies, as well as rangefinders. It seems like every sniper I take out at the hills in elektro has these, as well as AS50s. Seriously, the CZ550 is more rare than the AS50 and M107 now. That's how silly it's gotten. Anyway, I hope you enjoy the server. Sorry for the mix-up Lead. For the record people, please send any reports to [email protected] if you encounter a hacker. Please leave the time(in EST), location of the encounter, and what happened as well. Also, leave your in game name so I know what to check for in logs. Thanks.

I run a Vilayer game server, so I can't upload the new file and I imagine they'll have to do it.. unless I'm mistaken. The scripts.txt is still scripts_old.txt but I noticed it's 25kb now, so it seems bigger than the last. I can only imagine this is the new one. It also has //new attached to the first line as well. Anyone with a Vilayer server know if I have to do anything, or will they update it through FTP? Kind of clueless honestly.

Just noticed mine was renamed to scripts_old.txt as well. So whats the issue now? I just got the BE message as well asking to use the new script file as well but don't know where to get it, or if Vilayer has already updated it. I did notice in the scripts file, there was a //new attached to the first line. So, do I need to rename it to scripts.txt now and will it function then? Still a newbie to this stuff to be quite honest.

My server is up and working so far. We'll see how long this lasts. Knowing BE, we'll all be global banned within 30 minutes.

Mind in the gutter. Shame on me.

I'll just take that bike off your hands. Now </3 ? :D

Getting kicked for #98 on my own server. No one can get in for even 30 seconds before being kicked. Guess I'll restart the server & call it a night. Hopefully this will be addressed by tomorrow morning. And like someone else already mentioned, the server list does seem to be weird. Servers not showing up like they normally do. I know of the gamespy issues, and what not... but this is different.

Mate it's happening to everyone server wide right now. Some are getting lucky and able to play but for most we're experiencing this problem. The script restriction kick. I'm not saying it's not possible that the guy was hacking and caused this, since it's possible, but that would be a very big coincidence since this is happening to pretty much everyone, including me.. on my own server.

Confirming this. My server is kicking myself and everyone else for #98 and not allowing anyone to connect. I just got this damn thing transferred to NY. I want to play god damnit lol.

Yup. Confirming this. Brand new server just got setup. Got in for about 20 minutes. Then I noticed all new players attempting to join were being kicked for Script Restriction #98. Then I was suddenly kicked, as well as 2 buddies of mine as well. I restarted the server just for shits & giggles to see if it would cure itself but it remains ongoing at the moment.

Yes they are spawning, although some have been found and hidden. :) UPDATE: The server is now in New York. Same instance ID but it is US1313 now. No space. There may be some confusion as it appears the old server is still up and running with the US 1313 designation but we still have the same instance ID? Don't know how that's possible to be honest, but whatever lol. So yes, if you want to continue playing on my server, search for US1313 now. You will see [NY] in the server name to help alleviate possible confusion. I will not be running US 1313. I imagine it will be taken offline shortly.

M24 is a tack driver, aka: It's very very accurate and you can engage targets at further distances reliably. The DMR is a good medium range sniper rifle, but I don't like engaging players at more than 500 meters or so. I guess, if you know how to range with mil-dots and don't plan on engaging players further than 500m out, the DMR is the obvious choice. If you like the idea of being able to accurately shoot out to 800-900m, the M24 wins. Personal choice: m24 every time.

It's not fixed all the way unfortunately. Tested it before. Put half empty magazines in my bag. Logged out and back in. They were all full. Pretty damn stupid.

I was fucking wondering why my logs looked different and why I wasn't getting the same amount of information back. What the actual fuck Rocket?