Deprecated: The behavior of unparenthesized expressions containing both '.' and '+'/'-' will change in PHP 8: '+'/'-' will take a higher precedence in /home/iano/public_html/tpforums-vb5/forum/includes/class_core.php on line 5842

PHP Warning: Use of undefined constant MYSQL_NUM - assumed 'MYSQL_NUM' (this will throw an Error in a future version of PHP) in ..../includes/init.php on line 165

PHP Warning: Use of undefined constant MYSQL_ASSOC - assumed 'MYSQL_ASSOC' (this will throw an Error in a future version of PHP) in ..../includes/init.php on line 165

PHP Warning: Use of undefined constant MYSQL_BOTH - assumed 'MYSQL_BOTH' (this will throw an Error in a future version of PHP) in ..../includes/init.php on line 165

PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in ..../includes/functions_navigation.php on line 588

PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in ..../includes/functions_navigation.php on line 612

PHP Warning: Use of undefined constant misc - assumed 'misc' (this will throw an Error in a future version of PHP) in ..../global.php(29) : eval()'d code(6) : eval()'d code on line 1

PHP Warning: Use of undefined constant index - assumed 'index' (this will throw an Error in a future version of PHP) in ..../global.php(29) : eval()'d code(6) : eval()'d code on line 1

PHP Warning: Use of undefined constant misc - assumed 'misc' (this will throw an Error in a future version of PHP) in ..../includes/class_bootstrap.php(1422) : eval()'d code(4) : eval()'d code on line 1

PHP Warning: Use of undefined constant index - assumed 'index' (this will throw an Error in a future version of PHP) in ..../includes/class_bootstrap.php(1422) : eval()'d code(4) : eval()'d code on line 1

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 85

PHP Warning: Use of undefined constant onlinestatusphrase - assumed 'onlinestatusphrase' (this will throw an Error in a future version of PHP) in ..../includes/class_core.php(4684) : eval()'d code on line 6
Regarding the recent banishments (Programmers need your input) - Page 12
Page 12 of 14 FirstFirst ... 21011121314 LastLast
Results 111 to 120 of 136

Thread: Regarding the recent banishments (Programmers need your input)

  1. #111
    Senior Member
    Join Date
    Mar 2007
    Posts
    495

    Regarding the recent banishments (Programmers need your input)

    I bet they just pick the free account hehe

  2. #112
    Junior Member
    Join Date
    May 2008
    Posts
    25

    Regarding the recent banishments (Programmers need your input)

    "About 4000 of the 4959 banished accounts are premium accounts."

  3. #113

    Regarding the recent banishments (Programmers need your input)

    Quote Originally Posted by WRtB
    "About 4000 of the 4959 banished accounts are premium accounts."
    sure, and most of them have premium for 10 years... They can tell what they want cuz the black list will not be published, same as proofs etd.

  4. #114
    Senior Member
    Join Date
    Apr 2008
    Posts
    133

    Regarding the recent banishments (Programmers need your input)

    Hey guys,

    I was just thinking some about Tibia's past, how they started, what security leaks they had and then i remembered the XTEA generation algorithm wich was really insecure. There was the possibility to bruteforce.
    Remember, update 8.22 fixed this with getting the mouse position to generate a random XTEA key.

    Now, may it be possible to use this method for getting the mouse position to check if the player is cheating? Everytime a normal player attacks a monster, normally he klicks on it in the battlelist or at the screen. Bots do not klick on the monster, they just send an attack packet, even if Tibia is minimized.

    for more information about the mouseposition thing read some here:
    http://www.tpforums.org/forum/showth...?t=1959&page=9

    //Jan

  5. #115

    Regarding the recent banishments (Programmers need your input)

    Quote Originally Posted by Jan
    Hey guys,

    I was just thinking some about Tibia's past, how they started, what security leaks they had and then i remembered the XTEA generation algorithm wich was really insecure. There was the possibility to bruteforce.
    Remember, update 8.22 fixed this with getting the mouse position to generate a random XTEA key.

    Now, may it be possible to use this method for getting the mouse position to check if the player is cheating? Everytime a normal player attacks a monster, normally he klicks on it in the battlelist or at the screen. Bots do not klick on the monster, they just send an attack packet, even if Tibia is minimized.

    for more information about the mouseposition thing read some here:
    http://www.tpforums.org/forum/showth...?t=1959&page=9

    //Jan
    Yea but Tibia Client dont send anything new to server

  6. #116
    Senior Member
    Join Date
    Apr 2008
    Posts
    133

    Regarding the recent banishments (Programmers need your input)

    Are you sure? Maybe they send it in a way where we wouldnt realise it as an "im a botter" information. Something stupid that seems normal but isnt. We thought about a packet that starts the "scan for bot mode" and that this packet is only sent once a month. Maybe it just hasnt been captured yet?

  7. #117

    Regarding the recent banishments (Programmers need your input)

    So they need to store informations from this one month at our disc. Cuz its big possibility that u will not use bot in the day that client send infos.

  8. #118
    Junior Member
    Join Date
    Oct 2008
    Posts
    3

    Regarding the recent banishments (Programmers need your input)

    Quote Originally Posted by DarkstaR
    I've added this into the waypoint making of my bot. When you make a ground waypoint, it randomly chooses other positions within 4 squares of that on,e then uses the dat reader to make sure they are walkable. It then puts them at the end of the waypoint like:

    1,2:3,2:1,-1
    That means
    It can go to the set position X+1 and Y+2, X+3 and Y+2, and X+1 and Y-1

    Pretty easy to implement.
    just wondering will it pick a random square after every kill when it starts to move towards that wpt again?

  9. #119

    Regarding the recent banishments (Programmers need your input)

    Not now it only does it in waypoint creation. But it will get up to 6 randoms for each space so im pretty sure thats undetectable as a set path

  10. #120
    Junior Member
    Join Date
    Feb 2009
    Posts
    2

    Regarding the recent banishments (Programmers need your input)

    Its just a matter of time and testing to work around it, I find it amusing they are so scared to give any details about what it is because it must be easy to work around.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •