BitComet 1.16 SBI Leecher Pack

SB-Innovation Presents

>>>>>> BitComet 1.16 SBI Leecher Pack <<<<<<

╔═══════════════════════════╗
Coded by:
╚═══════════════════════════╝

>>>>>> BitComet Development Group <<<<<<

╔═══════════════════════════╗
Modded by:
╚═══════════════════════════╝

>>>>>> Butcho <<<<<<

╔═══════════════════════════╗
Changelog / Features:
╚═══════════════════════════╝

Features:

-upated to bitcomet 1.16
-built many different cheater versions
-included eMule plugin
-removed advertising
-cleaned code from some auto connected HTTP sites
-changed some parts to show SB-Innovation



Leecher Mods:

-Original
-Fakeupload_I
-Fakeupload_II
-Multi_11x
-Multi_111x

-NoComplete
-NoComplete_Fakeupload_I
-NoComplete_Fakeupload_II
-NoComplete_Multi_11x
-NoComplete_Multi_111x

-NoComplete_ReportSeeder
-NoComplete_ReportSeeder_Fakeupload_I
-NoComplete_ReportSeeder_Fakeupload_II
-NoComplete_ReportSeeder_Multi_11x
-NoComplete_ReportSeeder_Multi_111x

-NoComplete_NoReport-Seeder
-DHT-Patch
-Stealth


Erklärung:

No Complete
-Es wird kein Fertiggestellt Status gesendet dadurch entsteht kein Snatchlist Eintrag.

NoReport-Seeder
-Es wird weder euer Download und Upload auf dem Tracker gezählt.
-Ihr werdet als Seeder angezeigt
-Es wird kein Fertiggestellt Status gesendet dadurch entsteht kein Snatchlist Eintrag.

Report-Seeder
-Ihr werdet sofort als Seeder angezeigt euer Download wird auf dem Tracker nicht gezählt.
-Es wird kein Fertiggestellt Status gesendet dadurch entsteht kein Snatchlist Eintrag.

Fakeupload I
-Der Client sendet einen Fakeupload zwischen 10 bis 45 kb/s an den Tracker
(Wenn der Realupload auf 10 begrenzt ist)

Fakeupload II
-Der Client sendet einen Fakeupload zwischen 10 bis 95 kb/s an den Tracker
(Wenn der Realupload auf 10 begrenzt ist)

DHT-Patch
-Ignoriert die "Private Flag" und lässt euch DHT und PEX für private Torrents aktivieren.
(Verwendet diese Option nur wenn ihr wisst was ihr tut)

Multi 11x
-Der reale Upload wird mit 11 multipliziert.
-Es ist empfohlen in auf ≤9KB/s zu beschränken.

Multi 111x
-Der reale Upload wird mit 111 multipliziert.
-Es ist empfohlen in auf ≤2KB/s zu beschränken.

Stealth
-Euer Download und Upload auf dem Tracker wird nicht gezählt.
-Es werden keine aktiven Torrents in eurem Profil angezeigt.
-Funktioniert leider nicht auf allen Seiten.


Explanation:

NoComplete
-You don't send the completed flag to the tracker.
-There is no snatchlist entry.

NoReport-Seeder:
-Your upload and download aren't reported to the tracker.
-You are shown as a seeder.

ReportSeeder:
-You are shown directly as a seeder.
-Your download isn't reported to the tracker.

Fakeupload I
-The client sends a fake upload between 10 and 45 kB/s to the tracker
(If you limit your real upload to 10kB/s)

Fakeupload II
-The client sends a fake upload between 10 and 95 kB/s to the tracker
(If you limit your real upload to 10kB/s)

DHT-Patch
-Ignores the private flag, letting you enable DHT and PEX for private torrents.
(Only use it if you know what you're doing)

Multi 11x
-Your real upload is multiplied by 11.
-I recommend you limit it to ≤9kB/s.

Multi 111x
-Your real upload is multiplied by 111.
-I recommend you limit it to ≤2kB/s.

Stealth
-Your upload and download aren't reported to the tracker.
-You are also not shown in the peerlist.
-Unfortunately it doesn't work on all trackers.


╔═══════════════════════════╗
Password:
╚═══════════════════════════╝

Code: bc116

Thank!.Oh and i am having a little problem with this new version.It uploads with speeds up to 120KB.LOL.My max speed is 50-60KB.Not a problem but the upload doesn't go on my torrents.In the blue window it shows 120KB and when i look at my torrent it says 0KB upload.So wtf?

Quote:

---

In the blue window it shows 120KB and when i look at my torrent it says 0KB upload.So wtf?

---

Have you disabled auto-updating and such? BitComet has a feature to look for updates for your installed programs, this could be causing the extra traffic.

Nope.But i always had it running, from the first time i started using it.But i will disable it just to be sure.

Hmm that's strange i'll check it this weekend.
Which version you've tried?

Last one.1.16
But the orginal one was giving me problems.Not the hacked one.I treyd it again and didn't had that problem anymore so i'm confused.

Please tell me if you got the same problem again.
Normal all should work like in every sbi leecher pack but perhaps the bitcomet developers changed something in their code what i didn't noticed until now...

No more problem.Oh and the problem was at the unhacked version.I'll keep you posted if something new comes up.

I saw this :http://img121.imageshack.us/img121/4186/bitcomet.png

Does this mean i can report to the tracker like a different client?

---------- Post added at 16:33 ---------- Previous post was at 15:46 ----------

Another problem:I am using the fake report II version for the first time and i did 10% of the torrent and still didn't remorted some upload, just download.Do i have to limit it to 10kb or is it enough to limit the global upload speed to 10kb?And if it's this way than why doesn't the fake upload starts?

Quote:

---

Originally Posted by Mihai91

Does this mean i can report to the tracker like a different client?

---

No, it means you can change the User-Agent BitComet will send to the tracker. It's possible to bypass some (really poorly-coded) client blacklists if you set it to uTorrent/1850(17414), for example, but I definitely wouldn't recommend this on high-level trackers since the rest of the announce is left untouched.

Quote:

---

Another problem:I am using the fake report II version for the first time and i did 10% of the torrent and still didn't remorted some upload, just download.Do i have to limit it to 10kb or is it enough to limit the global upload speed to 10kb?And if it's this way than why doesn't the fake upload starts?

---

The individual speed limit - so that the torrent uploads at full 10kB/s and FakeUpload can act. I'll have a look at how Butcho coded the mod just in case, but I doubt he got it wrong.

Edit: the mod is coded correctly.

I have enough time testing the bitcomet of this page, but I had not realized that putting the upload speed of 10 really does not seemed so strange for me to navigate or use a program like listening to music available through the Internet had problems. And so I write because I have been measuring the network meter gadget for Windows 7 and the rates of rise and fall and rise especially not match easily, since the rise of 10 reflects me 32 that is the maximum speed allowed me ADSL line.

Sorry, but I don't understand your post - your network is slow even though you limited your upload speed to 10kB/s on a connection whose maximum speed is 32kB/s?

me explain better I use the option Fakeupload II it is assumed that if I limit the global rise of bitcomet to 10 or so should climbing about 10 but not, or at least that's what I reflected in the networkmeter ( "gadget windows 7"), then mark me about 28 to 32 KB / s which is the gross income increases, which gives me my adsl provider and if you have connected me back navigation is quite slow.

So upload goes higher than 10kB/s even though you limited it to that..?

If so, you should disable all the features that cause extra overhead - such as update checking, DHT, UPnP, long-time seeding...

If the issue persists, ask in the BitComet forums.

When should a pack for the new version apear?

Soon :wink: Since modding BitComet takes more effort than uT I want to make sure a new version won't come up right after I finish with the current one. Not to mention BC leecher packs are ~70MB long and my upload speed is 20kB/s.

If you are still making them then just make the usefull ones.I recomend these ones:
Fakeupload I,II, Multi 11x,111x
And is it posible to make a Fakeupload I without having to limit your upload to 10KB?

Quote:

---

Originally Posted by Mihai

And is it posible to make a Fakeupload I without having to limit your upload to 10KB?

---

I don't think so. :frown:

Quote:

---

Originally Posted by anon

I don't think so. :frown:

---

Ok.No problem.Oh and a little question.Tehnically when i don't limit my upload to 10KB it doesn't cheat right?And if i limit it again it will.
And does it start cheating only when i start seeding?"cause i didn't stop to look or test this.

You always cheat regardless of conditions when using the FakeUpload mod. And with an unlimited upload speed you could end up reporting huge rates!

I am confused.You mean even if i limit it or not i will always cheat?:confused2:

Quote:

---

Originally Posted by Mihai

if i limit it or not i will always cheat?:confused2:

---

Correct. The mod can't tell when you're limiting your upload or not and disable FakeUp accordingly.

So you don't need to make a Fakeupload that doesn't need a limit to 10KB because it will automatically cheat.

Quote:

---

Originally Posted by Mihai

So you don't need to make a Fakeupload that doesn't need a limit to 10KB

---

I directly can't - it's not possible with hex-mods...

Ohh.Now i understand.SO you are not obligated to limit your upload if you don't want to.And with my 50Kb+max 45KB=max 95KB speed.Not bad and not exagerated for the trackers i am curently using.Thanks for clearing this out!

Quote:

---

Originally Posted by Mihai

Ohh.Now i understand.SO you are not obligated to limit your upload if you don't want to.

---

You're not, but FakeUp will still come into effect, and you'll end up reporting higher speeds!

I see.Well i think for the new mods you should write not the fact that the mod starts cheating

Quote:

---

If you limit your real upload to 10kB/s

---

You should write that it is recomended to limit the upload so you will not report too high speeds.

You're totally right! I copied the text from Butcho's posts so I didn't notice that!

Quote:

---

Originally Posted by Mihai

No more problem.Oh and the problem was at the unhacked version.I'll keep you posted if something new comes up.

I saw this :image

Does this mean i can report to the tracker like a different client?[COLOR="Silver"]

---

Can i at least report as bitcomet 0.70?If yes what's the exact vesion i should write there?:confused:

Quote:

---

Originally Posted by Mihai

Can i at least report as bitcomet 0.70?

---

I just had to install v0.70 to check its User-Agent. I noticed its announce structure is also different. But if you want to take the risk:

Quote:

---

BitTorrent/3.4.2

---

(The UI is also much cleaner than that of newer versions!)

Quote:

---

Originally Posted by anon

I just had to install v0.70 to check its User-Agent. I noticed its announce structure is also different. But if you want to take the risk:


(The UI is also much cleaner than that of newer versions!)

---

I found the useragent too but when i saw bittorrent 3.4.2 i thought i messed something up.

---------- Post added at 18:34 ---------- Previous post was at 18:32 ----------

Didn't worked.

Quote:

---

Originally Posted by Mihai

Didn't worked.

---

I tried some things to make 1.18 look like 0.70, but didn't succeed. :frown:

I guess you could ultimately try setting the User-Agent to BitComet/0.70.0.0 even though 0.70 doesn't use that, but if the tracker is blacklisting clients via peer_id there's nothing you can do. Other than maybe asking them to whitelist the latest version (if they come up with the DHT shit, that was fixed on v0.61).

Quote:

---

Originally Posted by anon

I tried some things to make 1.18 look like 0.70, but didn't succeed. :frown:

I guess you could ultimately try setting the User-Agent to BitComet/0.70.0.0 even though 0.70 doesn't use that, but if the tracker is blacklisting clients via peer_id there's nothing you can do. Other than maybe asking them to whitelist the latest version (if they come up with the DHT shit, that was fixed on v0.61).

---

Tryed that too.Not working.

What's about 1.18? :frown:

Sorry for the waiting time.
I worked on my next emule version the last weeks.
I will create the bc 1.18 pack the next days if i have some free time...

Actually i spoke with some admins on the bitcomet forum and they found the bug i was talking about in this thread, with the big upload speed on no torrents.They said they will fix it at version 1.19 so you should just wait a little more.

Then i will wait until they release v1.19.