Attachment Point Errors

So I've got this model I was working on...
No, it's nothing even partially decent, it's actually just a demon hunter minus alternate animations, geosets, and materials.

Well, I got everything happy and working in Magos Model Editor.
Then I tried importing it into game...

Apparently the attachment points (All of them, from origin to right hand) go to a point something like 300 over where the origin SHOULD be.
Now I went back to Magos Editor and loaded him up, and the coordinates for the attachment points look fine.

I'm curious if there's some trick I should know about or if it's just my crappy luck that's causing this.

In any case, I attached the model.
I'd love some help, thanks in advance!

Could be that you've deleted an object or two, and the pivots are all messed up?

Perhaps the attachmentID lines are playing around too; delete them all.

Check the points themselves aren't animated either, but that's unlikely.

I suppose knowing what a Pivot is helps in this situation.
I did delete a couple objects, but Im not sure how to check pivots.

Those lines are where? And so once I've found them delete them all?

I doubt the points are animated, they're just taken from the original DH model, so it wouldn't make sense if they were.

Pivot points are coordinates used by bones, sounds, attachment points, bloodspits, etc. They are at the end of the mdl. Note that they start counting from 0.
No time to see your model now.

Yeah, find all the instances of "AttachmentID" in the MDL and kill kill kill.

There have been a few other models that have been messed up by these lines. Try that first, at any rate.

Excellent, absolutely excellent.
That fixed it right up.

You're brilliant, ArrDeeZizzle.

ArrDee... ARR DEE ZIZZLE?!

You should show some respect, else I might give you hilariously inaccurate MDL hints next time! *growls*

Still better than Nazza, eh.

You love it, Nasbo.

Please don't wink at me again, or I may fall prey of your sex-appeal.

What are AttachmentIDs exactly?

I haven't got a clue. But somebody came up with a similar issue a while back and that was the solution. Something half-assed that Blizzard did and we're not supposed to mess with, no doubt.