- Joined
- Jan 14, 2007
- Messages
- 12
- Reaction score
- 0
- Points
- 0
Heyas. I've been using lavastorm MM for about 3 years now, off and on. And i've never had any problems till here lately. Let me explains what's been happening.
I have every plugin required plugged in, including: moveutils, exchange, melee, piggyzone (for fade), mmobugstools, mq2twist, and a few others, but those being the main ones required to run.
I use the lslooterfry and lsmainfry version of the mac included with the compile you guys send out each patch.
Now the problem:
Sometimes, when running the macro, 1 or 2 or all (except the leader of the mission) will have a problem once they zone out (and not loot). It spams something about clockwork weapon (not sure of exact name atm) could not be found.... Obviously because they are standing in lavastorm and not in the mission as the monster. Or it'll spam about the repair kit not being found (again cuz they are in lavastorm and not in the mission itself) They (the clients) will stand there, and that message will spam into the MQ2 Window. (i think this might be a problem resulting from exchange possibly?)
Also, randomly sometimes the looters won't loot the shard at end, and will spam the message [MQ2] ! Looting ! "There are no spawns matching: (0-100) any. They spam it about 20 times, till either a) they don't loot at all and continue spammin till mission closes, b) they actually manage to loot the chest and continue the mission as norm, or b) crash out completely and close.
All my buddies who use this macro have reported the same thing happening on their end. We've eliminated the following as reasons this could be happening:
1. Too many windows loaded. I ran 1 window, he ran 3, and friend ran 2... after about 3 missions, i got the error with clock work weapon not being found.
2. Macro being altered in any form. We're using the newer version of fry's release, with only the password changed, and we've also used older versions of the macro, with just the password changed. Same Result from both.
3. User Error. Typically this seems to be the reason for most issues, however we've used MQ2 since 02, and pretty used to the commands and abilities of the macros and plugins we use. However, i'm still not going to eliminate this as the problem We all have our oops once in a while, however when 4/4 people i hang with all get the same problem, and we all have about the same expertise with this i try to think it's not us.
I've used every bit of thought process i can put into this problem, to try and fix it myself, but i feel that now it's gone beyond what i can do. And i see the communities responses to ween out the error, or errors.
Sometimes the macro will run fine for days at a time, with no error, then just poop randomly. I've watched it a few times, and even seen it mess up, but it wasn't doing anything that it doesn't do normally. I know death in the mission tends to bug it up, and a quick /fade fixes it typically (like it targeting the chest to loot, it won't loot it if you die too much, it's like the chest is there, but just not lootable at all till a /fade is done.
Thanks ahead of time and look forward to your responses.
I have every plugin required plugged in, including: moveutils, exchange, melee, piggyzone (for fade), mmobugstools, mq2twist, and a few others, but those being the main ones required to run.
I use the lslooterfry and lsmainfry version of the mac included with the compile you guys send out each patch.
Now the problem:
Sometimes, when running the macro, 1 or 2 or all (except the leader of the mission) will have a problem once they zone out (and not loot). It spams something about clockwork weapon (not sure of exact name atm) could not be found.... Obviously because they are standing in lavastorm and not in the mission as the monster. Or it'll spam about the repair kit not being found (again cuz they are in lavastorm and not in the mission itself) They (the clients) will stand there, and that message will spam into the MQ2 Window. (i think this might be a problem resulting from exchange possibly?)
Also, randomly sometimes the looters won't loot the shard at end, and will spam the message [MQ2] ! Looting ! "There are no spawns matching: (0-100) any. They spam it about 20 times, till either a) they don't loot at all and continue spammin till mission closes, b) they actually manage to loot the chest and continue the mission as norm, or b) crash out completely and close.
All my buddies who use this macro have reported the same thing happening on their end. We've eliminated the following as reasons this could be happening:
1. Too many windows loaded. I ran 1 window, he ran 3, and friend ran 2... after about 3 missions, i got the error with clock work weapon not being found.
2. Macro being altered in any form. We're using the newer version of fry's release, with only the password changed, and we've also used older versions of the macro, with just the password changed. Same Result from both.
3. User Error. Typically this seems to be the reason for most issues, however we've used MQ2 since 02, and pretty used to the commands and abilities of the macros and plugins we use. However, i'm still not going to eliminate this as the problem We all have our oops once in a while, however when 4/4 people i hang with all get the same problem, and we all have about the same expertise with this i try to think it's not us.
I've used every bit of thought process i can put into this problem, to try and fix it myself, but i feel that now it's gone beyond what i can do. And i see the communities responses to ween out the error, or errors.
Sometimes the macro will run fine for days at a time, with no error, then just poop randomly. I've watched it a few times, and even seen it mess up, but it wasn't doing anything that it doesn't do normally. I know death in the mission tends to bug it up, and a quick /fade fixes it typically (like it targeting the chest to loot, it won't loot it if you die too much, it's like the chest is there, but just not lootable at all till a /fade is done.
Thanks ahead of time and look forward to your responses.