Ideas for data to track with graphs.

[PatrickDattilio]

Average clear time per level Average time to specific upgrades/places (first warpstation/break the planet) Average helium per hour every X seconds/per level

Ideally we could graph some of this data so we can pinpoint the best point to portal?

[WG-SpaceCoder]

This was one of my secret features :D shhh don't tell anyone haha.

[weltvagabund]

I ran a build a while ago from @spindrjr were it was enabled. I really liked the Graphics. It made me better guess when to Portal. Is there a chance that it is coming any time soon?

[spindrjr]

Graphs was zin's thing. Think he's about done with this project but I have enabled it in the master build. It will build up quite a lot of portals so you can type the following into the console to clear some older ones. Change 272 to whatever portal number. This will clear all the runs below the number you type in (the number typed is saved).

while(allSaveData[0].totalPortals < 272) allSaveData.shift()

[spindrjr]

I have a better grasp on the graphs code now so I can probably implement most things. So anyone feel free to leave suggestions here.

[weltvagabund]

New Idea: Diagram of actual Heirloom Drops. Either Bars or a Pie. So that I can see in my last runs, that I had for example 3 Common, 2 Epic and one Etheral (including actual percentages) I would find it interesting, how the actual drop rates are. In theory they should narrow down to the ones in the wiki, but it would be general a nice thing. Maybe this information could be also integrated in the void maps run in the existing graphs.

[spindrjr]

I like this idea but I was so far unable to think of an elegant way to track it. I'll ponder on it though.

[Sciencefreak]

No idea about additional data, but a few improvements which might be easy to implement.

1. Save which runs are displayed. 10 are sometimes to much and I only want to compare my current run with previous one, but I have to disable the other 8 runs every time I open graph window (add a toggle all would be a way as well)
2. Add an option for a log scale, because clearing time ranges over several orders of magnitude (less than 1min for first zones up to several hours for deeper runs). This way one can see which run was faster without zooming into different locations

3. Option to plot total time needed to zone x, because it is more important to minimize time for clearing all zones until x instead of clearing zone x only. Together with point 4 it will help to find optimal perk settings to finish zone x as fast as possible. (without point 4 I have to remember/save myself)

   To be honest, I got two ideas for new data as well.

4. Add current perks to run info (currently only challenge name is displayed, maybe a mousover which displays perk lvls in a similar way as the perk window itself)
5. Time spent on maps vs time spent in zones. This will help to see where map farming slows down progress to much. This might help to tweak automaps settings for speed runs.

[tomrippity]

Population?

[jheard]

Would it be possible to get a helium per hour graph where the horizontal axis is actually time? This would be a more accurate representation of the statistic. Maybe instead of indexing on the zone number, since you are already tracking the clear time per zone, add that up and index the data by that instead?