[Tutorial about the BiglyBT Extreme Mod] All settings explained

[dickbutt123]

It seems VEM only fakes in relation to the % you've downloaded (e.g if i download half the contents of the torrent, it only fakes up until the ratio but applies it to 50% of the total i downloaded). So if a torrent was 18gb, i downloaded half of it, which is 9gb, i'll only fake up 4.5gb (my ratio is set around 1 - 1.15). Isn't this strange? I reckon it's because i downloaded 50% of the torrent, and VEM applied the 50% to the amount i downloaded, so it came out as 4.5gb. Anyone got any solutions on how to get the VEM to fake up the ratio applied to the amount i've downloaded?

[anon]

So if a torrent was 18gb, i downloaded half of it, which is 9gb, i'll only fake up 4.5gb (my ratio is set around 1 - 1.15). Isn't this strange?

Can you grace us with a screenshot of the settings that torrent is using?

[dickbutt123]

I haven't touched any settings in the Extreme Mod General Settings. Let me know if you need anything else

[anon]

Any chances you've already tried turning intelligent mode and/or "stop faking when the swarm speed is zero" off?

[dickbutt123]

Any chances you've already tried turning intelligent mode and/or "stop faking when the swarm speed is zero" off?

No, do you want me to try? Actually, i'll go for it, a little experimentation would do good for others

Edit: I checked the torrent before changing any settings and it faked about a gig extra. It does is slowly, and in bursts after long periods of time. I'll experiment with intelligent mode now.

Edit 2: Yep, it was stop speed when swarm speed is zero. Is it recommended to turn off, if i make sure i don't fake on dead torrents?

[anon]

Edit 2: Yep, it was stop speed when swarm speed is zero. Is it recommended to turn off, if i make sure i don't fake on dead torrents?

In that case, definitely.

[Lucius]

I thought Vuze used a different peer_id for each torrent? Or are there other values that have to be the same?

There's another way of getting data from Vuze, if necessary.

Yes but Are mRatio and Vuze generate the same Peer_id for the same torrent ? After some researches and sniffing i figured out that the answer is no :( .

I opened the same torrent in vuze and mRatio then i sniffed the announce and it was different from the mRatio emulation info in advanced menu .

oh crap youre right. didnt think anything of it

@tattah, youre safe as long as you dont start the same torrent in vuze and mr...

Yes ,After i tried to sniff it i found out that it's safe to use vuze (spoofed) with mRatio as long as I'm not using the same torrent.

But guys my problem now is the port number .. I have to use the same port number in vem and mR to make the perfect emulation but Is this won't make any conflicts ? I tried it and I saw red icon beside port number in mRatio so i think it can make problems .. AM i right or what ?

and again Thank you so much, I know that my questions is a noob ones :) .

[dickbutt123]

Has anyone experienced their ratio not being fully met? Normally, i can cheat up to and in between the ratios i set in the Speed Mode++ settings, but some times i only seed up to 0.7 ratio instead of my normal 1.3 or so. Why is that? I have intelligent mode on but should that affect it? This happens even though i leave the torrent seeding after it's downloaded, waiting for the announce, then checking the snatchlist but still it only goes well below my limits. Any one got suggestions on how to fix this? Here are my settings (i change the ratios every day)

[dickbutt123]

Update - i've found this is only a problem with TL, as any other trackers i tested, always gave me an accurate reading. I assume this problem arises because of TL's (in)ability to see how much was uploaded with the announces, as after the 1st announce, it's sometimes a rare problem to have the uploaded amount stay the same in the snatchlist, even if i update tracker or wait hours.

[dickbutt123]

I can't seem to edit my posts so i'll post another update. I've found this problem is still occurring, and it seems to be only on TL. Does anyone have any clues on what causes this inability to capture the fully amount of fake upload? Is it a Vuze problem? Would announcing before removing torrents help? (Even though some torrents have over 30 announces and yet, TL only sees half of what was fake uploaded). Any help would be greatly appreciated.

Edit: Now the button appeared for me, it didn't before! Mod, feel free to merge these into 1

[Dark Knight]

point 13. Safe fake upload.
Can you tell me practically what it does , i mean any example with numbers?
& what is the recommended value, mine is 1.7 .. but i really don't know what to consider while choosing this value..?

& also ...Ghostleech...what are its benefits & on what kind of trackers i can use it..?

[anon]

point 13. Safe fake upload.
Can you tell me practically what it does , i mean any example with numbers?

Let's say I'm faking on a torrent that's 200MB in total. I use speed mode++ to set a speed between 400 and 500kB/s, but I fumble when typing the speed, and set them between 400 and 5000 without noticing. It'd be very easy for my fake upload traffic to reach many times the torrent's size before I realize my mistake. But safe fake upload makes sure I never report uploading more than 'x' times the total size, in your case, 1.7.

& also ...Ghostleech...what are its benefits & on what kind of trackers i can use it..?

Do a little searching

[dickbutt123]

Let's say I'm faking on a torrent that's 200MB in total. I use speed mode++ to set a speed between 400 and 500kB/s, but I fumble when typing the speed, and set them between 400 and 5000 without noticing. It'd be very easy for my fake upload traffic to reach many times the torrent's size before I realize my mistake. But safe fake upload makes sure I never report uploading more than 'x' times the total size, in your case, 1.7.



Do a little searching

However, i've found that using a safe fake upload too close to your fake upload ranges causes most if not all of your ratios to become like "1.7", if you don't remove them fast enough.

[ljhonn95]

Is enabling ""doesn't send the "completed" flag when the torrent is finished"" while you are in NO REPORTING safe on all trackers?

[anon]

Is enabling ""doesn't send the "completed" flag when the torrent is finished"" while you are in NO REPORTING safe on all trackers?

It's redundant. You'll never send the completed flag if you use no report (except maybe if 15d is ticked, I didn't try that but it's not recommended anyway).