We know that's irritating when people use glitches on the Geodata to go to the underground in the Olympiads, Territory War or Siege. And in fact, these are the main problems. So I came here to clarify this matter completely.
First, I would like to say that we can't solve this problem by simply changing our Geodata files. Of cuorse we've tried this (and many other things, configurations, etc), but so far, no progress. We believe that this problem resides on how the L2J reads and deal with the Geodata files (the L2J Geoengine). We believe that the only way to solve all this, is by updating our L2J server to their latest version, which they built a new Geoengine. We don't know if that will work for sure, but it's already on the way. However this will take some time to be done. Everything we ever did on the server will need to be transfered to this new version, where many things work differently. And we must to it right. So, please calm down and wait for that.
Until then, the only thing we can do is punish those who use these glitches to perform any kind of anti-game. We came to the conclusion that these glitches are extremely rare to happen by chance, this means that it must be forced. Of course that we can't put a GM to watch all Olympiad arenas at the same time to find anyone who is attempting that for example. This means that if you want justice, you must report to us. How? Well, in the Olympiad a few Screenshots of the whole arena (including the /time command - very important) is enough. Unfortunately, fights against daggers we'll need a movie. A L2 replay is fine. How to report? Exclusively here.
About the Territory Wars and Sieges, it will work by the same way: reporting. But we'll try to let a GM online on Territory Wars and Sieges. So if you suspect or find anyone using Geodata glitches, just send a Petition to the GM and he'll take a look. The punishments for that will be severe.
Thank you for understanding.
New update on this matter (01/06/2015)
We saw lots of complaints on the L2J Forums regarding this new geoengine of theirs, basically, the same problems still happens on this new version. Knowing this, not even worth upgrading to the new version at the moment because we would do just for that reason.
Now, we're looking for alternative solutions. We heard about some systems that fixes this geodata problems by putting you on the ground again. We just need to implement it, but it's not easy since it's some code from a russian java project and a lot of stuff is missing.
First, I would like to say that we can't solve this problem by simply changing our Geodata files. Of cuorse we've tried this (and many other things, configurations, etc), but so far, no progress. We believe that this problem resides on how the L2J reads and deal with the Geodata files (the L2J Geoengine). We believe that the only way to solve all this, is by updating our L2J server to their latest version, which they built a new Geoengine. We don't know if that will work for sure, but it's already on the way. However this will take some time to be done. Everything we ever did on the server will need to be transfered to this new version, where many things work differently. And we must to it right. So, please calm down and wait for that.
Until then, the only thing we can do is punish those who use these glitches to perform any kind of anti-game. We came to the conclusion that these glitches are extremely rare to happen by chance, this means that it must be forced. Of course that we can't put a GM to watch all Olympiad arenas at the same time to find anyone who is attempting that for example. This means that if you want justice, you must report to us. How? Well, in the Olympiad a few Screenshots of the whole arena (including the /time command - very important) is enough. Unfortunately, fights against daggers we'll need a movie. A L2 replay is fine. How to report? Exclusively here.
About the Territory Wars and Sieges, it will work by the same way: reporting. But we'll try to let a GM online on Territory Wars and Sieges. So if you suspect or find anyone using Geodata glitches, just send a Petition to the GM and he'll take a look. The punishments for that will be severe.
Thank you for understanding.
New update on this matter (01/06/2015)
We saw lots of complaints on the L2J Forums regarding this new geoengine of theirs, basically, the same problems still happens on this new version. Knowing this, not even worth upgrading to the new version at the moment because we would do just for that reason.
Now, we're looking for alternative solutions. We heard about some systems that fixes this geodata problems by putting you on the ground again. We just need to implement it, but it's not easy since it's some code from a russian java project and a lot of stuff is missing.
Comment