Amended on Tue 18 Aug 2009 09:07 PM (UTC) by Davidchapman
Message
I originally had 4.33 installed with plugins for Aardwolf. I recently downloaded 4.4 and installed it to the same directory becuase 4.33 wasn't compatible with the map plugin.
I downloaded it from gammon.com, on the main download page.
Version 4.41 corrected an issue where under certain circumstances a trigger might send the client into a CPU loop. However that shouldn't apply if you aren't using triggers:
The only thing I can think of is I did try an ATCP plugin as well as a Mapper plugin, and had some trouble getting it to work. But like I said, I uninstalled mush and reinstalled without the plugins so even if they were causing the issue, they shouldn't be now right?
I play Achaea and I've never had this problem. Did you change any settings in particular for your Achaea world file, or write any triggers/aliases/timers/et cetera? I'd suggest creating a new blank world file and trying to connect, and see if the problem pops up again.
I've tried uninstalling and reinstalling several times, but after connecting to achaea, generally within 5 to 10 minutes, mushclient stops responding and cpu usage shoots up to 100 percent. Is there any way to trouble shoot this issue?
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.