Event logging addon for 3.3.5a, suitable for boss encounters. Integrates with both DBM and BigWigs backports.
- DBM backport: https://github.com/Zidras/DBM-Icecrown/
- BigWigs backport: https://github.com/bkader/BigWigs-WoTLK
- For DBM backport 9.2.20 or above (https://github.com/Zidras/DBM-Warmane), write
/dbm debuglevel 3in chat to enable DBM debug messages. Doing that in conjunction with Transcriptor logs all DBM debug messages too. This step only needs to be done once (per DBM profile). - With DBM: To ensure you don't forget to log the fight that you're interested in, you can automate Transcriptor logging on Options > Extra Features. (example: only log bosses https://i.imgur.com/QkagiPQ.png)
Otherwise, you can manually write /ts in chat at the start of the pull. You can also click the minimap icon (it will turn from dark red to bright red, meaning it's currently logging). This will start one log entry.
- If the log was manually started with
/ts, then write/tsagain in chat at the end of the fight to finish the log entry. You can also click the minimap icon (bright red -> dark red = idle). - For readability purposes, a log entry should only have 1 boss. DBM aumotation from step 2 will ensure this, but if you manually start the log, make sure you stop it at each boss/trash/roleplay... so that each section that you are logging has its own log entry.
- Reload by typing in chat
/reload, or logout normally, to save the log into your WTF > SavedVariables folder. DO NOT force close the client (ALT+F4, power outage, etc) before the log is saved or everything in memory is wiped and the log is lost!. This is very important! It is also crucial that you do not forget to start/stop the logs and reload frequently, otherwise you will be logging indefinitely and eventually crash if you run out of memory. Logging a full raid (although sommetimes necessary to also catch trash/roleplay/yells/etc) should be done cautiously by doing frequent reloads. Each system has different specs, so I cannot give you a timeline on when to reload. For reference, with a good PC I have successfully logged an entire ICC without stopping up to Sindragosa before, but my recommendation is to log the content you are interested in, including all bosses, and reload regularly (safest is after each log entry, but each 5-10 entries is also fine). - Go to your
WTF/Account/<name>/SavedVariables/Transcriptor.luato view the log. If TranscriptDB is empty, it means you didn't follow the steps properly and the log is blank. Example of a blank log:
- A good practice is to backup the
Transcriptor.luasomewhere else after the log is saved in step 5 (for example: copy and paste in a different folder). This prevents potential loss of previous logs if TranscriptDB gets corrupted on a force close.
Here is a short clip with all the steps combined on how to quickly generate a log:
Wow_pVIjMFMEut.mp4
- Download the addon from the main repository (https://github.com/Zidras/Transcriptor-WOTLK/archive/refs/heads/main.zip).
- Inside the zip file, open Transcriptor-WOTLK-main and copy (Ctrl+C) Transcriptor folder over to your addons folder (Interface/Addons).
