• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
MQ2Log

Release MQ2Log

Overview Updates (5) Discussion
Sym

Sym

Creator
Joined
Sep 20, 2005
RedCents
1,793¢
Plugin writes all mq2 output to logs/servername_charname.log. It will create the logs folder if you not have one. Command toggle is

Rich (BB code): 
/mlog on|off

Saves setting in ini under MQ2Log in servername_charname.ini

No longer has crashing issues during my testing. Any issues let me know.
 
Sym - love the plugin.

I have a few feature requests. -

1. Ability to specify which directory you want it to log to.
2. Ability to log specific chat channels, tells, etc. IE turn on only logging 'tells' or logging 'says' and 'tells'.

Right now I am logging everything and grep'ing the information that is useful for me. I would love to be able to save to a web writeable directory so I can check my feeds from wherever I am even through my phone. I don't really like to have my mq2 directory accessed through my webserver.
 
1. It uses whatever the log folder is set to in your macroquest2.ini file. Change that to the folder you want and it should use that. I don't set it specifically, just whatever mq2 reports as the log folder.

2. I'll look into that, that could be useful.
 
MQ2Log - Plugin writes all mq2 chat window output to your MQ2 folder /logs/servername_charname.log.

It will create the logs folder if you not have one. Command toggle is
Rich (BB code): 
/mlog on|off
Saves toggle setting to log file under servername_charname.log
Rich (BB code): 
[MQ2Log]
Enabled=1
 
when i type " \mlog on" it responds "cant parse mlog " and such thinng as mq2events arent working since there are no logs being created.
 
Is there a property to tell if /mlog on? I don't want to stomp on it if it's on and inadvertantly change the log file. I see it writes an INI file, do I need to read that?
 
I guess you could technically read the INI however.

INI: 
[MQ2Log]
Enabled=1

so I guess something like


/echo ${Ini[..\\${EverQuest.Server}_${Me.Name}.ini,MQ2Log,Enabled,0]}
would get you if it's on or off. Where the "0" is the default if no INI entry is found. If you don't provide the default, the result would return NULL, which is just as good as a false as far as mq2 would be concerned
 
Updated the Overview to reflect the ServerName_CharacterName.ini instead of .log, and specified that it was located in the root MQ2 directory. I did have to verify the file location because the information was incorrect slightly which is why it took me a few minutes to make the suggestion.
 
for some reason, one of my two bards didnt record anything yesterday other than a run over overseer. Did two raids and xp'd for a couple hours.
 
You must log in or register to reply here.
Release MQ2Log
Next unread thread 🦁

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top
Cart

Cart

Total -