Originally Posted by Multo
SlikStik is don't even know what he is doing...
Prove :Code:[0A 3E 65 00] < Monster Object ID [01] < Animation
the attempt of flaming is to cause the thread to be closed and nothing else to make believe I created a false thread..
maybe you guys should see yourself for now who is trying to help or who is trying to kill the section off..
Just make an SVN for ur source..
just update the scripts on github :P
He's not doing that for the current version to prevent leechers.
Back on topic, one way to get kill monster is to go into a monster map, kill a number of monsters, look at the list of possible monster opcodes, and search for the one that appears the same number of times as the number of monsters that you have killed.
Edit: By the way, I don't update GMS (due to the ip block), I only update MSEA, so I cannot provide GMS opcodes or check whether your opcode is correct.
kill_monster = 0x278 but something was changed and idk what -.-
I plan to release the source soon.. but the lack of help Im getting has only cause me to think otherwise also to prevent leechers and some angry flamers.
of course you have lack of help, nobody likes you
It only takes 2 days at most to get ingame from v144 to v146. It only takes 7 days at most to sniff everything that you'll need. This is all assuming you have next to no clue what you are doing.
Seven days to sniff ? WTF? Do you take 68534 breaks? It's at most a day
No. It is just that I don't sniff for 24 hours (maybe 1h in a day). Also, do take note of the "no clue what you are doing" :P
Sure..
SPAWN_PLAYER isnt updated right ? I see many opcodes here that arent updated to 1.46
But there are some that are updated, those saves me a lot of time of sniffing from gms, too bad I already sniffed most of them from gms :/
Mmmm, MapleStory smells good.
Yet operation codes are not a problem at all while packet structures change as birds fly.
Reply With Quote