I think for $200 checker should be without any errors also is this with DBC?
Scam report against | NodeCode | 595139 | 200$
#52
Posted 06 January 2017 - 11:00 PM
I highly doubt they are judging your code, I think they are judging the fact that as it was released early it's not working as everyone would expect so they want a refund. Even if it's a beta. It's up to you when you stop calling it a beta. You could keep it a beta forever and keep saying errors are normal, forever.
Everyone that bought the product has been thoroughly explained the terms and services, they all confirmed they were okay with helping me fix the bugs and that they did, in fact, know it was a beta and that errors WOULD occur.
#53
Posted 06 January 2017 - 11:02 PM
Are you gonna waste your time arguing now or you are going to start coding instead?
Actually, I've been coding for 4 hours now. Thanks for letting me know
EDIT: To everyone. You can all complain based on what Ivar said but nonetheless, we have the only checker that is proxyless and we didn't pull and iDev and scam everyone once our product got some criticism.
Edited by Coefficient, 06 January 2017 - 11:04 PM.
#54
Posted 06 January 2017 - 11:02 PM
Everyone that bought the product has been thoroughly explained the terms and services, they all confirmed they were okay with helping me fix the bugs and that they did, in fact, know it was a beta and that errors WOULD occur.
So Ivarovich must provide proof he didn't know this would happen, and you must provide proof you told him that it was a beta and he was part of the error checking team.
Normally, when you are uncertain your tool works properly, you let a few beta testers use it while you check for errors, and then release it to public after everything was tested. Why didn't you do that?
MY ONLY BITCOIN ADDRESS IS IN MY PROFILE. IF I SEND A DIFFERENT ONE IT'S NOT ME.
I HAVE 2 DISCORD PROFILES:
"@lucas.1337" DISCORD ID IS "474341590891102219"
"@n.to" DISCORD ID IS "1056693864322318406"
MY TELEGRAM: t.me/LucasNulledTo
https://www.nulled.t...ypto-addresses/
^MY ONLY CRYPTO ADDRESSES^
ALWAYS ASK FOR A PM, NEVER SEND ME MONEY WITHOUT RECEIVING A MESSAGE FROM ME ON NULLED. I WILL NEVER REFUSE TO PM YOU.
READ THIS TO AVOID BEING SCAMMED:
https://www.nulled.to/topic/543296-beware-new-impersonation-scam-must-read/
#56
Posted 06 January 2017 - 11:06 PM
So Ivarovich must provide proof he didn't know this would happen, and you must provide proof you told him that it was a beta and he was part of the error checking team.
Normally, when you are uncertain your tool works properly, you let a few beta testers use it while you check for errors, and then release it to public after everything was tested. Why didn't you do that?
They are currently only 10 customers, all are beta testers and agreed to help us fix bugs.
#57
Posted 06 January 2017 - 11:54 PM
I can confirm that the checker has been fixed and is working perfectly fine on proxyless, I haven’t ran in any errors so far.
Note: Failed accounts = incorrect pass
Thank you @Cactopus, mods are free to pm or add me on skype: amazon.buy4you for any other proofs
account no longer active
#60
Posted 07 January 2017 - 12:11 AM
ayy lmao devs are arguing with a user that the tool is working, instead of trying to help the user fix the problem xDD
Actually, we did fix the problem. We are just demonstrating that our tool works fine now, yet, he refuses to discuss.
Users browsing this thread: and 3 guests