Updated to 1.7.* with vanilla files verified via DiffMerge.
- Obviously full testing would require personal time and play through with Friends & Foes, but judging from the patch notes, marketing materials, and DiffMerge I am not anticipating any issues.

- Updated to be compatible with 1.6.1.2
- Vigilance Tradition's Coming of Age artifact shield has been buffed.
- Several Traditions with intangible Coming of Age "gifts" have been buffed. Duty, Guile, and Fortune receive a bonus perk in Martial, Intrigue, and Stewardship respectively to reflect the young adult experience indicated by the event text.

- Updated to work with v1.6.*
- Updated Dynasty Legacy preferences by tradition to work with Royal Court and Fate of Iberia Legacies.

Updated all appropriate "Gift of <tradition>" modifiers to the artifact system. Note that not every tradition receives an artifact, only those that were obviously referencing to a tangible item in the original modifier/event.

Aside from the wool shirt hand-knitted by a Compassion tradition parent, all are common items as they are meant to be commissioned from a local artisan. A talented compassion parent may produce a masterwork wool shirt.

I tried to integrate with vanilla items to make it consistent, immersive, and seamless, so some items such as swords and armor are generated via vanilla code which has some limitations on controlling the artifact's history. (For these items, it will just show the parent as the "creator" rather than an unknown benefactor/random artisan) it's limitation of the code that's hopefully not too jarring.

Most of these items are set to 30/60 durability on purpose. The intention is twofold: 1) To limit clutter from all NPC's having these items (majority NPC's will not have the gold to repair it, and will allow the item to be destroyed before getting it inherited) 2) Give players the option to repair and keep these very personalized items for their own roleplaying reasons.

Only non-blacksheep children with at least one living parent/grandparent of the appropriate tradition will receive the gift at age 15. Blacksheeps have a chance to "straighten up" to receive it.

Orphaned children will get a "Resolve: <tradition>" modifier instead just like before.

Cleaned up more error logs. Please note that there currently exists a CTD from the base game that has nothing to do with this mod. That crash can be overcome by simply relaunching the game.

As for the error log spam, most of the "errors" have no impact in the game and are along the lines of "Hey this noble character doesn't have a father, are you sure your event should be checking for a father?" The game is smart enough to just ignore the effect if the character has no parents. I cleaned out most of it but there's still some I'm not able to figure out how to get rid of without being exceedingly verbose in the code such as the constant checks for "bad_mother" (many fresh games have nobles with children but no spouse). I may not work on this part further since it doesn't have impact in the game and my goal in cutting down the error log is to find real issues.

1.5 also added a lot more error logging warnings about "hey this modifier is usually used for a character and not as a house modifier" - I'm pretty sure it still works regardless prior to 1.5 when I diligently tested each and every tradition. Please let me know if 1.5 outright banned some modifiers from being used as a house modifier (which would be really poor decision making by PDX if that happened) If it works, then it works. I can't do anything about PDX decision to keep the error log spammy.

- Disabled a non-essential file since it may be causing some people to crash. Strange, this file was not touched in a very long time and if it causes crashes it should have happened since day one of 1.5 release.

Error logs should be dramatically cut down. "Find Spouse" should also be faster across the board. It turns out that the game was attempting to make checks against lowborn characters who don't have a "House" to check for traditions to begin with that required tons of "hole plugging" to to tell it to stop doing that.

I'm aware that there's still some such error logs (such as bad parent checks which lowborns generally don't have) but at this time I'm not sure how to tell the game to stop checking for lowborns in the context the code is implemented.

- Pushed an update to initialize some global variables on_game_start to hopefully reduce the error log spam some people are seeing. I'm not seeing the issue on my end, though, and I'm unsure why the way I've set it up could produce error messages more than once, if any at all, as I've set them up to acknowledge a default state (as older saves obviously wont have them. Please let me know if there are any issues as this is somewhat of a "blind fix".