AboveTheChemist

Relative to the data folder within the CoH install folder. For instance, my settitle keybinds are in C:\Games\CoH\data\badge_title My keybind for cycling through the bind files is 'bind_load_file badge_title/<file_name>' And just to be clear that is for my personal settitle files that I developed, not the files associated with your application, but I think the concept should be applicable there as well. I point this out because I don't want to give the impression that I modified the application files to use relative paths. So if you decide to use relative paths in the application files, I'd certainly test them to make sure they work. And if you decide not to go that route, no worries, I just wanted to let you know it might be an option.

Yep, the length limit is 256 characters. Also, it is possible to use relative paths in keybinds so that might help avoid line length issues.

Feel free to do whatever you like with the data! The only excel file I have is in a slightly different format. It lists the recipes by individual level, whereas I compiled them according to level range by common sets of salvage components. But, as Heraclea demonstrated, it should be simple enough to take my text file and import it into excel (or just use the file Heraclea provided), as the columns are delimited with semicolons. One other thing to note is that the enhancement names aren't always the same as the recipe names. I also compiled a mapping of recipe name to enhancement name if that would be useful.

No worries, I appreciate that you are giving the badges a thorough checking!

TheWino is correct, you can definitely do this. My bind for Ice Slick is: CTRL+LBUTTON "powexec_name Ice Slick" I hold control and wherever I click my left mouse button (with the power's range, of course), it puts down an ice slick. I have used a macro like this for location AoE powers for many months and never had issues. Targeted and point blank AoE's should be able to be activated the same way, although with targeted AoEs you may need to mind where you click so you don't unintentionally click off the target mob. Edit: See Vulpoid's post immediately below, I was not aware that powexec_location was a thing and that command should take care of targeted and point blank AoEs nicely (see p62 of the consolidated i25 patch notes for more info).

Is that badge earn-able by a villain? The wiki info leads me to believe it is only earn-able by heroes (the usual caveats about the reliability of wiki data notwithstanding). If you earned it as a villain, do you mind sharing how? This is another alignment-related issue that I am hesitant to change.

I tested as well and concur! EDIT: I updated the file in my post above (again) because I forgot to change the badge tags down in the alphabetical section. All the Echo: Faultline and Faultline badges should have the correct tag now.

Updated the file in the OP again to account for the new IO sets introduced in i26p5. Those recipes are still on the beta test server but hopefully the recipes themselves won't change. Edit: I don't think the recipes have changed but the names have changed a couple of times, plus another set was added, so I am going to hold off any more updates until those sets go to the live servers.

Thanks for bringing this up! I did a deep dive into the badges for Faultline and Echo: Faultline and found a lot of issues there (understandably, given how the badges were shuffled around and new badges added). I think I have them sorted out but I need to test them first. Here is how I currently have them mapped: I have no idea if that mapping is correct without testing, so it's entirely possible I just made things worse. Usually the badges are listed in order in the .def file though so I just followed the order I saw there. That, plus I am reasonably confident that the mapping of the original Faultline exploration badges hasn't changed. I updated the menu in my post just above. If anyone else wants to test independently and report back I would welcome that. I am going to try to test them tonight if I can.

Here are a couple of examples I found while gathering some data on the new enhancements on the test server.

I've update the OP with the revised dataset from the leaked game files. A few notes on the updated dataset (behind spoiler tags to avoid a wall of text):

I submitted the fix for this, thanks! Regarding your previous post about the alignment of those badges, I'd like to hear from @KeyboardKitsunebefore submitting anything for those. If I recall, when we were working on the badge data we had some (possibly brief) discussions about what to do about the alignment of some badges, since HC did some blurring of the lines between hero and villain in terms of who could earn which badges. The evidence you presented above does lead me to think that the 'V' option could be removed from those badges but it's been so long that I honestly can't remember what was decided and I am a little hesitant to submit fixes just yet.

I've been able to acquire the recipe data from the leaked game files via OuroDev, and am in the process of verifying the dataset. I have found some discrepancies, so in the event that anyone has started using the data, just be aware of that fact, and I'll post an updated version as soon as I can.

Submitted a fix for this one as well, thanks again!

I didn't make it, I just helped with some of the data and with some of the maintenance. Hope you got your menu fixed!

Looks like a case where the HC devs decided to use a different icon for that, compared to what shows up on ParagonWiki and/or City Info Tracker. I submitted this for a fix, thanks for pointing it out!

Yep I noted that in the spoilered section under 'A few other items of note' (3rd bullet).

If you are looking in Ouro, mission 1.17 in the level 50 range will do the trick.

You're in the wrong thread, this is the one you need: There are newer versions/variations of that menu (including one I made) that should have that already fixed.

Can you post a screenshot please? I cannot find this typo anywhere on the Badger site (or the spreadsheet).

I was able to put this together (and do some very limited testing in my parser) quicker than I expected. Tagging @seebsto make sure they see this.

This is a dataset I've wanted for a while, but only recently found a reasonable means of piecing it together. Attached is a semicolon-delimited text file that contains, for each level range within each recipe, the component salvage required to craft the recipe. The file is structured as follows: First column: Recipe name as it appears in-game, so it can be matched via log files, and without the '(Recipe)' tag (because not all recipes contain that tag). Second column: Minimum level for the applicable level range. Third column: Maximum level for the applicable level range Fourth through eighth columns: Names of the individual salvage components, with a max of five components. Recipes with fewer than five components will contain blanks in the trailing columns. Components that are used more than once in a recipe will appear the appropriate amount of times in separate columns. Note that as of 21-Feb-2020 the in-game name for Encouraged Accuracy: To Hit Buff shows up as 'Family_Boss_Defense'. In this dataset it is listed as Encouraged Accuracy: To Hit Buff, and attempting to match it with game logs will cause issues until the devs can correct that typo. This dataset won't be immediately useful to anyone without coding some means of using it, but feel free to use it for whatever purposes you wish. All I ask is that I be acknowledged for providing the dataset. The data was parsed from the leaked game data files (obtained via OuroDev) and should be highly accurate, but may or may not be 100% accurate. The exceptions to that are the components for the Sudden Acceleration and Experienced Marksman IOs, the five IOs introduced in i26p5, and the five IOs introduced in i27p3. I transcribed the salvage data for those recipes directly from the game (via screenshots) because those IOs were not in the game data. NOTE: The previously posted version was sourced from the wiki, and this updated version corrects many errors found in that data. I have incorporated this dataset into my personal parser and it worked great for the 25 or so recipes I had on hand to test with. I will of course continue to test as I acquire more recipes, but considering there are approximately 1,750 recipe/level range combinations, complete testing won't happen any time soon. To that end, if anyone notices any errors or omissions, please let me know and I will verify and update the dataset accordingly. I can also supply a pickle file (upon request) for any Python users who would like the data in that format. recipe_salvage_data.txt

Here's my final version of my previous screenshot. I adjusted the view a bit to even it up, moved the characters as close to the center as I could reasonably get them, adjusted their spacing, and adjusted their yaw so they were looking towards the camera. This took multiple iterations to get everything looking right, but I think it turned out fine. I've attached the demo file if anyone wants to plunk their characters in. Here's the lineup (spoilered) if you want to know who is where in the screenshot, so you'll know which ones are where to replace with your characters: If your characters are vastly different in size, you'll probably need to adjust positioning a bit. ouro_lineup.cohdemo

I'm a bit late, but I couldn't find any leads in the pigg files. I had a revelation today for a way to get most of this data off the wiki, so I am pursuing that angle. I'll post again if/when I am able to put together a meaningful dataset, hopefully within the next week or two.

Odd, it shows up fine for me.