-
Notifications
You must be signed in to change notification settings - Fork 16
keys get eaten without being used #10
Comments
I tried to reproduce it, but with 5 keys (and setting remove duplicated): Only the first key got removed and the rest stayed in the same order. From looking at the code, only right codes can be removed (depending on the answer from ASF). About the order I am not 100% sure, but if I remeber lists and arrays in C# correct, the order of the remaining keys can litteraly not change. Did you had every key in a seperate line or some in the same line, seperated with ","? Edit: There seems to be a bug, when the last key would be removed, which should not happen (from looking at the code) as well, so maybe there is a part in the code responsible for that, which I missed. |
For the reorder part - it happened to me much earlier, but it did not matter. But for other stuff, which is far more important ... I can only hope it was the only time it happened :/ |
Well it's not my code ;-> But jeha But for the other Problem (see the other issue) that should not happen as well ^^. Don't know, when I will have more time. |
I've tried redeeming multiple keys with your UI. Earlier it worked, but after some updates your UI seems to be eating keys. For you to be able to debug the bug ( :) ) you can try to check the code, what is happening, when you put multiple keys for single title to redeem on single bot (i.e. first key should be activated, rest should have "Already Owned" status. So only the first key should be removed from the text box. In my case, removed was first and ... unknown key. 8 keys in, 6 keys out in messed up order (2nd to last key was placed as 2nd, not sure why this app changes order of keys).
The text was updated successfully, but these errors were encountered: