- 0
-
Posts
-
By tomlondon12 · Posted
We are taking new orders. DM us on Telegram! -
By KiddSupreme · Posted
Account Features ➡ EARLY SUPPORTER BADGE ➡ NO QUEST BADGE ➡ 24 MONTHS BOOST BADGE ➡ 1 YEAR NITRO SUBSCRIPTION ➡ CREATION DATE IS 2017 ➡ ACCOUNT STANDING STATUS IS ALL GOOD ➡ CLEAN BILLING ➡ OGE MAIL OUTLOOK PAYMENT METHODS ➡ CRYPTO ➡ PAYPAL ➡ CASHAPP ➡ BANK TRANSFER ➡ GIFTCARDS ➡ ZELLE ➡ VENMO CONTACTS ➡ DISCORD : crh11s ➡ TELEGRAM : crh11s CONTACT WITH ME IF YOU ARE SERIOUS BUYE -
To check the operation of npc movement. You can turn off all movement in the game and move only the npc you want using the move to package. This way you will reduce a lot of unnecessary code and understand where the problem is. And all your maps are not thread safe and you are using multithreading startQuestTimer("move", 5000, npc, null); -
-
Verify if following is supposed to be the way to handle movement npc.getAI().setIntention(CtrlIntention.AI_INTENTION_MOVE_TO, new Location(point.getX(), point.getY(), point.getZ())); For me, it's not enough. And if it's the case, whole AI system is probably buggy.
-
-
-
-
Topics
-
Question
tazerman2
hello all i am looking a old rev before update geodata
because i need fix the big problem with pathnode.
the problem is the character is not move to target if
character is back from a wall and some time is stuck
to wall i try fix geoengine but 30% from geodata say
can't find path node. So i change 5 geodata and say same.
after much test i test geodata from another pack with fix mouvement
and the character is not stuck to wall and if you target a and and click
attack character is moving normally without problem so i want test if
new geoengine is problem.
8 answers to this question
Recommended Posts