Recent content by AngelSpirit

Re: [Guide] OnTemporaryStatSet (v15x) Thanks for the feedback! One by one: The encode is ordered. It is sorted before being written in the call to MapleBuffStat.sortBuffStats(), which handles getting the order of the stats to be written correctly. I would argue that the serverside...

Re: [Guide] OnTemporaryStatSet (v15x) Anything actually useful? It's strange that you came just to tell people it was wrong without providing anything correct yourself. If you can correct me, do so. This isn't a challenge, I'm honestly asking you: Please tell me what is wrong. A guide is no...

I originally started writing a whole long post here, but then I realized that with how long it was getting it should just be a general guide. Fraysa: You must be registered for see element.

Disclaimer: I have not worked with GMS since about version 162. It's entirely possible they tore out all the buff code since then and replaced it with something sane...but I doubt it. Nexon sure loves to cling to their ten-year-plus crapsack code, and buffs should be no different. This guide is...

It depends on the source you're using. Somewhere in your source there should be a list that matches items to their optionType values. Find that and change the type of your desired item(s) to be included in weapons. I think weapons are optionType 10 or 11, but don't remember. If you're running...

You're missing a lot of things. For starters, it's a loop for each projectile, not just one block. Also, the same packet is used for all sorts of other skill projectiles, not just Soul Seeker. Here, take a look at mine: MaplePacketLittleEndianWriter mplew = new...

Sounds like some oddity in your projectile values. I once had a similar problem caused by conflicting Object IDs. Can you post your projectile packet structure?

Is your MapleLib updated? Seems it's missing a property type. See: You must be registered for see element. It's also possible there's (another) new type as well, but try that first.

Figured I'd throw in my input on this. That int is a "stack ID" assigned to every buffmask in a buff packet. You can leave it as literally any value and it won't cause the game to crash. However, in order for buffs to stack with each other properly you need to track and use the stack ID...

It's not in the attack packet. The attack packet (server recv, that is) contains no information about critical hits. You have to do it entirely serversided, which is why it's so difficult.

It's in the client.

It's a client check. You can, however, force Androids to wear non-cash equipment just fine (through various methods; editing item positions in the database will work, as will forcibly equipping through, say, an NPC or command).

Ah, that. I remember working on that in MapleCrystal's 117 source. It's mostly fixed there, so you can get the masks (and code, for that matter) from there.

It depends, actually. What skill are you trying to fix?

You can't. Buffmasks are serversided, so even the client won't tell you which buffmasks belong to which skill.