LootNanny - Beta - 0.0.7
Pre-releaseTaken a little bit of a break from mayhem to bring you an updated version of LootNanny:
v0.0.7
- Shrapnel should now be counted correctly (fixed off by ~0.1% error)
- Mindforce misses are now counted
- Significant overhaul to how config is stored and read. Should have a lot fewer issues on startup/saving config.
- Added Markup to Item Table, you can now set an individual items markup which is reflected in the current runs total return.
- Total cost field now persists and allows you to add extra expenses, such as for a fap or armour decay.
- Added notes column so you can track information about what the run was for. I.e. What mob you killed or where you were hunting.
- Expended skill table to contain 40 entries.
- Added weapon load-outs, where you can add multiple types of weapons and easily switch between them.
- Added three new streamer overlay metrics: PERCENTAGE_RETURN_MU, TT_RETURN and TT_PROFIT. PROFIT and TOTAL_RETURN now include markup.
- Should now screenshot your crafting and mining globals
- Should now respect the configuration options for screenshotting and screenshot location.
Markup
Markup will need to be manually maintained by each person on this update: The application exposes a file called markup.json
in your %appdata%\Local\EULogger\ folder.
Its contents look like this:
{
"Shrapnel": ["1.01", false],
"[Empty Skill Implant (L)]": ["12", false]
}
Each item in the JSON object has two fields in an array. The first is the markup expressed as a decimal value, the second being a boolean to determine if the markup is absolute or not.
false is for stackable items, such as shrapnel and oils. A markup of 101% would be added as "1.01".
true is for items with a fixed markup, such as armour or weapons. A markup of +3500 would be added as "3500"
{
"Shrapnel": ["1.01", false],
"[Empty Skill Implant (L)]": ["12", false],
"Shadow Helmet (F)": ["3500", true],
}
These values can also be added directly in the App's Loot window also by double-clicking on a particular items markup column and entering the value itself. For absolute values being added in the UI, you can prefix the value with a '+' such as '+3500' which will set a per item markup instead of a relative % markup.