[Kayot]

People are complaining about jumping, not warping. They need to correct that.

Jumping or Holding is what happens because of either packet hacking, or #commands inside the same zone. MQ2 can't jump as it uses the EQ client and all of it's built in limitations. Holding happens if there is a ton of system lag. The server attempts to estimate where the client should be until it gets a packet. This is best observed (Ironically) two boxing with one client in the background. The second character seems to bounce backward over and over. I haven't found a way to have MQ2 over come this or to Jump to me or any where else.

As for summoning, I haven't found any case or code that will allow the summoning of items with the exception of #si or #summonitem being unrestricted OR having an alias that the MQ2 could find, in which case it is the Servers fault for leaving an unsecured command AND summoning an item within the packet watching range on a MQ2 Client running with a Plugin that I have yet to see with that aliased command. (As far as I can tell, it's impossible to see a #command as it stops at the server.)

For skill ups and AA, I'm not sure about the AA's and most of them don't work anyway. Skill ups are restricted by the client and there for only happen due to an exploit in the Skill system itself which could be done without MQ2.

Here's a question, have you ever used MQ2? I think most of the fear is caused by ignorance. openKore suffered from allot of that too. When I tried it I was impressed. I make a priest that followed me around and healed and buffed me. The main difference is openKore is stand alone while MQ2 hooks into the client. openKore even had to have built in functions to keep it from Jumping. oK also had something I wish MQ2 had. The ability to keep from KSing. It hasn't happened, but I know the possibility is there. So much that I put in a sniplet to prevent it. I'd like to make a plug in.

Other wise, MQ2 is just what its name states MacroQuest.