Guys help me out with: Script Restriction #5

Discussion in 'Trouble Shooting' started by Vizteck, Sep 16, 2013.

  1. Vizteck

    Vizteck New Member

    Joined:
    May 15, 2013
    Messages:
    15
    Likes Received:
    0
    Hey guys, i have an issue with overwatch serverfiles 0.2.4 and x00 antihack.
    People are getting kicked with reason: Script Restriction #5
    As i searched for any answears i get the idea i need to whitelist in script.txt the lines wich is kicking poeple in script.log, correct me if i'm wrong.

    So basicly my script.txt looks like this:
    and people are getting kicked by this reason:
    So if i understund correctly, i need to whitelist:
    Can someone lead me how to do it right, if i'm correct in my research!
    Thank you and i'm realy sory for my bad english :(
     
  2. Vizteck

    Vizteck New Member

    Joined:
    May 15, 2013
    Messages:
    15
    Likes Received:
    0
    UP, does it is so hard to just tell me one line how to correctly whitelist these kicks?
     
  3. Bassline

    Bassline Well-Known Member

    Joined:
    Feb 10, 2013
    Messages:
    109
    Likes Received:
    22
    Tell them to turn off there Arma 3 hacks then they may get in the server:eek:
     
  4. Vizteck

    Vizteck New Member

    Joined:
    May 15, 2013
    Messages:
    15
    Likes Received:
    0
    No its for everyone, antihack is derping...
     
  5. ebay

    ebay OpenDayZ Guru!

    Joined:
    Jan 9, 2013
    Messages:
    828
    Likes Received:
    296
    The antihax script scan is running on all players when they join the server. Since it is scanning for those bad names BE will kick everyone for running code with those names in it.

    Solution is remove/comment out those lines or add an exception. It is silly to include most of these in your scripts.txt because they are already being blocked by antihax variable scan and script scan. However, if you want to do it anyway you would do it like this:
    Code:
    5 Shadowy_NONRE !"Shadowy_NONRE\setup\startup.sqf"
    This is only useful if someone is running a script with the text "Shadowy_NONRE" in it. Nine times out of ten that person would have already been blocked by antihax script scan, so it is kind of pointless. Similarly kicking for text like _salamence, _skarmory, etc. is also silly because those variables are already blocked by antihax variable scan.
     
  6. Vizteck

    Vizteck New Member

    Joined:
    May 15, 2013
    Messages:
    15
    Likes Received:
    0
    But if i comment out or remove thouse, i have other problems.
    For example people start to get kicked by pressing "Insert or Tab" e.t.c :/
    Seems its pointless to try to fix it, cuz people gona get kicked anyways!
     
  7. ebay

    ebay OpenDayZ Guru!

    Joined:
    Jan 9, 2013
    Messages:
    828
    Likes Received:
    296
    The bad key combination kicks are from the antihax logging the player's name with parenthesis or brackets. For example, here is a player who pressed shift + tild in publicvariable.log:
    Code:
    02.10.2013 01:13:39: Echo Walrus (71.185.218.86:3393) ceaebbe33a6be493584c581b06f95564 - #0 "PVAHR_214729" = ["Echo Walrus","88823622","Key: VG(Shift + tild)"]
    With default BE filters he will be kicked by this line in publicvariableval.txt because he is running code with a "(" in it:
    Code:
    5 "(" !"TELEPORT REVERT"
    So, you just add an exception like this:
    Code:
    5 "(" !"TELEPORT REVERT" !"VG(Shift + tild)"
    All other BE kicks can be fixed in a similar manner. Just look in the corresponding .log file and find the line that is kicking the player. Look at what the code looks like and add an exception for it.

    EDIT: Also see my posts in this thread:
    http://dayzepoch.com/forum/index.php?/topic/1512-value-restriction-293/?p=14053
     
    Vizteck likes this.
  8. Vizteck

    Vizteck New Member

    Joined:
    May 15, 2013
    Messages:
    15
    Likes Received:
    0
    Thank you wery much, it helped me alot! :)
     

Share This Page