Thread: Vuze Extreme Mod by SB-Innovation 5.6.0.1 B05 Beta

SB-Innovation Presents

Vuze Extreme Mod by SB-Innovation 5.6.0.1 B05 Beta



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

>>>>>> DigitalDJ & ghostfucker <<<<<<


╔═══════════════════════════╗
Credits:
╚═══════════════════════════╝

>>>>>> Butcho <<<<<<
>>>>>> Rebound <<<<<<
>>>>>> hitman <<<<<<
>>>>>> Manas <<<<<<
>>>>>> eudora <<<<<<
>>>>>> ghostfucker <<<<<<
>>>>>> anon <<<<<<
>>>>>> Instab <<<<<<

╔═══════════════════════════╗
Supplied by:
╚═══════════════════════════╝

>>>>>> SB-Innovation <<<<<<

╔═══════════════════════════╗
Original Mod by:
╚═══════════════════════════╝

>>>>>> Shu <<<<<<


Change Log:

+ Perfect Spoof 2
+ uTorrent ID Generator
+ Modifiable Client Files
+ Ghostleech
+ LTEP Fixes
+ Multiple peerlist entries fixed
+ More No Report Options
+ Perfect Spoof 1.0 by ghostfucker
+ (Fake Upload) Stop faking when swarm speed is zero
+ Upload Kicker
+ Ratio Tool
+ Fixed bug preventing Vuze plugin downloads
+ Synced with latest Shu Mod
+ (Upload Multiplier) Show as seeder
+ (SBI-Hack Torrentview) Scrollbars added
+ Use Swarm Peers fixed
+ Updated core to Vuze 5.6.0.1_B05

Vuze Change Log:
Vuze Change Log

Installation:
1. Download and install Vuze (if this is a Beta/CVS update, download the latest NON BETA release) (Vuze : Java BitTorrent Client - Download).
2. BACK UP YOUR TORRENT LIST! IT IS LIKELY YOU WILL LOSE IT!
3. Optional: If you want to make a backup of your old Vuze version. Go to the install directory and rename Azureus2.jar to Azureus2.jar.bak
4. Extract the files using WinRAR (WinRAR archiver, a powerful tool to process RAR and ZIP files) or equivalent to %PROGRAMFILES%\Vuze (C:\Program Files\Vuze) and overwrite ALL files.
5. Run Vuze and Enjoy!
NOTE: For other operating systems simply replace the Azureus2.jar. For 64-bit, portable, and Vuze Plus support read the README in the appropriate package.

Troubleshooting:
Before posting problems please make sure:
1. You have updated Java Runtime Environment (JRE) to version 6 (Java SE Downloads).
2. You have removed the Vuze folder in %PROGRAMFILES% (C:\Program Files\Vuze).
3. You have removed the Vuze folder in %APPDATA% (The folder may be hidden).
C:\Documents and Settings\<username>\Application Data\Vuze for XP
C:\Users\<username>\AppData\Roaming\Vuze for Vista
4. Reinstalled Vuze using the package from Vuze : Java BitTorrent Client - Download
5. Re-applied the hack from the downloaded archives.

Warning: Performing steps 2 and 3 will wipe your torrent list and Vuze settings.

Enjoy!

Ignore the portable zips if you don't need portable.
There are no best settings, it depends on the situation and torrent. Slow and steady are usually a good way to go.

Checking the CID is not necessary because, the clientfile will generate its own/new/unique Peerid etc. on startup?!

Yes

Checking the CID(without checking read from file) would only allow me to make Vuze look like uT if I had both programs open at the same time(or wanted to make Vuze look like I had never changed the Torrent Program and/or restarted uT) because I can enter an ID that I got from uT with the help of the a memory scanner(RM+)?

it's dangerous, uTorrent peerid is global so using the same peerid is legal but what aboyt the key value ? it's global also but in vem you can't modify it.
Why you will need uT when vem will appear to tracker and swarm just as a very uTorrent client.

- Hypothetical: would using my client file result in the detection of my spoof? Would something seem out of place for the tracker?

<field>Connection: Close</field>
I think you have modified another client file. your version announce has no Connection : Close in the headers.
Also, <param>&amp;ipv6={ip}</param>

<param>...</param> <!-- The query, Required, Available fixed parameters: [info_hash], [peer_id], [port],
<param>...</param> [azudp], [uploaded], [downloaded], [left], [corrupt], [numwant], [no_peer_id], [compact], [key], [azver], [ip]
Available volatile parameters: {supportcrypto}, {requirecrypto}, {cryptoport}, {event}

there is no {ip} in vem , Read the PS2 docs
So, yes it was detectable.