Damage hack explanation

[greenhouse95]

Hey, it's been quite a while since I've played Metin2. But back then there was the damage hack that worked by changing the .msa files. I've never really got into how it worked, and now after thinking about some good ideas to implement it, I wondered how does it work. Like, what does the hack change in the file, to make it attack without moving and at higher speeds.
I mean the damage hack that when you attack, it'll hit everything around you multiple times. I've looked around for any mention of it, but couldn't find anything, that's why I'm posting this.
So, If you've ever done one or have any idea on how did those work, I'd appreciate a brief explanation. Thanks

EDIT: I did find with a bit of information, but not much.

[sad666]

msa files hold the sphere information that check for collision between weapon and target when attack process. So if you copy this information 10 times, 10 spheres will be calculated instead of one sphere during the attack and you will deal damage as if you hit 10 times. I think you want to simulate these duplication but don't forget that every success attack process end with OnHit event handler. I mean duplicating the sphere and calling the SendBattlePacket 10 times will be the same thing. The only difference is how you send the attack packet.

[greenhouse95]

I see. Interesting. So, what would you duplicate from it exactly? The Events? And do they need to be any different?
It's really cool to know how it works, I've always wanted to know. But in terms of making it work, how would be the process of going from the default msa, to making one with multiple collision spheres? There's quite a few files and lots of information in there.
If you don't know, it's fine. I sure will be doing multiple trial and error. Thanks

[sad666]

copy "Group Event0x" and increase x by 1 each time also you need to re order the their StartingTime. You can edit position and radius too for bigger attack range but if mobs not close to you enough, it will only affect visual since there is a server side protection.