Not to mention not every engine may handle the same formulae exactly the same....so while it is a basic thing, the fact a bug cropped up should prove that lol.I can't wait for this feature!
Zirael, let me reiterate what he said above because you seemed to have failed to acknowledge it. Programming is a very complex environment with strict deadlines, roadmaps, regression tests, and versioning. It is not as simple as "oh but look at da google." Just because it's easy doesn't mean they have developer time to fix it right now this close to the patch release.
I think it would be fun to add a /janken (rock, paper, scissors) command
rand() doesn't return a uniform distribution of numbers, they'd probably use something more complex.
also, i imagine the bug isn't just "Oh, our random command keeps returning 7, that's weird."
I'm going with the comedy "someone discovered a way to screw with the /random seed clientside" reason.
Alternate comedy reason: NSA backdoors.
Just a sec ... it's a joke, right? Or are you serious, it was done clientside?
That's even a bigger fail than SE's notorious refusal to encrypt the TCP streams.
You clearly aren't aware of absolutely terrible the engine and coding they use is. It's over complicated for no reason. I mean look how many months it took them to add a '%' feature to hp? Far too long.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.