+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: Script Help (/Forum-Script-Help)
+--- Thread: Access Violation in CChar::CanMoveWalkTo (/Thread-Access-Violation-in-CChar-CanMoveWalkTo)
RE: Access Violation in CChar::CanMoveWalkTo - Norlack - 03-02-2013 12:49 AM
yes, and I'm sure that those two spawn gems were placed after all this mess started. In short, nothing to do with the problem.
RE: Access Violation in CChar::CanMoveWalkTo - Mordaunt - 03-02-2013 01:18 AM
When I said that gembits I described can and do cause this problem, I was speaking the truth, it has been verified by the devs, who were looking at that very issue last night.
Attitude because correcting that issue did not solve the error is not going to fix it any faster...
RE: Access Violation in CChar::CanMoveWalkTo - Norlack - 03-02-2013 01:57 AM
Sorry but I don't get the point of your last sentence...
I'm very quiet. I just said, in my own case, those two specific gems were unrelated with the issue; not that bad spawns couldn't cause errors like this. ^^
RE: Access Violation in CChar::CanMoveWalkTo - darksun84 - 03-02-2013 03:09 AM
i tried to manually reproduce it by modifying the position of some npc(by changing the p value in the sphereworld.scp), but sphere automatically deletes them (Garbage collection) after a restart.
RE: Access Violation in CChar::CanMoveWalkTo - RanXerox - 03-02-2013 09:39 AM
Hmmm, worst case scenario, stop the shard, edit the sphereworld.scp file and remove the offending NPCs that have locations out-of-bounds...
***MAKE A BACKUP OF THAT FILE FIRST!!! Just-in-case ;-)