Jump to content

Defent

Member
  • Posts

    720
  • Joined

  • Last visited

Posts posted by Defent

  1. A lot of the addactions in fn_selfactions make the destictions quite easy. For example, to tame a dog:

    if (_isDog && _isAlive && (_hasRawMeat) && _ownerID == "0" && player getVariable ["dogID", 0] == 0) then {
    

    This checks if the dog has the array, raw meat and if the ID is 0. 

    Just check for items, more specifically, something maybe every player has, like bandage or similar. That's a very cheap work around.

     

    You could also check for CharID or PlayerUID and set it to => or <=, =/=. That could also work since traders don't have those ID's if I recall

  2. That makes sense. I'll look in to changing that. Thanks.

     

    The reason why I have it as it is because the numbers set in the orignial settings for the loot (DZMS) uses the same numbers. I.E, where I placed DEFMPistolRate it would say 1 or 2 or what ever. I figured that I could change these with a variable. The point is, I did not really make the loot spawn function, it is migrated from DZMS, but I'll look in to it.

     

    I know the current system is unreliable but I'll see what I can do.

     

     

    The argument you posted did exist before, however, I removed it because I couldnt add a variable to it so that it could be set in DZMSConfig.sqf.(to my knowledge)

  3. I'm working on upgrading their skills too btw. Currently they are weak as shit and don't really fire back, at least not on my live and test servers. I'll post here once I get some resulsts.

     

    Edit:

     

    Ok I managed to fix some of the AI skills, for exampel I did this:

    Changed it to 1 instead of 1.00 or 1,00 (note the , & ,) at around DZMSAIConfig.sqf

    DZMSSkills3 = [	
    ["aimingAccuracy",1],
    ["aimingShake",1],
    ["aimingSpeed",1],
    ["endurance",1],
    ["spotDistance",1],
    ["spotTime",1],
    ["courage",1],
    ["reloadSpeed",1],
    ["commanding",1],
    ["general",1]
    ];

    I'll push this to the GitHub as soon as I get my version a bit more stable.
     

  4. Open config.cfg

     

    Delete

    requiredSecureId = 2;
    

    and comment out or delete

    //regularCheck = "{}";
    

    I got these suggetions from MGT and they seem to have stopped some of the authentication issues. 

    Among other things, I also tweaked my basic.cfg to this:

     

     

    Note that maxbandwith is set for a 1gb connection. Going above that is sort of over-kill. Especially since you probably have a 1gb connection at most.

    MinBandwidth=1097152;
    MaxBandwidth=1073741824;
    MinErrorToSendNear=0.049999997;
    MinErrorToSend=0.0029999993;
    MaxCustomFileSize=0;
    Windowed=0;
    adapter=-1;
    3D_Performance=1;
    Resolution_Bpp=32;
    Resolution_W=800;
    Resolution_H=600;
    
    

    And cleared the character_data table when the steam patch came.

  5. Get your UID, give it to the admins, ask them to go to the root folder, open bans.txt and remove that ID from that list and you should be unbanned. 

    To my knowledge, VAC is not connected. However, if your guid is banned, I believe that you may need a new CD key (account) to play again. But the grey screen is infistar and not battleye. 

  6. Best tip would be to search all the logs you have, battleye filter logs, infistar hack and surv logs if you use those and the arma2oaserver.rpt file. Just use a program like Notepad++ and search for his name in all documents.

     

    If you find something suspicious in say, scripts.log then he's probably a hacker. That's generally how I catch 2/3rds of the scripters and hackers on my servers.

×
×
  • Create New...