MacroQuest64

Hi all,

I'm a professional perl programmer, and I'm VERY glad to see the development of the MQ/Perl integration. Over the last few weeks, I've been developing a very involved automation program for a wizard. During the course of the devleopment of this project, I ended up re-writing events.pl to include a number of new features, including the use of hashes for the timer and chat hooks (speciffically to allow disablable but not deleted events,) and a few other things. I'm a professional Unix perl developer by trade, and I'm glad to see things moving in this direction - there will be some MUCH more powerful bots out there in the near future. =)

Anyways, I have run into a little problem that I can't quite nail down. It looks like a memory leak, but I can't identify or trap it in my code. What happens is after a number of tells via the chat event (around 100 from the best I can tell, not an excessive amount and well within perl's addressing capabilities) that instance of MQ seems to crash the game. Sometimes I get the standard XP crash message, other times the game just hangs. I'm going back through and writing some more code to check the status of my timer and chat hashes, but I'm pretty sure it's something to do with MQ. One thing to note is this does NOT happen when I periodically do /perl restart to reload the perl engine.

My question is this: Given that the old events.pl uses arrays, have there been any known issues with instability using that method? My code is (more or less) a backwards compatable version of events.pl, and I will be more than willing to share it once this problem has been solved. If anyone can shed some light on this, I would greatly appreciate it. I hate restarting my wizard whenever it crashes (about once an hour.) =\

-pooka

its great that you are willing to share what you've worked on and we look forward to that..

best thing to do is to join the IRC server and pm AMadMonk .. he doesnt idle in the #mq chatroom anymore, but i think he still responds to pms :)

Unfortunately amm doesn't seem to hang out on IRC any longer. He's been MIA now for about a month.

While talking to him though shortly before his disapearance, he seemed to indicate that he will no longer be progressing development on the perl release.

From what I got out of it, there are some memory leaks that would require a full re-write of perl's integration into MQ.

Unfortunately, it doesn't look like perlMQ will make it to a better state than it's currently in, unless someone else steps up to the plate.

-Phantal