Need help coding mission files

[the bunny lover 1]

Hello I am the bunny lover i am in search for a coder that can edit mission files and install add on's we will be willing to pay the coder if he can get the server working with all of our add on's with out any trouble. add our owner of the server on skype. His skype name is le.oneleg. please we need to get our server working again!  :lol:

[AmberHelios 2071]

what addons are you looking at adding and to what mod/map of dayz 

[Oneleg 0]

what addons are you looking at adding and to what mod/map of dayz 

Headshot suicide, debug monitor, Self bloodbag, AI, Auto-refuel, and Cannablism. (Also if you could tell me how to remove BE restrictions, and unban vehicles, that'd be great.)

Edited September 7, 2013 by Oneleg

[AmberHelios 2071]

to unban vehicles you need to use rmod 

 

the script your looking at adding have really good tutorials for on open dayz i suggest you try yourself first and if you run into problems send me a pm with your files and a copy of your servers rpt and i sort it and tell you where abouts you went wrong if you did 

 

doing it this way will give you a better understanding of how the game code works and if you have any problems you don't have to wait for someone else.

 

for be kicks the only way to really do them is to do the following 

 

check the log - search for "#12345" where the number is the restriction you got kicked for. It'll show the code block that kicked you. Find that line in scripts.txt - it will be the line number + any commented lines, so the quickest way is to go to line 12345 (etc) and then keep looking past there until you find the "5 commandthatkickedyou" line. 

Would be easier to explain if you included log info, but here's an example using some random stuff in my log file..

So, the number was #23. Searching scripts.log for #23 I find this:

 

08.02.2013 12:01:36: SOMENAME (123.456.789.12:2304) XXXXXXGUIIDXXXXXX - #23 "playActionNow "Die";};player allowDamage true;player enableSimulation true;0 cutText ["", "BLACK IN",3];

So I look in scripts.txt, starting at line number 23 and looking at the first word on each line until I find something that matches my code block. Here we go, line #25 - "1 enableSimulation" followed by a bunch of other stuff. 

So, we don't want to kick (or in this case log - doesn't matter, same process) for this anymore. BattlEye is freaking because it sees "enableSimulation." I need to tell it that this particular code is legit - so, at the very end of the line that starts with enableSimulation, I put a space, and the following:

Code:

!"player enableSimulation true;"

 

So what we've told BE now is that enableSimulation, in general, is bad -- unless you see it in that exact format in the quotes there, in which case you can safely ignore it. Just make sure you copy and paste that exact line containing the "bad" command.

The only extra tricky bit -- If your code has quotes in it, like this for instance:

 

0 cutText ["", "BLACK IN",3];

You'll need to escape each of the quotes like this:

 

!"0 cutText [\"\", \"BLACK IN\",3];"

That way BE can tell the difference between a quote in the code and the quotes that are wrapping around the entire block of code.

 

 

hope this helps feel free to pm me anytime 

[Oneleg 0]

to unban vehicles you need to use rmod 

 

the script your looking at adding have really good tutorials for on open dayz i suggest you try yourself first and if you run into problems send me a pm with your files and a copy of your servers rpt and i sort it and tell you where abouts you went wrong if you did 

 

doing it this way will give you a better understanding of how the game code works and if you have any problems you don't have to wait for someone else.

 

for be kicks the only way to really do them is to do the following 

 

check the log - search for "#12345" where the number is the restriction you got kicked for. It'll show the code block that kicked you. Find that line in scripts.txt - it will be the line number + any commented lines, so the quickest way is to go to line 12345 (etc) and then keep looking past there until you find the "5 commandthatkickedyou" line. 

Would be easier to explain if you included log info, but here's an example using some random stuff in my log file..

So, the number was #23. Searching scripts.log for #23 I find this:

 

08.02.2013 12:01:36: SOMENAME (123.456.789.12:2304) XXXXXXGUIIDXXXXXX - #23 "playActionNow "Die";};player allowDamage true;player enableSimulation true;0 cutText ["", "BLACK IN",3];

So I look in scripts.txt, starting at line number 23 and looking at the first word on each line until I find something that matches my code block. Here we go, line #25 - "1 enableSimulation" followed by a bunch of other stuff. 

So, we don't want to kick (or in this case log - doesn't matter, same process) for this anymore. BattlEye is freaking because it sees "enableSimulation." I need to tell it that this particular code is legit - so, at the very end of the line that starts with enableSimulation, I put a space, and the following:

Code:

!"player enableSimulation true;"

 

So what we've told BE now is that enableSimulation, in general, is bad -- unless you see it in that exact format in the quotes there, in which case you can safely ignore it. Just make sure you copy and paste that exact line containing the "bad" command.

The only extra tricky bit -- If your code has quotes in it, like this for instance:

 

0 cutText ["", "BLACK IN",3];

You'll need to escape each of the quotes like this:

 

!"0 cutText [\"\", \"BLACK IN\",3];"

That way BE can tell the difference between a quote in the code and the quotes that are wrapping around the entire block of code.

 

 

hope this helps feel free to pm me anytime 

I've tried doing it myself, but yea, I will try one more time, and I will send you the file if it does not work. Thank you for the help.

 

I'd also like to mention that we are running 1.7.6.1 build of DayZ, so compatibility when it comes to the mods, should be no issue.