This addon contains a collection of tools for getting data from Elder Scrolls Online.
It's a combination of in-game addon modules, external scripts, and some HTML for viewing the data

# Warnings
This is not an easy setup. I've made it as easy as possible, but there are a lot of moving parts.
Furthermore, you still have to do a lot of the work afterwords.

This addon can use a lot of lua memory to export data, depending on how many items you use.
Consider disabling other addons when running. As well, you'll want to delete/move the saved
variables for this when you're done.

Your game may appear to freeze while doing some of the commands. This is normal.
A lot of the commands involve a lot of processing, and it's not really a priority to make the
game run smoothly during them.

Checking the set data will bind unbound gear in your bags.

# Installation
1. Install the addon in-game (place in folder).
   Note: You can place all the files in the addon directory just fine.
2. Install Wykkyd's Outfitter (required for skill curve module)
3. Install R (
4. Install Rserve. Within the R cli, type the following command:
NOTE: Stand-alone Rserve can be used if desired for most functionality

5. Install Scilua + LuaJIT
  a) Follow the directions on
  b) Make sure to get the main Xsys library and the Rclient library.

# Usage
## Addon in-game

There are several different modules in-game. They're accessesd by slash commands and self-documenting.
Type `/quant` in the chat box to see a list of commands and a brief description.

### Major modules:
* Champion system -- (`cs` and `cs-desc`) dumping champion system per-point data and descriptions
* Stats dump -- Exports character current character stats
* Skill dump -- Exports description and details about skills
* Skill curve -- See below. Requires extensive setup
* Sets dump -- Exports a dump of all set info
* Power register -- crude dumping of stamina/magicka changes to chatbox

### Skill Curve module
This module iterates through gear combinations recording tooltip data. It's decently automated, but
does require some setup. This is best done on PTS.

1. Use a base VR14 character (no attributes, skill points, or champion points).
2. Prepare gear sets: health, magicka, and stamina enchants. Try to keep set bonuses neutral.
3. Prepare 6-12 bows of different power (Level 1 to VR14 gold).
4. Have all gear sets and bows in inventory. Don't put anything else in inventory.
If you have unbound gear items, this command WILL bind them to your character.
Alt+F4 or /reloadui to stop this running
5. Run /quant itr-all-skills
6. Wait 3-6 minutes. It takes awhile
7. Reload UI or logout to make sure data is saved.
8. Repeat for other classes. Can just do /quant skills for this

## External Lua

Several commands write out to the game's `SavedVariables`. A few of the scripts are designed to extract
the data from the `SavedVariables` file and process it.

First you need to setup the `cfg.lua` in the root directory. If you don't, the scripts won't find your
saved variables.

To access, run the `runScripts.lua` file in the base directory. Files will be output in that same directory.
There's a brief summary, buts see the individual scripts for more details.

Under the HTML directory, there's HTML for displaying. After exporting the data to JSON, move the JSON into the
same folder as the HTML. You can then open the HTML in Firefox.

Note: Unless you actually host it on a site (or some complicated workarounds), Chrome will not load local

This is currently hosted on

# Cleanup
Delete `Quant.lua` from your SavedVariables directory when you are done with it.
Also feel free to contact me if you want to include a module.

# Extending Quant
This is fairly modular so can be easily extended. You can use/extend however (under the GPL).

* See `modules/Template.lua` for a documented example of the framework.
* After adding a module, include its path in `Quant.txt` at the end.

External Lua
* There are several convenience functions under `scripts/inc` to help out
* Consider adding to the `runScript.lua` to make it easier to access

* It should be straightforward. Data is primarily output as JSON here.

# Changelog
0.5 - Add HTML to initial release. Cleanup modules
0.4 - Add sets, initialize Git
0.3 - Begin limited release to Mostly Harmless and Wagonborn
0.2 - Personal use (Skill iteration)
0.1 - Personal use (Champ System)