For quick questions, discussions or other conversation that isn't an issue feel free to join an open discord channel: https://discord.gg/dCDEPXx
Our GitHub Page: https://baaron4.github.io/GW2-Elite-Insights-Parser/
-
Go to Code tab
-
Go to Release section
-
Download the GW2EI.zip file
-
Extract all files anywhere you like
-
Open GW2EI.exe (feel free to make a shortcut and move to desktop)
-
gg
NOTE: ArcDPS log files are currently located within "C:\Users<USERNAME>\Documents\Guild Wars 2\addons\arcdps\arcdps.cbtlogs"
-
Drag and drop 1 or multiple .evtc, .evtc.zip or .zevtc files into program
-
Click parse
-
When done the .html will be located in the same location as the evtc, or at the desired output location, as "samename_boss_result.html"
If you would like to have your logs parsed without the GUI pass the file location of each evtc file as a string.
Settings can be configured using .conf files (see Settings/sample.conf for an example). You can then use it with -c:
GuildWars2EliteInsights.exe -c [config path] [logs]
To disable windows-specific commandline magic you can use -p:
GuildWars2EliteInsights.exe -p [logs]
You can start the application in GUI mode using -ui option:
GuildWars2EliteInsights.exe -c [config path] -ui [logs]
Note it may take some time for each file to parse and they will not be ready to open the moment they are created.
-SaveAtOut: if true, the generated files will be in the same location as the source file.
-OutLocation: secondary output path, will be used if SaveAtOut is false.
-Anonymous: if true, player character and account names will be obfuscated.
-AddPoVProf: if true, the profession of the pov will be added to the generated files' name.
-AddDuration: if true, the duration (truncated to seconds) will be added to the generated files' name.
-MultiThreaded: if true, multiple threads will be used for parsing a single log.
-ParseMultipleLogs: if true, multiple logs will be parsed in parallel.
-SaveOutTrace: if true, log files will be generated.
-SkipFailedTries: if true, failed encounters will not be parsed.
-AutoAdd: if true, EI will automatically add logs that appear in AutoAddPath.
-AutoAddPath: the path to listen to for automatic additions.
-AutoParse: if true, every added log file will be automatically processed.
-ParsePhases: if true, phases will be parsed.
-ParseCombatReplay: if true, combat replay will be computed.
-ComputeDamageModifiers: if true, damage modifiers will be computed ( forcefully disabled on WvW logs for now).
-SaveOutHTML: if true, html logs will be generated.
-HtmlExternalScripts: if true, css and js files will be separated from the html.
-LightTheme: if true, the html will use a light theme by default. Please note that the theme can be dynamically changed on the html post generation.
-SaveOutCSV: if true, csv logs will be generated.
-SaveOutJSON: if true, json logs will be generated.
-IndentJSON: if true, generated json logs will be indented instead of being on a single line.
-SaveOutXML: if true, xml logs will be generated.
-IndentXML: if true, generated xml logs will be indented instead of being on a single line.
-CompressRaw: if true, xml and json logs will be compressed.
-RawTimelineArrays: if true, xml and json logs will contain graph related data.
-UploadToDPSReports: if true, the log will be uploaded to dps.reports using EI as generator.
-DPSReportUserToken: dps.report user token.
-UploadToDPSReportsRH: if true, the log will be uploaded to dps.reports using RH as generator.
-UploadToRaidar: if true, the log will be uploaded to raidar (not used).
-WebhookURL: Webhook URL to send an embed or simple message to.
-SendEmbedToWebhook: if true, the Webhook URL will receive a small embed containing meta data + dps.reports link. (Does not work with ParseMultipleLogs for now)
-SendSimpleMessageToWebhook: if true, only the dps.reports link will be sent to the webhook.
The Json documentation can be found here
- baaron4
- EliphasNUIT
- cordbleibaum
- QuiCM
- amgine
- Linus
- Sejsel
- Flomix
- Stonos
- Hobinjk
- Linus (arena maps/ icons for combat replay)