MagistratMay
New Member
- Joined
- Dec 7, 2014
- Messages
- 33
Hello Guys,
I wanted to know if you have any plans for a BDO Bot.
I wanted to know if you have any plans for a BDO Bot.
Their anti-***** is very, very intrusive, with their drivers. Most likely not sadly.
XIGNCODE is so easy to bypass it's a joke. The most recent method (and easiest) is just to lock access to a few files while the bot is running. No third-party program is needed. The Buddy team could just setup the bot to do it on launch (the files would automatically unlock when the bot closes). Then XIGNCODE can't block the bot from running and it can't even create logs to send back to Daum. It might look suspicious that they're not getting any logs from you but lack of proof isn't guilt (at worst it would get you flagged for investigation but they haven't banned a single bot yet for it so I doubt it).
I would gladly dev for a BDO Buddy bot (currently doing work on ViperBot but it's so basic/bad). It really wouldn't be hard for the Buddy team to do either. Hope they pick it up soon.
And then you log in the next day without disabling Xigncode, and they feed up the last 48hrs of accessed files from prefetch. Xigncode is way too unsafe to make a proper bot around, without enforcing users to always disable Xigncode.
Mine are disabled 24/7. I went the route of setting permissions to the log files (both the xigncode.log and the crash dump logs) to DENY ALL so they're always blank (BDO opens fine with no errors like this). I also go overkill and have a firewall setting to block all "Outgoing" traffic from XIGNCODE (you have to toggle that off long enough to open BDO though, and it's overkill/unnecessary at this point I think).
You could also just go the route of making a custom game launcher, that way even when users aren't using the bot it still locks and blocks everything. Here's what one of the Viper users made:
https://github.com/stooged/DGGlobalLauncher
![]()
![]()
![]()
And then you log in the next day without disabling Xigncode, and they feed up the last 48hrs of accessed files from prefetch. Xigncode is way too unsafe to make a proper bot around, without enforcing users to always disable Xigncode.
I can't speak for other bots, since I don't know their protection schemes. (I know a certain few other bots have zero protection whatsoever, but I won't name names)
Xigncode is just a tricky anti-*****, since it is more than happy to update itself mid-gameplay and do a new scan. Disabling it sends big red flags to the servers, tampering with it sends even bigger flags. All of these things are causing a large surface area for being banned.
During my few months of researching the game, and Xigncode specifically (at which point I wrote a custom driver to hide the bot, and allow it to access the game), I found that the RU version is actually more difficult to work with, than the NA/EU version. That said, I can't comment on whether it's safe or not. I personally was not banned for any of the bypasses (and final "hide and seek" approach) that I came up with, but YMMV. Fact is, unless you are always on top of making sure Xigncode can't send logs, and can't scan properly, you are at risk. It only takes 1 mistake to get you banned.