|
Removing the mob files helps, I do that too, but even then I think the JPNs have a hack far more powerful than that. To see what I mean.. use a program like artmoney to search for a monster name in the same area as you.
I used a crawler in the maze, but anything that spawns in there same spot, with nothing else by it works.
Near the end of the address range, 1000-0000+ is usually where its found. Scan through till you see the 4 byte target index, 4 byte mobid, and then name. My example it looks like
77 00 00 00 77 60 0c 01 43 61 72 6e 69 76 6f 72 6f 75 73 20 43 72 61 77 6c 65 72 00
This area of memory is updated very frequently, like on a pulse, and is the area I think wyvern uses for his radar thingie. Its very fragmented and I haven't yet figured a reliable way to seek it out :P
36 bytes after where the monsters name starts, there is a 4 byte pointer that points to a structure I don't compleatly understand yet.. I think the sturcture describes what the monster is doing, direction its facing, what its doing, etc, but either way, its 00 00 00 00 if the monster is dead and points to something when its alive.
Now here is where it gets interesting.. Make a macro like /targetnpc /ja "Provoke" <t> and write a script that reads that memory address (it changes everytime you zone, reboot, so you gotta do this all at once) till its non zero and spams that macro 10 times a second.
Kill the monster, start the script and wait...
Every time you see
>> /ja "Provoke" <t>
...A command error occured.
Thats .1 second at least (since, if you spam a macro a billion times, only a few activate) since your computer found out it spawned till you were able to voke.. I sometimes see 8 of those fly by before i get a successful voke.
Maybe my computer is slow? I tried this test at 256x256 resolution, and I have a 2.8ghz p4 with a geforce4 and 512 megs of ram.. I bet this test would be more extream on a NM model that my computer hasn't loaded from disk yet.. I'll try this on behemoth someday :P
The whole reason I got started on this tirade is when I was useing wyvern's map plugin and saw King Behemoth's position move like 3 seconds before I could see it or target it.
My theory is that our client waits for two things before it will let you target it. The pulse updates that happen a few times a second that include just x,y cordinates and maybe a different streamed update that flows and gives you things like what model to display, what clothing, what direction its looking at, what its doing etc.
Explains why you see all the radar dots in jueno the instant you zone in, but it takes forever to see the actual people :P But our client lets us target players by name with /target Name, and we will target someone who hasn't loaded yet. The client doesn't let us target monsters not loaded yet..
Listen, the JPNs on my server don't beat us.. some of the times.. We haven't claimed a ground HNM since novemember besides adamantoise. We only got that king behemoth claim back then cause of daylights savings time, the Japanese were too stupid to do the math and showed up an hour late. My ping to pol is only 168ms, I do all the common tricks like removing files so I don't see darters during fafnir or elementals during behemoth. I go to the job ablity menu and select provoke, and have xunleasehed spam the y and enter key for me 20 times a second each and I always always always always always loose. This has been happening once or twice a day for half a year.
If i had a hard drive to dump the 330 megs of ram ffxi uses, to disk 10 times a second I might be able to figure this out easilly :P
|
. As for voke bots to target the monster in specific, I haven't seen anything yet to do it correct.
Who is online