BiglyBT Extreme Mod by SB-Innovation 2.5.0.0 Beta

[anon]

Is there a guide to set this up to mimic/be undetected? I know there's the guide explaining all the settings, but am I missing anything if I follow the instructions in this post and then follow the instructions for spoofing a client? Just want to make sure I'm not missing anything that would be an easy giveaway.

My tutorial should cover all theoretical and technical aspects well. The only thing you may want to read at this point is the "cheating on..." thread for the tracker(s) you're going to use the mod on. Don't forget to search either, there are good chances whatever you want to know has already been answered before.

Also, GhostCode, I have uploaded the client files you requested.

[sbkk]

This version have same numbers of bug as previous version.

[sigduwksnsksis9283]

how can we optimize cheating more at a traffic sinkhole like places as ipt,tl,fl?
i see popular new game cracks get 500-1k s/l around for 1-3 days at best but lets say i added the torrent 15-50 minutes after it was uploaded and had around 120 seeders and 300 hundred leechers. i instantly start fake seeding with swarm usage but make at best 5gb upload on such a traffic sink upload where even by cheating standards i am safe uploading few hundred gb's but bigly makes around only few gb since red dead redemption(with around 500-800 leechers showing on FL at certain point) was the latest hot torrent and surprisingly i got only 2 gb upload such a hot torrent using the swarm usage..
current enabled settings,



is there any way to optimize or benefit the amount of leechers?
See the last attachment on upload amount. that is absurd

[anon]

The "swarm" settings were added as a reasonable compromise for those who wanted to cheat without routinely checking on their torrents and making minute setting adjustments. All of them de facto err on the side of caution, because it's impossible even for the tracker to have a complete, real-time picture of what the swarm looks like. Since you're likely fake seeding, this is worsened by the fact you'll have very few peer connections which won't be open for long.

Anyway, if you want to buff your upload, you could turn those off and rely solely on 13a, on which you may want to set the first value to 0 for the reason I mentioned. This will provide adequate security for torrents which are already known to be active, but you'll need to be there to reduce or stop fake upload whenever that changes.

[sigduwksnsksis9283]

is there a way to set the upfake speed on this? or is there none since at the moment it is hovering at 3-9Mb/s speed so if i could configure it to be 1-2Mb/s at some torrents with 20 leechers it would be nice.

[anon]

is there a way to set the upfake speed on this?

Unless I'm missing something, you can find that at the bottom of your second screenshot...

[sigduwksnsksis9283]

thanks i thought that it wouldn't account for 13a and thus asked but stupid me

[zxspectrum]

This works for me but the torrent will not start downloading. I've tried spoofing different clients. The same torrent will happily download in normal utorrent.

Edit: Ok, I found the log file but it's not very helpful to me in finding the culprit.

[anon]

This works for me but the torrent will not start downloading. I've tried spoofing different clients. The same torrent will happily download in normal utorrent.

Did you try it with the official, unmodified BiglyBT? Someone reported this problem before and apparently it may be related to character encoding in filenames, although I wasn't able to investigate further.

[zxspectrum]

Did you try it with the official, unmodified BiglyBT? Someone reported this problem before and apparently it may be related to character encoding in filenames, although I wasn't able to investigate further.

I just tried the unmodded BiglyBT and it works. In the modded client it just goes to inactive mode and will not start.
Do you have any ideas about how to debug this?

[Cr@zYiNsEiN]

Hi there,
First, you need to debug this from the client-side. Then if possible, have someone of the staff member of the tracker you are on check it out from the server-side. Yes, I know what I am saying about contacting the tracker's staff member about a modded client. But if this turns into a desperate situation, desperate measures are usually applied by people. You could always say you are testing out a new client that you are making. But we don't need to go there yet.

Here's what you can start with. BiglyBT's logging feature can be found at Tools -> Console (but must be enabled first on Tools -> Options -> Logging). After you've logged the data. It can be found at BiglyBT config folder (%appdata%\BiglyBT on Windows), (~/.BiglyBT on Linux) and ("/Users/<username>/Library/Application Support/BiglyBT/ in Mac OS).

Note:-
1) Make sure you are logging the modded version of BiglyBT.
2) Try and use (if possible) a separate account for logging in case you send out more than one tracker announces. The tracker may see this as weird and might flag your account.
~cloud99

Source:-

http://www.sb-innovation.de/showthread.php?34730-uTorrent-3-5-5-Build-45798&p=359057&viewfull=1#post359057
https://wiki.vuze.com/w/Configuration_directory

[anon]

I just tried the unmodded BiglyBT and it works. In the modded client it just goes to inactive mode and will not start.
Do you have any ideas about how to debug this?

The console logging feature should definitely help, especially at the highest log level. Note that it needs to be enabled both for the base client (as per cloud99's post above) and the Extreme Mod features (setting #4 in http://www.sb-innovation.de/showthread.php?t=13781).

[Cr@zYiNsEiN]

Hi there @motalemb,

Is there a guide to set this up to mimic/be undetected?

No. There isn't one available to date. (According to my knowledge). I plan on making one though soon to help other members who have similar questions like yours. However, I need time to juggle between work and side-project time and again without making errors unintentionally.

I know there's the guide explaining all the settings, but am I missing anything if I follow the instructions in this post and then follow the instructions for spoofing a client?

You'd be doing yourself a favor as the more knowledge you have about these things, the more the chances are you won't log in to your account on a particular day and find yourself banned.

Just want to make sure I'm not missing anything

Yes, you are. Firstly search for the tracker you want to cheat on here in the below-mentioned section.

http://www.sb-innovation.de/forumdisplay.php?229-Tracker-Cheating-Experiences

Once you find that tracker, you want to cheat on. I would suggest you read the latest posts and see what other members have to say about their experience with the tools and mods they've used. Follow them, and you will be safe. If you don't want to manually go through all the pages to find the tracker in question, utilize the SB-Innovation search functionality to find the tracker. If you still don't see it, you are free to make your own thread asking other members for their take on the tracker. Before you make a thread for the tracker in question, I suggest you read the Tracker Cheating Experiences Section Rules.

http://www.sb-innovation.de/showthread.php?17764-Tracker-Cheating-Experiences-Section-Rules

Moving on.
1) Anyway, that's not going to be enough as you will also need to use some common sense (I don't mean to be rude, but there's no other way to word this) and not faking questionable uploads and speeds. You don't want to show up on the trackers' list of members in the top list of stats for uploads, seeding the most torrents, or any other factor that shines a light on your account.
2) You want to be as undetectable as possible, which means don't unnecessarily make posts on the tracker's forum or help section. Search for forum or help section for threads or posts that can answer your questions without making threads or posts. Once there's visibility on your account, any staff member can quickly check your torrent client interactions with a tracker and compare it with other members who are seeding or leeching the same torrent. You know what comes next. If you don't, they will notice the announced' irregularities and see that you are cheating or faking your stats.
3) Stick to faking on newly released torrents with a high number of leechers. Also, manually check to see whether the torrent you plan to cheat on has actual leechers and not partial seeders. You can do this by just seeing the release date or upload of the torrent on the tracker. Torrents that are old or have been released for quite some time and still have leechers on them are not real leechers but, in fact, partial seeders. Members of the trackers who don't want to download the entire torrent for reasons of their own.
4) Stick to one torrent client and fake tools or mod. For example, if you use qBittorrent to download torrent(s) and since you posted on the BiglyBT thread, use BiglyBT to cheat faking uploads, downloads, seeding time, or anything similar. Stick to the same torrent client and faking tool or mod. Don't keep changing them; it will report different torrent announces to the trackers, and this will force the staff members to scrutinize your account and the activity that you (not you but your torrent client) have reported.

Anyway, I hope this has covered all the basics. If you have a specific question to a mod, tool, or tracker, please make sure you post it in the right thread to increase your chance of other members seeing your post and then providing you valuable insights into your queries.

Good day.

Hi there GhostCode,

hello, may I ask for these two files.
thanks in advance
qBitTorrent 3.2.3
uTorrent 2.2.1 Build 25154

I've already made both these clients emulation files as of 06:31 (time displayed on SB-Innovation). I had it bookmarked and kept it to work on for when I'm free. The only things I am waiting on are: -
1) LTEP Identification strings need to be checked and made correct in the emulations. (I'm waiting for @anon to reply to my post in regards to it. Also, don't harass him to speed up the process as he must be having other work priorities that come first).
2) Testing out the client files. I plan to test out my emulations files with specific trackers before making them public from now on. This so that other members using the client files don't get banned for using incorrect emulations.
So these are what is preventing me from posting them as of writing this post. Suppose you believe yourself to still want these emulation files with slightly incorrect information in them before they are made right. Reach out to me via Personal Message, and I will send them to you. The only thing I would say about them regarding it is that you don't make them public.
Note: My suggestion would be to wait for a couple of days to adequately check, evaluate, and test the emulation file(s) before I post them on SB-Innovation. Then others can scrutinize them and report back the problems before they are safe to use.
~cloud99

[motalemb]

Thanks cloud99. I still can't get the mod to work. Where are the mod options located? My Tools->Options looks normal, so I have no idea if the mod correctly installed or not (the mod files are in the same folder as BiglyBT.jar and I have the two lines at the bottom of vmoptions)

[anon]

Where are the mod options located? My Tools->Options looks normal

If you don't see Extreme Mod settings there, then the mod is not installed correctly. Another way to find out is to check the status bar: there should be a blue button labeled "SB-I MOD" with version number "2.x.0.0_DDJ" next to it.