Read this if your BatMUD game client is eating a lot of memory

[Axu]

We have Today confirmed that there indeed is a memory leak in the debug-mode for player created triggers. The debug-mode is not enabled 'by default' when you install the game on Steam, so any new users should be all good.

However, it appears that either some players developing a set of triggers or the game client itself may have at some point had a related debugging mode (debug="true") turned on.

If your game client is eating 'a lot of memory' (read: e.g. 1GB to 20GB) and you're using a trigger set distributed by other players, there's a good chance that the following will help your gaming experience immensely:

1. Shut down your running game client instance
   
   
2. Open \batclient\conf\triggers.xml with your favourite editor (notepad.exe is fine)
   
   The first 3 lines of triggers.xml should look something like this:
   

   <?xml version="1.0" encoding="ISO-8859-1"?>
   <Triggers>
     <TriggerManagerSettings onlyVisibleWindows="false" debug="true" /
   

   
   
3. Edit debug="true" to be "false" instead, resulting in:
   

   <?xml version="1.0" encoding="ISO-8859-1"?>
   <Triggers>
     <TriggerManagerSettings onlyVisibleWindows="false" debug="false" />
   

   
   
4. Save & Start game client again

We will address the issue (change the client code appropriately) in a future release as well.