14.2 maintenance: unknown packet and homunculus not detected

[handspoof]

screenshots, cutting few parts to avoid my character name

it's still few hours ago I run my homunculus fine and that's happen after maintenance update. I'm using homun s command as well, not detected...

Here is what happen when you logged in




then the characters stupidly cast homun res pretending it's dead, but in-game client the homun obviously stand near genetic...

[Yavi]

Yea, my client is doing the same thing with my Homun. It's also not detecting a bunch of NPCS. Mainly the Tool Dealers, any of them. It goes to them and then they don't show up.

Edit: It seems it's random as to whether or not it can detect the NPCs. ATM my script is set to autobuy/sell in ra_in01, sometimes it goes in and there are no npcs, other times it goes in and it sees all the npcs just fine. If it goes in and doesn't find the npc, it just sits there trying to auto buy/sell over and over until I do something about it.

[icetea813]

This might not be related but there seems to be a problem with auto storage also. It just talks to the kafra over and over again without storing anything. It used to work fine before the patch. Here is my storage config:

storageAuto 1
storageAuto_npc comodo 195 150
storageAuto_distance 5
storageAuto_npc_type 3
storageAuto_npc_steps c r1 c r0 n
storageAuto_password
storageAuto_keepOpen 0
storageAuto_useChatCommand
relogAfterStorage 1
minStorageZeny 50

Another note would be when I try re-logging it cant seem to find the npc. [s]I was using start.exe when this problems occurred, then I tried wxstart.exe and it was able to use storage fine with wxstart with wx npc talk enabled.[/s]

edit:
The wxstart has nothing to do with it working when I tested it out again. It seems that it is able to detect the npc again when moving away (to the point where you cant see the npc in game) and moving back towards it again. I guess the missing npc triggers when you spawn on the location, but not while walking towards it.

[inv]

screenshots, cutting few parts to avoid my character name

it's still few hours ago I run my homunculus fine and that's happen after maintenance update. I'm using homun s command as well, not detected...

Here is what happen when you logged in




then the characters stupidly cast homun res pretending it's dead, but in-game client the homun obviously stand near genetic...

Same here. Don't know about homunculus bugs. But still playable.

[Pitbull]

Good day!

My name is Pit, I am kinda returning warrior of Rune Midgard =D. To be very honest I am noob in OpenKore however, I was once an advance user of modKore seven years ago.

I have been using OK to bot several account, some for vending, some for leveling and I noticed there has been some post-patch issue this morning. I have no idea how to fix it, I was about to update the recvpacket.txt to fix the first problem listed below but then I am afraid that I might stuffed up something if not everything (/heh). So here goes the list:

1. Packet Tokenizer: Unknown Switch: 099B
2. "Could not find npc at location ......." whilst has been checked the npc is exactly there..
3. Disconnected by itself
4. Attempt to delete char by itself (Luckily it doesn't know my email address)

If someone would spend their precious time to teach me a couple of basic - advance technique to solve this sort of problems, I really appreciate it and I will be more than happy to learn and teach other noobs like me or simply posting important update on this forum as regularly as needed. I have done similar role in the past within the modKore community and I am looking forward to start contributing for OK community.

Regards,
PITBULL

[EternalHarvest]

It seems it's random as to whether or not it can detect the NPCs. ATM my script is set to autobuy/sell in ra_in01, sometimes it goes in and there are no npcs, other times it goes in and it sees all the npcs just fine. If it goes in and doesn't find the npc, it just sits there trying to auto buy/sell over and over until I do something about it.

Another note would be when I try re-logging it cant seem to find the npc.
...
It seems that it is able to detect the npc again when moving away (to the point where you cant see the npc in game) and moving back towards it again. I guess the missing npc triggers when you spawn on the location, but not while walking towards it.

2. "Could not find npc at location ......." whilst has been checked the npc is exactly there..
3. Disconnected by itself
4. Attempt to delete char by itself (Luckily it doesn't know my email address)

As random as promised in FAQ for "packet tokenizer - unknown switch" warnings.

[hihi12345]

I'm not sure I understand what you're saying there EternalHarvest?

[summerkidzz]

i also not understand...now my bot still cant use the npc to buy/sell item

[unkoman]

\tables\iRO\recvpackets.txt
+099B 8 8 1

My client still has packet error,
but it can detect the NPCs

[mastermind66]

^
thanks!