![]() |
|
Bug Report and Suggestion - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Hack Forums Official Information (https://hackforums.net/forumdisplay.php?fid=1) +--- Forum: Site News (https://hackforums.net/forumdisplay.php?fid=2) +---- Forum: Suggestions and Ideas (https://hackforums.net/forumdisplay.php?fid=134) +---- Thread: Bug Report and Suggestion (/showthread.php?tid=6001238) |
Bug Report and Suggestion - DNA - Aug 22, 2019 Suggestion- MyAwards.php needs updating Bug- Firefox Android: Seems to be an overly large amount of refresh requirements on Scratch Cards. Out of 10 Cards, roughly 6 of those attempts threw a refresh screen in my face where I am able to predict the outcome Feel free to delete this thread as it may bring attention to the issue Example: ![]() Either resending or cancelling does not change the results (must be predetermined), ergo I can resell scratchcards that I know will fail using UID. Temporary workaround: Disable Gifting of Scratchers Solution: If the refresh page is forced on the user, disable the gifting on that card RE: Bug Report and Suggestion - Omniscient - Aug 22, 2019 You can do this before even making one scratched box? RE: Bug Report and Suggestion - Adolf Hipster - Aug 22, 2019 I am thinking this is more of a mobile error as I had very few on PC. RE: Bug Report and Suggestion - DNA - Aug 22, 2019 (Aug 22, 2019 01:13 PM)Omniscient Wrote: You can do this before even making one scratched box? I believe the refresh issue only occurs after one has been partially scratched but if you're quick enough and scratch three before the refresh screen, you can see the result beforehand and just resell the cards that will fail. Example if I buy 1k card, I notice it's failed and refresh screen occurs, I cancel (or resend), and then sell that card for 800 bytes. The buyer gets a useless card and I get 80% back (Aug 22, 2019 01:18 PM)Adolf Hipster Wrote: I am thinking this is more of a mobile error as I had very few on PC. That's what I believe as well RE: Bug Report and Suggestion - Adolf Hipster - Aug 22, 2019 (Aug 22, 2019 01:18 PM)Jelly Wrote: I believe the refresh issue only occurs after one has been partially scratched but if you're quick enough and scratch three before the refresh screen, you can see the result beforehand and just resell the cards that will fail. Ah that is a good point since you can transfer the card. RE: Bug Report and Suggestion - DNA - Aug 22, 2019 (Aug 22, 2019 01:22 PM)Adolf Hipster Wrote: Ah that is a good point since you can transfer the card. This is why I reported this as soon as I noticed, could be heavily exploited RE: Bug Report and Suggestion - Omniscient - Aug 22, 2019 Quote:I believe the refresh issue only occurs after one has been partially scratched but if you're quick enough and scratch three before the refresh screen, you can see the result beforehand and just resell the cards that will fail. Once one is scratched it should not allow you to sell the card. I'd need proof of concept that you're able to know a cards results and still be able to sell it. RE: Bug Report and Suggestion - Adolf Hipster - Aug 22, 2019 (Aug 22, 2019 03:21 PM)Omniscient Wrote: Once one is scratched it should not allow you to sell the card. I'd need proof of concept that you're able to know a cards results and still be able to sell it. I see. This is great if in fact its the case. RE: Bug Report and Suggestion - DNA - Aug 22, 2019 (Aug 22, 2019 03:21 PM)Omniscient Wrote: Once one is scratched it should not allow you to sell the card. I'd need proof of concept that you're able to know a cards results and still be able to sell it. Sure thing. I'll purchase some bytes later and try record some proof of concept. Because as far as I know, it's not scratched when you press cancel as it's still in your scratch cards and the transferring option was still there. The image in the OP was that of a semi-revealed card. Previously semi-revealed card showed the same result on the revealed card afterwards. RE: Bug Report and Suggestion - Elitas - Aug 23, 2019 (Aug 22, 2019 03:21 PM)Omniscient Wrote: Once one is scratched it should not allow you to sell the card. I'd need proof of concept that you're able to know a cards results and still be able to sell it. Yeah what he's describing sounds like the results are being stored client-side and then the user sends the 'result' to HF after it has been scratched (which if it's the case would likely allow you to modify the end result and win every time). I doubt that's how it is designed so it doesn't make sense to me either. OP you sure the cards aren't expiring after you scratch one? RE: Bug Report and Suggestion - DNA - Aug 23, 2019 (Aug 23, 2019 05:45 AM)Elitas Wrote: Yeah what he's describing sounds like the results are being stored client-side and then the user sends the 'result' to HF after it has been scratched (which if it's the case would likely allow you to modify the end result and win every time). I doubt that's how it is designed so it doesn't make sense to me either. I am unsure of this, I was able to back out of it and re-enter as if nothing had occured. Waiting for a Bytes seller to reply to my PM so that I can get the bytes to test and record. I wouldn't imagine so, as technically none of them was scratched. RE: Bug Report and Suggestion - Elitas - Aug 23, 2019 (Aug 23, 2019 05:56 AM)Jelly Wrote: I am unsure of this, I was able to back out of it and re-enter as if nothing had occured. Waiting for a Bytes seller to reply to my PM so that I can get the bytes to test and record. Yes, re-enter and scratch the exact same card; That makes sense. But that doesn't mean you could transfer the card to someone else like you suggested. RE: Bug Report and Suggestion - DNA - Aug 23, 2019 (Aug 23, 2019 06:44 AM)Elitas Wrote: Yes, re-enter and scratch the exact same card; That makes sense. But that doesn't mean you could transfer the card to someone else like you suggested. I'll find out because I noticed that resubmission and cancelling caused it to act differently, not sure. ![]() Good job, even though cancelled, couldn't transfer it RE: Bug Report and Suggestion - Omniscient - Aug 24, 2019 (Aug 23, 2019 11:59 AM)Jelly Wrote: I'll find out because I noticed that resubmission and cancelling caused it to act differently, not sure. Just like I said. We're not noobs at this coding thing. We do have some experience. |