Patch Notes 9/25/13

[Klepto]

NOw it is important to note that some people were told by customer support in the past that the extra sails were a bug/glitch. REALLY???? We aren't stupid. The gems and the sails don't share coding, so it was intentionally put in there.

You can't possibly know that without seeing their code. Just because a feature is separate in the UI doesn't mean it has fully separate code behind the scenes. Code reuse is desirable in order to keep your code base small and more maintainable, at least in most development offices. I'm not defending them here, just pointing out you have no idea what their code looks like, and it's dangerous to assume its structure when making an argument, as for all we know there was some intertwined code that was causing a reset on the number of sails.

[Bubba87]

You can't possibly know that without seeing their code. Just because a feature is separate in the UI doesn't mean it has fully separate code behind the scenes. Code reuse is desirable in order to keep your code base small and more maintainable, at least in most development offices. I'm not defending them here, just pointing out you have no idea what their code looks like, and it's dangerous to assume its structure when making an argument, as for all we know there was some intertwined code that was causing a reset on the number of sails.

I'm no coder by any means, however if they did reuse code that *happened* to cause a glitch that reset sails, it would be logical that this same glitch would reset other aspects like investment, benefits, or labs...not saying that they didn't "reuse" code in just an instance of sailing and gem purchase causing a rest, but if the recycled in one element, it is more logical to assume they recycled it else where as well. Nothing else was seen to have reset after gem purchase, thereby implying that purchasing gems indeed reset sails, was intentionally inserted, and was not a bug/glitch...but again, I'm no coder.