If you want to receive support we need this info to help you properly.
» Find Revision
L2J Revision Number:7669
L2JDP Revision Number:4422
Object Id at bad coords: (x: 235467, y: -76810, z: -1536).
Object Id at bad coords: (x: -1829542, y: -1737286, z: -162035
Object Id at bad coords: (x: 4753568, y: 261660, z: -3610).
Object Id at bad coords: (x: -1733106, y: 1533329, z: 659544).
Object Id at bad coords: (x: 4906590, y: 43546, z: -3610).
Object Id at bad coords: (x: -1896752, y: 490834, z: 1144360).
Object Id at bad coords: (x: -605053, y: -2092010, z: -165969)
Object Id at bad coords: (x: -1278957, y: -595048, z: -3728).
Object Id at bad coords: (x: -274146, y: -2269411, z: 170826).
Object Id at bad coords: (x: 513748, y: 1224368, z: 9490).
Object Id at bad coords: (x: 2280562, y: -1113785, z: -15118).
Object Id at bad coords: (x: 1235708, y: 2043759, z: 729086).
Object Id at bad coords: (x: 1606346, y: -1370792, z: 694572).
Object Id at bad coords: (x: 807912, y: 1293423, z: -2992).
Object Id at bad coords: (x: -8625377, y: 3789998, z: -3610).
Object Id at bad coords: (x: 2118496, y: -1114653, z: 590907).
Object Id at bad coords: (x: -1250042, y: -621494, z: -3065).
Object Id at bad coords: (x: -2267146, y: 719593, z: -32252).
Object Id at bad coords: (x: 58168, y: -1472573, z: 8505).
Object Id at bad coords: (x: 2123705, y: 1179918, z: -275744).
Object Id at bad coords: (x: 1852650, y: -1497134, z: -3088).
Object Id at bad coords: (x: 1758721, y: -1573936, z: 26632).
Object Id at bad coords: (x: -1296047, y: 639685, z: -240).
Object Id at bad coords: (x: -1039249, y: 2059874, z: -390920)
Object Id at bad coords: (x: 2365748, y: -568723, z: -488112).
Object Id at bad coords: (x: -1227456, y: 3055118, z: 439051).
Object Id at bad coords: (x: 478241, y: 2387685, z: -4200).
Object Id at bad coords: (x: 1451280, y: -2940459, z: -3712).
Object Id at bad coords: (x: -1377365, y: 480899, z: -240).
Object Id at bad coords: (x: 33039, y: 2509303, z: -242871).
check all tables that spawns mobs and npc could not find these
i did search only found one other post like this but it was no help
Object Id at bad coords
Forum rules
READ NOW: L2j Forums Rules of Conduct
READ NOW: L2j Forums Rules of Conduct
- janiii
- L2j Veteran
- Posts: 4269
- Joined: Wed May 28, 2008 3:15 pm
- Location: Slovakia
Re: Object Id at bad coords
you can try this patch to find out from who and where it was called:
Code: Select all
Index: java/com/l2jserver/gameserver/model/actor/position/ObjectPosition.java===================================================================--- java/com/l2jserver/gameserver/model/actor/position/ObjectPosition.java (revision 4422)+++ java/com/l2jserver/gameserver/model/actor/position/ObjectPosition.java (working copy)@@ -14,6 +14,7 @@ */ package com.l2jserver.gameserver.model.actor.position; +import java.util.logging.Level; import java.util.logging.Logger; import com.l2jserver.gameserver.model.L2Object;@@ -66,7 +67,7 @@ } catch (Exception e) {- _log.warning("Object Id at bad coords: (x: " + getX() + ", y: " + getY() + ", z: " + getZ() + ").");+ _log.log(Level.SEVERE, _activeObject.getName() + " (" + _activeObject.getObjectId() + ") at bad coords: (x: " + getX() + ", y: " + getY() + ", z: " + getZ() + ").", e); badCoords(); } }
DO NOT EVEN TRY TO MESS WITH ME!
forum flOOder dancing dEVILoper ♀
I don't give private support - PM will be ignored!
forum flOOder dancing dEVILoper ♀
I don't give private support - PM will be ignored!
-
- Posts: 60
- Joined: Fri May 19, 2006 5:55 pm
Re: Object Id at bad coords
Ok will try just hope it happens again strange thing is no one was on the server as it is not live yet yes it is being hosted on a server box and a good one at that will install this and see what comes up when it does
-
- Posts: 173
- Joined: Fri Nov 06, 2009 6:32 am
- Location: Argentina
Re: Object Id at bad coords
I had the same problem ... Change of hosting boy who had a bigger one and never saw the problem.
Someone once told me: "The easiest way of doing things, making them the hard way"