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 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

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
Cipsoft goes into bot detection
Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Cipsoft goes into bot detection

  1. #1

    Cipsoft goes into bot detection

    Hey guys,

    While checking Craban's twitter (Cipsoft product manager) I've seen his latest tweet..

    "Now getting ready for another conference call with that possible partner for bot detection, still all in evaluation stages though."
    https://twitter.com/Crabans_Beak/sta...08555102830592

    What do you guys think about it? What "options" have they got?

    Let's discuss
    Last edited by szulak; 09-12-2013 at 08:37 AM. Reason: typos

  2. #2
    Senior Member
    Join Date
    Jan 2008
    Location
    Cambridge, England
    Posts
    725
    Their options are primarily to farm data (which they admitted in the latest monthly article that they have been doing for years) or to try to detect using hidden information in the transfer protocol. Chances of them using hidden information are slim, since someone would have seen and caught on to it. Beyond that there are issues around the legality of acquiring information without the consent or awareness of the end user (potentially massive law suits, these have been brought against most gaming companies and the majority fail, but it all boils down to the size of the company involved. A company such as Blizzard has a large team of lawyers who cover their arses. Tibia just has it's 40 employees (just a guess, not a clue in reality, haven't checked in so long) and probably a contracted solicitor who drew up the current terms and privacy policy for them.

    Data farming is the most likely method. That doesn't mean to say that performing any action a large number of times is the cause, but what it means is that performing X, Y, and Z actions a ridiculous number of times in an identical fashion will most certainly raise the alarm. Beyond that it's down to what the actions in question are, how they are determined to have been so fast or repetitive, and if they could be proven to be incorrect by a feasibility study (the one part where data mining falls apart is when that one solicitor who plays the game gets banned and works to get back at the company).

  3. #3
    @XtrmJash
    Data farming might be their choice as you said, but why would they contact another companies in this purpose and not implement it on their own?

    IMO, they will not implement any client-side detection (bot creators has proven that they are able to reverse the whole Tibia client on small pieces), and could easily bypass such thing. Solutions like GameGuard wouldn't change anything at all, there are already know methods how to bypass such software.

  4. #4
    Quote Originally Posted by szulak View Post
    @XtrmJash
    Data farming might be their choice as you said, but why would they contact another companies in this purpose and not implement it on their own?

    IMO, they will not implement any client-side detection (bot creators has proven that they are able to reverse the whole Tibia client on small pieces), and could easily bypass such thing. Solutions like GameGuard wouldn't change anything at all, there are already know methods how to bypass such software.

    That's a very loaded assumption, though. If they are contacting a company, they might be seeking a fresh implementation of bot protection from RE professionals. I can promise you that, if CipSoft hired someone with my skills level who was serious, they could easily make it very hard to touch the client. CipSoft may not have the skills as their dev team is programmers, but someone who actually focuses on RE based development can definitely make some huge craters.

  5. #5
    Looking on the Cipsoft way of 'solving' things they will most likely use something what's checked & proven, like GameGuard (or something). I didn't mean that hiring RE professional wouldn't solve this problem, of course it would. Some time ago Valve was in the same shoes with cheaters - they took their own way and implemented VAC.

  6. #6
    Senior Member
    Join Date
    Jan 2012
    Posts
    417
    imo, there are two main options to cipsoft:

    • Cut bots out of the game and try to save the game (using some serious anti-bot professionals / tools and alike)
    • Keep Tibia how it's actually (conniving to bots, deleting them slowly) and watch the game die slowly as we are seeing year-by-year.


    But honestly, I think that Tibia's decline is not only caused by bots, it's deeper in how it has been designed each update. For example, each update CipSoft turns Tibia's pvp even worse, they don't listen to its users community about their taste at all, etc, etc, etc.

  7. #7
    @Blequi

    But do really 100% removing bots would make Tibia get more players? I don't think so, with or without bots Tibia is slowly dying, removing them (us) Will just decrase the count of players, i don't think ppl will start playing Tibia becouse bots are gone. People who played the game when it was on it's best in 06'-07' are growing up, and new players are not starting play it cause the standards has changed and now there are games like GTA V, LoL, etc, etc. whitch attracts kids now.

  8. #8
    Senior Member
    Join Date
    Jan 2012
    Posts
    417
    Quote Originally Posted by MeNi View Post
    @Blequi

    But do really 100% removing bots would make Tibia get more players? I don't think so, with or without bots Tibia is slowly dying, removing them (us) Will just decrase the count of players, i don't think ppl will start playing Tibia becouse bots are gone. People who played the game when it was on it's best in 06'-07' are growing up, and new players are not starting play it cause the standards has changed and now there are games like GTA V, LoL, etc, etc. whitch attracts kids now.
    IMO, dropping the count of players by cutting off botters and its community is a short-time impact in their user base (and could be a fatal decision in their business, but any business must make critical decisions... in the current state tibia will definitely die in years, it's a fact), but it's a safe strategy for any long-time game, because in the point of view of a fair player (the main target of any game), why would I (hypothetically a fair player) play a game where everybody needs to cheat in some form (PvP, leveling up, growing in any aspect) to have fun?

    if I would part of CipSoft team with full decision power, for sure I have had stick to kill botters definitely, assuming the risk to kill the game.

    IMO, it's a poor business strategy to watch your own business die slowly without doing critical changes, masking the bot problem like they are doing: "hey fair players, we are deleting 1k - 4k botters per update, are you all ok?" when it has been shown by years be the worst option because fair players already noticed and know well that Tibia is conniving with bots.

  9. #9
    They should firstly check how many percent of players are using bot (IMO it's around 25% of community). Cutting 25% of user base will also cut their income about this amount, and if their finance are able to handle such drop of income, they will make more profit in long way. As far as I can see they are following the easier way (for example creating flash client instead of desktop app on mac, or even using frameworks like Qt to make it cross-platform.

  10. #10
    Quote Originally Posted by szulak View Post
    They should firstly check how many percent of players are using bot (IMO it's around 25% of community). Cutting 25% of user base will also cut their income about this amount, and if their finance are able to handle such drop of income, they will make more profit in long way. As far as I can see they are following the easier way (for example creating flash client instead of desktop app on mac, or even using frameworks like Qt to make it cross-platform.
    If you think it is only 25% I have some bad news for you..

Posting Permissions

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