this REALLY annoying when im skeling I allways need to go after my pet and loot the meso myself . *It's not allways not-looting meso , but like , half of the time it doesn't. and it doesn't matter if im standing on the bag whatsoever or how many time my pet will walk on it. my pet is a Husky ,lvl 10 if that helps..
I think this happens mostly when you jump down from a ledge. The pet seems to not realise that you have changed ledges and doesn't loot meso. Whereas if you go down a rope/ladder and jump off the rope/ladder onto the below ledge it is fine. Let me know if this corresponds with the issue you are having.
This also occurs if you don't loot the mesos pretty soon after they drop - regardless of whether you've changed platforms or not. For example, if mesos drop out of your pet's range, or if you're walking to the left and the mesos have dropped to the right, the pet often won't loot the mesos when you go back to them, but it will loot the drops.
I think this is related to the 30~ish or so second timer from when you kill a monster and the loot belongs to you to when it becomes free to anyone who would pass by. I have no idea if it actually is 30 seconds, it just makes sense to me. What doesn't make sense is why it only happens with mesos and not items.
This glitch occurs whether you are solo or are in a party. If you don't move (i.e. attack from the same spot over and over), it will loot normally but if you are moving around the map (which is how most training is done) your pet will miss 90% of the meso-bag loots. This glitch is really under-reported since everyone is so used to it by this point, but it really is not a minor glitch. It kills immersion to see an obvious bug EVERY time you grind, and eventually players start missing out on serious meso (10k each bag). Also unlike the quest glitch, this pet glitch does not exist on many other pservers, only ones with our source. Pet pathing is really weird here, and there are many other working servers you could go on to see how they're really supposed to work. I would argue this is a major bug, moderate at the very least.
