The lotto winner.... number ZERO? Are you serious???

[MiaShino]

What my guess would be, and it's just a guess, is that they likely tested the results for a very large number of entries. The odds of ending up with a 0 when there's only 2 entries is relatively high (that being even odds of getting a 0, 1 or 2). If, however, you test with 2000 entries the ends up ending up with a 0 result are tiny. That doesn't mean they shouldn't have caught the issue beforehand but I can see a world in which the error was missed, especially if there were essentially rushing the system out the door.

The last part of the post seems to be precisely what hath occurred. How do you even miss the eventuality that there will be only one bidder on the house? That.. that is the easiest possible thing to test for and one of first things I personally would have tested against because of how fricken common it might be.

One quick glance at the code could have told you zero was possible outcome because why the heck would it not be?

Five minutes of reading your debug statements would have caused realizing to occur.

I do not believe they do any Q&A testing at'all over there. Twenty four hours of maintenance to release catastrophically broken system? Would fully expect to lose my job if I did this - be demoted - or spend substantial time being reamed by my boss and rightfully so. You are yelled at for more insignificant things in this industry. How half of these people managed to maintain a job and have not been blacklisted by nearly every tech company in field boggles the mind.

Main expac launch? Bork the login system to point sales must be suspended now this..

Am sick if paying these corporations to be their Q&A team. I assisted in solving their little audio bug and it took me ten minutes of thinking about it before had working solution. They claimed to be incapable of re-producing the issue yet after post is translated they somehow understand how to fix it.

How about they start paying me? Pretty sure the solution is not "complex because many variables" and is just "oopsie poopsie we forgot number start as zero". I firmly believe this because of the number of amateurish issues within their codebase. I could see them being this dumb.

Heck! Still waiting for NTT nodes on hop 3 - 4 to be fixed.

Wondering how the lead manager of mmo project doth not understand how latency works yet is even allowed to release statements like that.

I am wondering many things about this company and can state this. If my friends are told to re-enter the lottery they rightfully won they will no longer subscribe. Without them (my reason for even playing) I too shall unsub. Sure sure I am just one lala but there are limits for all. Keep screwing up and you will kill your game, simple. This is one big screw up of many recently.

It could be rushing. I could be something overlooked. It could be the system is more complex than we think and it was a corner case they didn't test. None of us can really say what they should or shouldn't have known because we aren't looking at and working with their code.

It is simple pseudo RNG function that selects number then writes number to database then compares against your entry number. Why would it be any more complex then this? How would it be more complex then this?

Have personally written thousands of similar functions they are not complicated. Probably lifted code from the system that selects Cactpot winners because why re invent the wheel.