Getting Started With Rift Logs
Welcome to Rift Logs! This page will help you get familiarized with the Web site and all of its features. You will need an account to upload logs to the site, so if you plan on uploading logs, first create an account. You do need a valid e-mail address, since we verify it via an activation e-mail.
What is a Combat Log?
A combat log is a file created by the game that contains a series of events. These events contain information such as what abilities your team used, what damage they did and to whom, and what healing was received.
The idea behind combat logging is pretty simple: record what happened so that it can be sent to Web site for analysis.
Enabling Combat Logging
The first step is to get combat logging turned on such that the combat log file is getting written to disk.
Although Rift has a combat log file, it is missing features that Rift Logs needs, so Rift Logs generates its own combat log using a combination of an in-game add-on and a client application. You can read more about installing the uploader and add-on here.
The add-on, called RiftLogger, can be obtained from Curse. Once you have it installed in-game, you can access its command list by typing /rlog. Below is a brief description of the add-on's commands.
- /rlog on - The add-on will begin collecting combat events in memory. By default it will not dump these events to a log file, but will wait until you explicitly dump the events using /rlog save.
- /rlog off - The add-on will stop collecting events.
- /rlog toggle - Shortcut for toggling on and off.
- /rlog instant - When this mode is set, the add-on will write events to the file as they happen. This can be quite CPU-intensive, so this mode is not recommended for large raids.
- /rlog status - Will tell you how many events the add-on is holding in memory. It is very important that you save periodically throughout your raid night, or the add-on will eventually consume so much memory that you'll see a performance slowdown.
- /rlog save - Flushes all current events to the file. You will see a message in yellow text that indicates when all the events have finished.
- /rlog clear - Discard all events in memory without logging them to the file.
The way the add-on works is it writes events to your General chat tab, and if you turn on non-combat logging via /log then those events will be written to the non-combat log file. Always make sure that non-combat logging is enabled via /log before you let RiftLogger write any events, or you will lose them!
In order to upload logs to the Web site, you use a client application. This application can be obtained here. If you have any issues getting the application to launch or install, we encourage you to go to the forums for assistance, since it's likely someone else has encountered the same issue and can help.
Two Kinds of Logging
There are two ways you can choose to log. The first is to upload the entire log file after your raid is over. The second way is to do what we call live logging. In this model, the client monitors the log file and whenever it sees new events tacked on to the end of the file, it sends those events up to the Web site. The live logging mode is great for when you want to study wipes right after they happened to see what went wrong.
Where Do Logs Go?
You have two choices for where to upload your logs. Every user on Rift Logs gets a personal log space just for them, so you can always upload your logs there without ever joining a guild.
The second option for log uploading is to upload your logs to your guild's area. When you do this, everyone in the guild will be able to see the logs. Think of it as a shared space for official raids by your guild.
Before you can upload logs to a guild, you must first join the guild. If the guild does not exist, you can also create a guild.