MoetsukiDansei

You have got to be kidding me if you think I am criticizing the guy for not fixing my problem. Do you even understand what I've said here? I would have preferred it if the dude never showed up in the thread at all. Legitimately 0 interest in communicating with the guy. The fact that some people think sharing something with the community in some way makes them immune to criticism... like the guy never criticized people he took code from? Bro... I've been here a month I've already read multiple counts of that. By the way I've stopped using his source entirely. I will never use anything he's touched again. Can I talk smack now? Or... I'm indebted for life for building the public source and running around TI for a week?

I will say I am grateful for the opportunity to run around on a locally hosted game server, to dig around in some code and see if it's something I want to spend my time and money on. But I could have done that on other projects too: L2J, ACIS. And let's not ignore the fact that you have a public version not out of charity but because you consider it a worthwhile business model - due to leaks, competition, sparking initial interest, having a larger base of bug testers, etc. - who knows exactly why? It's another topic unto itself. But man... I asked a issue in a help forum about a core L2J issue, using your public source as an example, and you shill the benefits of subscribing to your private sources? You expect a response that displays gratitude? Who would even invest in sources that don't have a proper change log? Someone with more money and curiosity than sense IMO. If your work was really worth the investment (and let's be honest at $150 there wouldn't even have to be that much accomplished) then why wouldn't you publicly document your improvements? If it saves a programmer days, weeks, a single month of work, why would they not just spend the money? Instead you want people to take your word for it - how good your product is. Just hope your changes are something they would be interested in, relevant to the server they would like to make. I may be new to programming and L2J, but I am not new to life. If it looks and sounds like a scam, it probably is, stay away from it. Saying you'd never have me as a customer? Might as well ban me from MLM schemes or purchasing lottery tickets while your at it. By all means allow Mobius to respond to my post here if he so pleases. But afterwards, if an admin could please lock the thread. Can't see this discussion being very productive going forward.

Well I commented out: player.setXYZ(_x, _y, _z); that may occur after the ValidatePosition packet is received. Then I placed a target dummy and teleported to a location ( x , y , z ) nearby. I sent an attack command and recorded the difference between server/client coordinates for the character. Here's 4 tests from the same location. This is 1 single call (per test) to moveToLocation() (further calls were disabled for the test) ( y is the difference between client/server calculated by player.calculateDistance3D(_x, _y, _z)) ( x is order of ValidateLocation packets received) I did more tests but you get the idea. Given this is a single call to moveToLocation(), can I assume that this issue is geodata related and not functional miscalculations that occur during the move? Wouldn't the difference only get worse if it were due to calculations done server side? If that's true I suppose I should: 1. learn to make geodata. 2. attempt a small area of very accurate data (preferably on some area of steep Z-axis change) 3. try these tests on that area to see if the problem persists. Or maybe it would be wiser to investigate further into the code for issues?

For someone who claims to not have insight, your words have given me inspiration to look somewhere I had not yet, and found something new. For that I thank you. I will continue to look for the solution until I find it, that or pull out all my hair, whichever comes first Unfortunately I don't think L2OFF is a good solution for me as customizing the game in many ways is of great interest to me and extending is surely out of my reach for the time being. I will post the solution here if I do figure it out.

Sorry but what is the point of this reply? I am not asking YOU personally for help. Wouldn't it be strange if every user here replied and said they refuse to help? I have been debugging this for days. Pathetic I admit, but I am trying here. You see a novice programmer actively trying to debug an issue, asking for a hint from skilled individuals in a help forum, and you more or less suggest they quit, wait around for your next free release. This attitude is why I asked here, not your forums, nor in your discord. Anyway this is not an issue specific to L2JMobius, I did say in the post that the issue exists in L2J master branch as well. That being said if the issue existed in L2J dating back 10 years and exists now on the L2JMobius test realm (it does), I doubt waiting for the next free release, or subscribing for that matter, is going to do me much good.

As shown in the gif - after issuing an attack command the character moves to the target, after reaching the target it sometimes stops for 1-2 seconds before attacking. The pack in the clip is L2J_Mobius_04.0_GrandCrusade, but this issue exists on L2J master branch as well. It seems to occur far more frequently when attacking monsters that are farther away (e.g. 600+ distance), and happens very rarely when attacking monsters that are close. Despawning all NPCs on the server, then spawning a single non-moving monster on a hill and the issue still occurs. Though it was happening on flat ground (constant Z-axis), after reducing the number of calls to moveToPawn() (there were many for some reason), it stopped occurring on flat surfaces. Even still it continues to happen on varying Z-axis surfaces. updatePosition() continues to be called even after the character has arrived on the client (server still thinks the character has not arrived I guess). calls to player.calculateDistance3D(_x, _y, _z) in ValidatePosition are returning 150+ throughout the movement. if (player.calculateDistance3D(_x, _y, _z) > player.getStat().getMoveSpeed()) { if (player.isBlinkActive()) { player.setBlinkActive(false); } else { player.setXYZ(_x, _y, _z); } } changing if (player.calculateDistance3D(_x, _y, _z) > player.getStat().getMoveSpeed()) to if (player.calculateDistance3D(_x, _y, _z) > 0) seems to improve the situation maybe? I imagine there are terrible side-effects to this I noticed this bug does not exist on ACIS servers, but comparing the two sources (I understand they are drastically different), I cannot seem to understand what may be causing this. At this point I'm not sure where to look next. I have started looking at geodata/geoEngine from here, but as I'm pretty new to programming and even newer to L2J server development, I have no clue if this is remotely the correct direction. I'm hoping someone can give me some advice, or a hint, or anything, where I might look next to solve this.