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.
Recommended Posts