![]() It provided previously omitted information on battle details, such as battle engine, and laid the groundwork for an ever-expanding logging system. While imperfect, the system was an important first step. It's main goal was to provide our support staff with enough information to attempt bug replication. ![]() Initially, the battle log was a simple system used to record a small number of interactions that occurred during battle. The first steps towards eradicating the waiting glitch were taken in 2015, by adding the first iteration of battle logging. So how do we go about trying to fix it once and for all? This makes fixing the issue particularly challenging since when someone talks about "the waiting glitch," they could be referring to any number of potential problems. This is unsurprising, it has existed for so long due to the fact that the most infamous "glitch" in Pixelmon is actually a combination of hundreds, and potentially thousands, of bugs all leading to the same result. In fact, the earliest mention of it dates back to 2016, and the first bug report dates back to version 4.2.7. This is an issue that has unfortunately plagued Pixelmon for many years now. The example below illustrates what it looks like, and we are sure it's not an unfamiliar sight for many of you. This creates a loop that is now known as the "waiting glitch." Although it is simple to explain, there are various ways the client can end up in this loop. The server ends up in an unrecoverable state, leaving the player waiting for instructions from the server while the server thinks it has already sent those instructions. To those who experience it, the term "waiting glitch" refers to a bug that occurs during battle, causing an error that locks the player into the battle UI. IntroductionAs we all know, battling has suffered from the infamous "waiting glitch" for a long time now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |