(13 June, 2021 - 12:28 AM)sh_0ck Wrote: Show More(12 June, 2021 - 07:22 PM)Serend Wrote: Show More@NotAleecher69420
Stated the fixes he wanted done, I have completed every request he has asked of.
I fixed the kill counts, the username capture, the gun purchases fix, etc etc.
I have released 6 updates since my config has come out and not a single person has had an issue but you.
With that being said CPM comes from two different factors, the request you are targeting and the proxies you are using.
Everyone else on the market is using the same device ID, ACT SSO Cookie, etc for their form data on the same exact login request.
Worked fine a week ago, and that has never changed but cpm is getting shitty after 20 min of checking. Only thing that this can be caused by is the domain rejecting your proxies or their site is just garbage and is timing out login requests or giving errors. When that happens it recycles your proxies.
" I also accepted a fully working config which you clearly can't provide ", config is working perfectly fine for others. So, that seems invalid.
"Everyone else on the market is using the same device ID, ACT SSO Cookie, etc for their form data on the same exact login request."
Unless you're skidding configs no one else is going to be using the same device id, cookie and others. idk what you're doing wrong but it honestly seems you dont know much about making configs especially as he said hes tested the proxies with other peoples checkers/configs and they get much more cpm so theres obviously something wrong with your config. i dont know anyone whos config is getting shit cpm after 20 mins
First off, device ID is random generated up as is the cookies. Coded mine myself and it had it been out longer than most on this forum. One of the quickest after the Akamai protected APIs for inventory, and camos unlocked.
Second, who the fuck asked you @sh_0ck We all know your shit is skidded.
Never stated that all cookies and device ids are the same. I’m saying that everyone uses the same login request url/api.