[SIZE=+6]LogMark v1.0.2[/SIZE] [SIZE=+6]by Bobby53, for use with Honorbuddy [/SIZE] [SIZE=+1][ What Is LogMark? ] [/SIZE] [SIZE=+1]A light weight plug-in that adds a line to the log file (and log window) indicating LOGMARK # when you press any two (2) modifier keys ( SHIFT, ALT, or CTRL) from within WOW. [/SIZE][SIZE=+1][ Why Use Mark? ] [/SIZE] [SIZE=+1]It GREATLY simplifies marking a spot in the HonorBuddy Log file where you saw a behavior occur that you want to post in forums about. Authors of CCs, BotBases, and Plug-ins and other HonorBuddy components always require you to provide a log file for any issue you are reporting. Additionally, they want to know the local system time (on your computer) when the problem occurred, so they can correlate the symptoms you describe to that specific portion of the log file. LogMark will add a line to the log file (and log window) marking the point where you recognize the problem. This means when you recognize a problem you no longer have to check the system time and save it for later when you post the issue in the authors forum. You can now just remember it occurred at LogMark ### and mention that in the post you attach the log file to. This eliminates the need for keeping a clock showing the current time (with seconds) visible and actively saving it off somewhere while you are botting.[/SIZE] [SIZE=+1] [/SIZE] [SIZE=+1][SIZE=+1][ Feature Overview ] [/SIZE] [/SIZE][SIZE=+1]Monitors WOW for modifier keys being pressed. When you press two (2) or more at the same time it will immediately write a [LOGMARK] message including a Mark # to the HonorBuddy .LOG file so you can easily reference that occurrence within your post. Here is an excerpt of what you could expect: [/SIZE]... (log output from bot and cc) ... ... (log output from bot and cc) ... ... (log output from bot and cc) ... [LOGMARK] Mark # 1 added to logfile ... (log output from bot and cc) ... ... (log output from bot and cc) ... ... (log output from bot and cc) ... [LOGMARK] Mark # 2 added to logfile ... (log output from bot and cc) ... [SIZE=+1] Note that WOW needs to be the active window for the keys to be recognized. [/SIZE] [SIZE=+1][ Installation ] [/SIZE] [SIZE=+1]Extract the .ZIP attached to this post to the Bots folder of your HonorBuddy installation. The successful installation will match: [/SIZE][SIZE=+1]Folder: [/SIZE][SIZE=+1]HonorBuddy\Plugins\LogMark[/SIZE] [SIZE=+1]Contents: [/SIZE][SIZE=+1]LogMark.cs[/SIZE] [SIZE=+1][SIZE=+1][ Donations ] [/SIZE] I support the solicitation of donations by other Developers and Profile Authors. It takes countless hours to create and adequately support something of the complexity of anything but the most trivial HB components and you can acknowledge them by a small monetary donation. This particular project is simply a pastime or hobby for me personally, so no donations are permitted. You can show your support in the following ways: Click the star at the bottom of this post and give +rep to this project [SIZE=+1]When posting issues provide clear detailed descriptions with full debug logs [/SIZE]attached. The time you save me by providing this is more valuable to me than monetary contributions. [SIZE=+1][ Notices ] [/SIZE] 1. Read my posts and documentation on the forum before posting a question. 2. I will try to respond to your posts quickly, but I do this in my spare time. If you don?t get a response, see #1 above. 3. Disclaimer: Use of 3rd party programs are against Blizzard's terms of use and license. This Bot is not intended for use on live Blizzard Entertainment World of Warcraft realms. Any use on Blizzard realms is at your own risk and not supported per this statement. o READ THIS POST BEFORE DOWNLOADING[/SIZE]
Note: the new release is updated to work with the latest version of HonorBuddy. Additionally it fixes the problem where multiple LOGMARK entries were written to the log when 3 modifier keys were pushed.
Note: If you are using Singular, there is now a LOGMARK! button in the Class Config form that provides the same functionallity (no key mapping tho.) See the Singular thread for details.
