Leaderboard

http://i.imgur.com/v52VMFA.png Dear Ninja, Today we fixed one of the biggest server crashes plaguing the games development, and with it comes a lot of lessons for the future of the game's development. We now know some things to look out for and avoid when coding the game, and we now have the means to debug crashes like this in the future. The reason this particular crash was so unsolvable was that it wasn't actually crashing the server. It was creating an infinite loop in calling server game logic. Which didn't crash the server and provide any debug information, and our current server was not able to give any debug information when attempting to debug through the latest version of Visual Studio. It turns out that our dated technology required the use of dated copies of Windows and a dated copy of Visual Studio to give us the debug information we needed, and I would not have been able to discover this without @Seth. It also took @Robin's knowledge in debugging methods to figure out what was causing it. I've spent the last couple of weeks blindly testing the server to see what would cause crashes, it took me and Seth stress testing parts of the game blindly, as we collected useful data and information from players about what they felt was causing the crashes. While I cannot disclose the exact cause as of yet for the game's server security, I would like to say that some of the information given did in fact make sense once the bug was found. The discovery took the efforts of Seth, Robin and myself convening over a long period of time analyzing the course of action to solve the bug. I also would like to thank Pokemon Planet's creator, Brody, for also providing assistance, and advising possible courses of action as well @Abhi for agreeing to put aside time from his busy exam schedule to look into it when I called him. Lastly I'd like to thank all the players who have been patient and sending me reports on possible causes for the crashes over the last week. Thank you to Nintendave @Bolan Vongola @Dayum Mirana @Riley @Sukki Ohiya @Jellal Kuraen @Oriax @Itachi Himitsu @Lumy @Shissei @MrChubb The Hozuki @Origami Heart User_name @Lain and whoever else gave useful feedback and encouragement, you're all top notch beta testers. This may not be the last problem causing crashes, but we now have the means to debug any similar problems (which there might be). Hopefully this means a much more stable Nin Online server immediately, or in the weeks to come. However, I would like to apologize in advance that the goals of 2018 (Adv. Masteries / Mist) may come a bit later than end of the year. I was initially going to rush out a lot of content by the end of 2018, but I've decided that in the spirit of Christmas, I'll be working on making the server stable and doing a Christmas event again, because we haven't had holiday events this year. Regards, Rory Edit (26/10/2021): For historical purposes, this crash was due to body flicker technique warping players randomly to a spot around the target. But if the target was at a corner of the map, it was looking for a spot outside the bounds of the index, and because this was a while loop, it was creating an infinite loop of finding a potential spot. It's such a simple issue in hindsight, but impossible to find with the kind of reports we were receiving and the lack of any debug information. There were all kinds of checks in place, but a while loop was still not a good option for this.

December Chunin Exams is postponed until further notice due to server instability! We're sorry for the inconvenience.