Cole
I wonder why unit + selenium tests were unable to identify this bug. But I guess, you won't discuss this in public. ;-)
I don't mind. The initial patch was intended to address attempted flood attacks on design, essentially attempts at cheating. Along with a complete rewrite of the system aimed at preventing increasingly sophisticated attacks, an additional check was added to only allow design updates within 1 second of a previous change. However, in rare circumstances the timestamp in question was sent as a NULL value, and such a value failed the security check, so the design update was not allowed to pass. It misfired in this case but was quickly and easily remedied.
The system was also designed to take design points from anyone attempting to cheat without giving them design upgrades, so not only would it not work, but such activity would have a negative impact on anyone attempting it (for my own amusement).