Contract grouping with live tiles was a good idea and is now available in 1.2, but it took way longer than I wanted to implement. I think I will have to take a break after this big update!
I decided against forcing it for all escalations, so the content pack needs to explicitly request it. I updated the unofficial pack to do so for the escalations with more than one level.
I also added an option to merge elusives into each sublocation, but you can of course keep using your approach as well. See readme for details.
Just got a chance to test it and it works great. Though you said it took longer than expected, you still managed to get it done within a day! I think this currently looks as good as it can, if you have personal preferences as to order its easy to make edits yourself. Enjoy your well earned break.
Knowing now that this is possible, another cool idea but probably even greater pain to implement is to have livetiles for items. Then you'd reduce the amount of clutter due to the variations of mks and reskins. I'd be willing to help wit the the grouping of the items if you're eventually up to it.
Understandable. On a different note, I was trying to install some modded missions from a pack through the framework and I got an error for like half of them. I moved the scoring folders so that only that content pack would be applied.
I couldn't really identify which lines were causing the issue based on the prompt but after testing I narrowed it down to the objectives section. Maybe getting these to work is more tricky because they are less traditional than other missions?
https://www.nexusmods.com/hitman3/mods/38
The ones that wont import are:
Sniper Assassin Hawkeaido
Target Run
Target Streak Miami
Time Trial New York
The framework requires all json files to be valid, while the game seems to tolerate some minor errors. This has nothing to do with the complexity of a contract.
As displayed in the error, the issue is a wrong character following a '\' character in line 172 of a json file. From the rest of the error, it can be derived that the json file in question is a contract file, so the culipit is in the contracts subfolder.
As you see, the framework just prints errors that occur without giving you the filename, so it could be any contract. Try isolating each one to see which one fails, or edit __init__.py by adding print(contract_definition) before line 121 and look at the last filename above the error.
I will try to remember to add support for displaying the filename when such errors occur in future versions. No promises though!
