Jump to content

gopostal

Member
  • Posts

    142
  • Joined

  • Last visited

Posts posted by gopostal

  1. i have since tested this and it only happens when i teleport while inside of a vehicle. it just dont save the vehicle location after restart unless i get out, get in and drive a couple feet, but i resolved the issue

    If you look at your last log you posted it doesn't contain a single DZMS entry. If you made changes post another log but look for some DZMS lines where the mod is initializing, otherwise it's not even loading with your server.

  2. See this part:

    23:37:31 Warning Message: Script z\addons\dayz_server\init\server_functions.sqf not found
    

    That's gonna be a bit of a problem ;)  It looks like your folder setup isn't being called correctly. BTW, sorry I missed you guys. First of the month is always bad for the mailman. I'm off tomorrow (Thursday) and I'll be free all day if you still need setup help.

  3. You need to find and fix this:

    18:56:46 Error in expression <er getVariable["lastPos",_charPos];
    if (count _lastPos > 2 and count _charPos > >
    18:56:46 Error position: <count _lastPos > 2 and count _charPos > >
    18:56:46 Error count: Type Number, expected Array,Config entry
    18:56:46 File z\addons\dayz_server\compile\server_playerSync.sqf, line 70
    

    Any time you have a continuing error like that it has to be addressed because Arma is a sequential engine when it follows the sqf file. What I mean by that is that if my sqf file has 800 lines and the code errors on line 20 then the rest of the 780 lines never get read. This can cause all sorts of errors down the line in cascading fasion. Just think if you made a typo in your init file somewhere in the middle and you'll see how important this concept is.

     

    tl/dr:

    If you see error lines specifically quoted by number like this:

    18:56:46 File z\addons\dayz_server\compile\server_playerSync.sqf, line 70
    

    They MUST be fixed.

  4. Well done severed, that's a huge help. However you need to go a little further. The log you posted barely has the server getting started (only about 2 minutes worth of startup). Many things don't initialize until someone actually joins the server so restart your server, join and play a little while. Maybe even die once. Then post your log from that. You'll see a huge amount more data being written once you add in a live player.

  5. ZG, I'll be in my teamspeak for the next 30 minutes or so: legion.teamspeakserverhost.com:21929

     

    It's not terribly complicated but you need to have live access to the database using something like HeidiSQL. Provided you have that and you know your PlayerID then here are the steps you can follow (this is only one way, there are much easier ways if you use infistar or install certain mods to the server):

     

    1. Travel to the exact spot you want the mission/squad/patrol/whatever to spawn.

    2. Escape out of game to the lobby. DON'T disconnect. This will update your position to the database.

    3. Using Heidi or whatever DB program go to character_data and find your PID. Your PID can be found at the bottom of your profile screen in case you need to get that.

    4. Make sure that the column "Alive" has a "1" in it. This will be your current alive character. Having a "0" means that character is dead.

    5. Find the column "Worldspace" for your PlayerID that is alive and current and copy that number series down exactly as you see it.

    6. Using my post above clean up your coordinates and you are ready to rock.

     

    If you need more coords then just rejoin the server, move to the next position, and repeat.

     

    Like I said, there are much easier ways using other things but this is about as stone simple a way as you can get for any server admin running any map/mod.

  6. Location does NOT need to be converted, though you can dispense with the radial orientation part. For example if you had this as your position:

    [271,[16905.2,6272.22,0.00584412]]
    

    you can dispense with the first number as it tells the direction you are facing (out of 360 degrees). You need this part:

    [16905.2,6272.22,0]
    

    and you can almost always just use zero on the last one. The engine will place the object to ground level for you.

  7. What does your rpt log have to say about the mission spawning?

     

    Guys, it's just nearly useless to post your code without an rpt to go along with it. Yeah, we could debug it line by line but the engine already does that AND tells you exactly where the problem is.

     

    Edit: your problem is here

    f ((_x == 1) && (_RPG > 0)) then {
    _unit addweapon "RPG7V";
    _unit addmagazine "PG7V";
    _unit addmagazine "PG7V";
    

    Keep looking and you'll see what you did. BTW, the rpt will tell you too. THAT'S why you post that too.

  8. Yes I did. It's not nearly as bad as I thought it would be. You can combine those into arrays like this. A chunk of your original:

    // text removed
    [[2126.88,7086.95,0],2,1,"Random",4,"","","Random"] call spawn_group;
    // text removed
    [[2153.68,7098.58,0],2,1,"Random",4,"","","Random"] call spawn_group;
    // text removed
    [[2185.64,7080.15,10.797],2,1,"Random",4,"","","Random"] call spawn_group;
    // text removed
    [[2209.8,7049.18,7.861],2,1,"Random",4,"","","Random"] call spawn_group;
    

    into:

    //Location1, location2, location3, location4
    [[[2126.88,7086.95,0],[2153.68,7098.58,0],[2185.64,7080.15,10.797],[2209.8,7049.18,7.861]],2,1,"Random",4,"","","Random"] call spawn_group;
    
    

    You can easily combine all like spawns in this manner and compress down your sqf tremendously.

  9. To all you guys having issues: Please post your server rpt file somewhere and link in to your help request post. It makes it so much easier for us to find the issue and it saves 2 or 3 posts where we have to ask for it. Be sure you get the rpt from when the server was having the issue too.

     

    The plus side of this is every single person I've helped with their AI setups I've found other things in their rpt log that they needed to address too. Posting yours will not only highlight things you know are broken but may shine a light on things you aren't aware of.

  10. I haven't tested it to say it works perfectly or not but you could try changing the way position is defined in the creation parts of the script. For instance you would have this

    [[8555.83,16947.9,0.002],                  //position
    

    for one of your fixed gun so try to add orientation into it by changing that to

    [244,[8555.83,16947.9,0.002]],
    

    The 244 is the 360 degree orientation radial used as the static guns 'center' of fire. Now one thing to be absolutely SURE of is to preserve the bracketing. This is going to add another set of brackets so don't cut them down by one. For example you first have this:

    [[_position select 0, _position select 1, 0],                  //position
    4,						  //Number Of units
    1,					      //Skill level 0-1. Has no effect if using custom skills
    "Random",			      //Primary gun set number. "Random" for random weapon set.
    4,						  //Number of magazines
    "",						  //Backpack "" for random or classname here.
    "CZ_Special_Forces_GL_DES_EP1_DZ",						  //Skin "" for random or classname here.
    "Random",				  //Gearset number. "Random" for random gear set.
    true
    ] call spawn_group;
    

    but in order to add radial orientation code you would then end up with this:

    [[123,[_position select 0, _position select 1, 0]],                  //position
    4,						  //Number Of units
    1,					      //Skill level 0-1. Has no effect if using custom skills
    "Random",			      //Primary gun set number. "Random" for random weapon set.
    4,						  //Number of magazines
    "",						  //Backpack "" for random or classname here.
    "CZ_Special_Forces_GL_DES_EP1_DZ",						  //Skin "" for random or classname here.
    "Random",				  //Gearset number. "Random" for random gear set.
    true
    ] call spawn_group;
    
    

    where "123" is the added orientation. See how it added a new set of brackets to that first line? Be sure to do that or it won't work at all. If you test this let me know how it goes. It's something I always meant to try and never got around to doing.

     

  11. Here's a copy of mine:

    <Scheduler>

    <!--Restart (00:00)-->

    <job id="1">
    <time>23:30:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 30 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="2">
    <time>23:45:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 15 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="3">
    <time>23:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 10 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="4">
    <time>23:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Get to safety and hide vehicles !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="5">
    <time>23:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 5 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="6">
    <time>23:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 You run the risk of losing gear if you don't disconnect !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="7">
    <time>23:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 1 minute!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="8">
    <time>23:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Log out now, you might lose gear !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="9">
    <time>00:00:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>#shutdown</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <!--Restart (06:00)-->

    <job id="10">
    <time>05:30:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 30 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="11">
    <time>05:45:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 15 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="12">
    <time>05:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 10 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="13">
    <time>05:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Get to safety and hide vehicles !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="14">
    <time>05:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 5 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="15">
    <time>05:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 You run the risk of losing gear if you don't disconnect !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="16">
    <time>05:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 1 minute!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="17">
    <time>05:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Log out now, you might lose gear !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="18">
    <time>06:00:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>#shutdown</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <!--Restart (12:00)-->

    <job id="19">
    <time>11:30:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 30 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="20">
    <time>11:45:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 15 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="21">
    <time>11:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 10 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="22">
    <time>11:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Get to safety and hide vehicles !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="23">
    <time>11:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 5 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="24">
    <time>11:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 You run the risk of losing gear if you don't disconnect !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="25">
    <time>11:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 1 minute!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="26">
    <time>11:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Log out now, you might lose gear !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="27">
    <time>12:00:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>#shutdown</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <!--Restart (18:00)-->

    <job id="28">
    <time>17:30:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 30 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="29">
    <time>17:45:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 15 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="30">
    <time>17:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 10 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="31">
    <time>17:50:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Get to safety and hide vehicles !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="32">
    <time>17:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 5 minutes!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="33">
    <time>17:55:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 You run the risk of losing gear if you don't disconnect !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="34">
    <time>17:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Server restart in 1 minute!</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="35">
    <time>17:59:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Log out now, you might lose gear !</cmd>
    <cmdtype>0</cmdtype>
    </job>

    <job id="36">
    <time>18:00:00</time>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>#shutdown</cmd>
    <cmdtype>0</cmdtype>
    </job>

    </Scheduler>

     

    This one is set up on a 6 hour restart schedule with a couple of nag warnings as you get really close. Feel free to edit as you wish, it should give you a really good template to follow.

     

    If you want to add nag messages every so often here's more you can add:

    <!-- show text ingame every 75 min -->
    <job id="37">
    <time>007500</time>
    <delay>000000</delay>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 There is NO PVP, you will be banned if you do!</cmd>    
    <cmdtype>0</cmdtype>
    </job>

    <job id="38">
    <time>007501</time>
    <delay>000000</delay>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 All bans are reported to the central database.</cmd>
    <cmdtype>0</cmdtype>            
    </job>
        
    <job id="39">
    <time>007502</time>
    <delay>000000</delay>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Our sister server runs Napf PVP 68.232.188.52:2302</cmd>
    <cmdtype>0</cmdtype>            
    </job>

    <job id="40">
    <time>007503</time>
    <delay>000000</delay>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Locked vehicles are not to be touched, unlocked are fair game.</cmd>
    <cmdtype>0</cmdtype>            
    </job>

    <job id="41">
    <time>007504</time>
    <delay>000000</delay>
    <day>1,2,3,4,5,6,7</day>
    <loop>1</loop>
    <cmd>say -1 Teamspeak: legion.teamspeakserverhost.com:21929 </cmd>
    <cmdtype>0</cmdtype>            
    </job>
    </Scheduler>

     

    Just edit the text to what you want and set the <time> to your chosen replay schedule. I use 75 minutes and I know that seems like a long time but players get irritated if you pop shit up every 15 minutes saying the same thing over and over. Lastly be sure that you slip this section in before the "</Scheduler>".

  12. The problem with that Finn is each time you expand the spawn area you restrict the spots where missions can properly spawn. If you are truly dedicated to making a proper experience for your players you can use the sample mission I posted as a tutorial and build your missions by hand. Once you code the mission to spawn in one spot (instead of random) it opens up the possibilities to be anything you want. For instance you could create a mission that spawns in Lenzburg and call it "Lenzburg Massacre". In the mission file just spawn many small groups of AI (1-3 members) spread all over the city. It would take an hour for two players to properly clear the city if you did it right.

     

    There's just so much that can be done with WAI if you only put some effort into the setup. It got boring because no one made anything but "spawn a group of soldiers". Try out some of the custom missions I posted to get an idea of the variety you can create even with such a limited toolbox.

  13. My guess is you have an errant brace somewhere or one is missing. It's got to be right in the declaration part of the mission names, should be an easy fix. My email is agutgopostal at hotmail dot com if you want to trade files privately if you have trouble fixing it.

  14. Dude, I really appreciate that. No one takes the trouble to post their entire log and it just helps so damn much. I see a few problems:

    21:17:24 Warning Message: Script z\addons\dayz_server\WAI\missions\missions\any.sqf not found
    

    This looks like your mission declaration needs to be cleaned up some. Post me your missionCfg.sqf and I'll fix it for you. It's trying to spawn a mission that doesn't exist and so it crashes out.

     

    Also I see a metric shit ton of these errors:

    21:04:43 taviana\silnice\semafor.p3d: house, config class missing
    21:04:43 taviana\silnice\semafor.p3d: house, config class missing
    21:04:43 taviana\silnice\semafor.p3d: house, config class missing
    21:04:43 taviana\silnice\semafor.p3d: house, config class missing
    21:04:43 taviana\silnice\semafor.p3d: house, config class missing
    21:04:46 ca\misc\piskoviste.p3d: house, config class missing
    21:04:46 ca\misc\houpacka.p3d: house, config class missing
    21:04:46 ca\misc\houpacka.p3d: house, config class missing
    21:04:47 taviana\budovy\rov_nam.p3d: house, config class missing
    21:04:48 taviana\budovy\roh_nam.p3d: house, config class missing
    21:04:48 taviana\budovy\rov_nam.p3d: house, config class missing
    21:04:48 taviana\budovy\rov_nam.p3d: house, config class missing
    21:04:49 taviana\silnice\semafor.p3d: house, config class missing
    21:04:49 taviana\silnice\semafor.p3d: house, config class missing
    21:04:49 taviana\silnice\semafor.p3d: house, config class missing
    

    Can someone confirm if this is normal for Tavi or does he have a problem on his server install?

  15. OMG, I finally figured it out! This was REALLY pissing me off but this is how you fix it...

     

    Go into your battleye folder and make sure your beserver.cfg has the settings you want. Next delete the BEServer_active_XXXX.cfg and let the server create you a new one by restarting.

     

    Yeah it's really that simple and it instantly fixed both my servers.

×
×
  • Create New...