Already did test it. There is no possible way for someone to legit hit more than 1 damage on bigfoot. Even on my GM with 30K in all AP, I'm unable to hit more than 1 damage with any holy based skill (Shining ray, Genesis, etc) on Bigfoot.
Unless you can give us a valid explanation as to how you managed to do this sort of damage on Bigfoot, there's nothing we can do except close the thread.
A valid explanation? You guys should tell me why ban someone that NEVER hit more than 1 on the BF. Why I was banned w/o using hack. Theres something really wrong here. And I wouldn't still arguing if I was wrong. I really regret the time I've wasted in this server that ban innocent people out of nowhere, and the GMs only tell me that theres nothing they can do, and just keep accusing me of 'Hacking'. I'm really sory if you guys can't really check who uses hack and who doesn't. And I'm really sorry if that was probabbly a bug and none of you can see it... I rather play on another MS that won't ban me for something I didn't do. Goodbye.
Our cheat tracker wouldn't report that you did 3.2k damage on bf if you only hit 1s or misses on it. You're likely to run into the same problem with any server which has a cheat tracker. Can I just ask an obvious question - were you using any kind of magic attack potion? If so, which one.
Probably not, I was just with my buffs. Me and my brother killed several BFs this same way and I never hit more than 1. Maybe this is a issue with Meso Explosion (my brother was exploding mesos at that time), I don't know.
OK, GM Tim and I tested this out as thoroughly as we could. We logged in using the regular MapleRoyals client (GMs normally use a different client) and used a Priest and a Chief Bandit to test things out with. We formed a party and spawned a Bigfoot and 4 Elderwraiths. He used Meso Explosion to attack with while I used Shining Ray, and we tried this out several times in an attempt to see if it would trigger an autoban. It didn't. Obviously, if we discover there is a bug, then we will unban you, but at the moment, none of us have been able to replicate what happened to trigger your autoban.
Well, thanks for at least trying, and I hope you guys find an explanation and this probable bug soon...
