isoterik

remove them and put them back later when they are more usefull like: stopping zeds. when you run into them there might be a chance that they hurt you/cause bleeding but if you approach them slow there is only a little chance that you will be hurt or so

how about an auto save function everytime you put/take something in/out a tent or vehicle it saves automaticle after useage so noone can duplicate gear with it!

great idea. the devs should do this with the next patch. a complete reset. other games do this aswell in their alpha/beta stage. best example is diablo 3. they did it alot in the beta phase.

you are wrong, it was the m107 tws http://dayzmod.com/forum/index.php?/topic/78686-as50-tws-save-to-hive/page__st__60#entry752275

and whats up with the m107 tws? its even in the dayz weapons.pbo....

look here: http://forums.bistudio.com/showthread.php?121438-How-to-secure-Your-server-Read-here! and use this: http://dayzmod.com/forum/index.php?/topic/71904-new-major-battleye-anti-cheat-features/page__st__20#entry687939 you can also find those files where you get your other stuff from the dayz staff.

could be this #36 icopter" || _v iskindof "plane") then { _v setVehicleInit "[this] spawn BIS_Effects_AirDestruction"; #55 his] spawn BIS_Effects_AirDestruction"; processInitCommands; }; if (_v iskindof "tank") then { _int i got kicked also with #55 as i was in the huey, but i got killed in there and after my death i got kicked :) forgot to mention, the huey disappeared after that :S

the problem is, some of my clanm8s got that in our log to, and i know for sure they are not cheating! and remember, some cheaters run scripts on ppl who never know it and they get logt because of that. but what would be great to get a bit more sure on who is cheating, is when the server admins can see in their logs who shot who! atm there is nothing to track that down. *edit* the commands in the logs are about the view direction and placing something on the ground. btw every cheater i encountered, never was logged and so are the most. dont ban ppl when you are not 100% sure. i know they are a pain in the ass but false alarm is oftern there instead of a lucky catch ,) *edit2* a teleport script dont look like that ;) and i dunno which scripts.txt you use. in the one we use, there is for thoses strings only a 1 infront. that means only log an no further actions.

thats not a cheater. every thing is fine. _item addWeaponCargoGlobal [_iItem,1]; is when you take something and move it into your gear. and the rest is normal too. nothing to worry about. use that till something is better is out there for your scripts.txt http://dayzmod.com/f...ript-detection/ much cleaner script.log ;)

with cords. but got attackt shortly later by a hacker, killed my buddy and me and damaged EVERY vehicle on the server :( and a few of us got kicked by BE in that event -_-

will there be any option to reload the two m240? or must we wait for a server restart?

the smart ones use bypass, someone released just yesterday a "privat bypass" but i think that will get detected soon...

the 1st code quote: ["PG7V"] is ammunition for the RPG7V. i never saw one in dayz so far only the M136. the 2nd code quote: nothing to care about the 3rd code quote: when you press ingame SHIFT+P you get kicked and that comes to the logs the 4th code quote: when you press G to view your inventory that is written into the logs and the 3 other strings are normal too. im testing currently my new scripts.txt and such entrys execpt the ammo and the SHIFT+P kick entry are history then, much better to look at the logs ;)

you have to add: //new in the scripts.txt. but beaware it can cause problems using the old scripts.txt without using the new format/commands for the strings

thats my i uploaded here, but took it down till i edit it correct to the new version, but atm i got server performance issues when using it after i had converted it. dunno why, have to figure out from what its caused by. and when in a string a " is used, and you want that its recognize correct you must also use \"