search

Shiawaseu / fluxus-key-bypasser

Bypasser for Fluxus' key system
31 stars 35 forks source link

Not working #5

Closed LordUnadmin closed 1 year ago

LordUnadmin commented 1 year ago

Tested the V2 to see if it really works, the key didn't work and got temp banned.

Shiawaseu commented 1 year ago

Just tested, looks like it is patched for now, I'll work on a fix.

By the way you do get the key, you just have to wait until the temp ban is over.

takoda121 commented 1 year ago

As someone who is expirienced with browser automation and most "key sites" like KRNL I assume that Fluxus added a check if IP/HWID did the HCaptcha and this bypass doesnt do it. I honestly think that everyone should make their bypass or just pay the 20 for SW or SX. I also used bypasses that I made but it was not worth it. Just pay 20 USD.

takoda121 commented 1 year ago

Checked the V2 version using Py 3.10.11 and Chrome 115.0.5790.99 everything works.

Shiawaseu commented 1 year ago

As someone who is expirienced with browser automation and most "key sites" like KRNL I assume that Fluxus added a check if IP/HWID did the HCaptcha and this bypass doesnt do it. I honestly think that everyone should make their bypass or just pay the 20 for SW or SX. I also used bypasses that I made but it was not worth it. Just pay 20 USD.

Let me answer this one by one.

Fluxus never checked their HCaptcha, if they did now I’ll have to use an AI Captcha solver (probably NoCaptcha)

Second, I’ve confirmed the “ban” is via IP addresses, you could get around the ban with a vpn/proxy (This might be an optional feature soon)

Third, I’ve originally made this bypass for myself, then released it to the public. Maybe it is my fault. Also don’t forget the snitches that roam around telling the devs.

Fourth, most obvious one is yes. Buy an exploit. I only made this after Byfron. Otherwise I would’ve stuck to using SynX.

In the end, hopefully I’ll try my best to keep this working. Until SW or SX update, then I will discontinue it.

takoda121 commented 1 year ago

As someone who is expirienced with browser automation and most "key sites" like KRNL I assume that Fluxus added a check if IP/HWID did the HCaptcha and this bypass doesnt do it. I honestly think that everyone should make their bypass or just pay the 20 for SW or SX. I also used bypasses that I made but it was not worth it. Just pay 20 USD.

Let me answer this one by one.

Fluxus never checked their HCaptcha, if they did now I’ll have to use an AI Captcha solver (probably NoCaptcha)

Second, I’ve confirmed the “ban” is via IP addresses, you could get around the ban with a vpn/proxy (This might be an optional feature soon)

Third, I’ve originally made this bypass for myself, then released it to the public. Maybe it is my fault. Also don’t forget the snitches that roam around telling the devs.

Fourth, most obvious one is yes. Buy an exploit. I only made this after Byfron. Otherwise I would’ve stuck to using SynX.

In the end, hopefully I’ll try my best to keep this working. Until SW or SX update, then I will discontinue it.

Well I made my own exploit/dll for the UWP version but when SW v3 drops I will use that.

Shiawaseu commented 1 year ago

Quick update V1 works just fine, the temp-ban issue is for V2 only.

takoda121 commented 1 year ago

Quick update V1 works just fine, the temp-ban issue is for V2 only.

After many tries I didnt notice any temp ban on the V2. Idk about V1, Im lazy to install node (new pc problems)

Shiawaseu commented 1 year ago

This issue was already solved with commit 2489380f15d4af1ec53c3b6afa3c178f71f7acf8

I simply forgot to test it hence why @takoda121 didn't run into any issues.