* Make weapon key series an array Draconic Weapons Providence can have original Draconic Weapon keys, but also have a new key that can only be equipped to them. Thanks, Cygames. * Update weapon.rb * Update to check key compatibility against an array instead of an int * Add convenience function to check if the weapon is part of a Draconic Weapon series * Update grid_weapon.rb Update conflict detection to: * Detect Draconic Weapons Providence * Add multiple weapons to conflicting weapons instead of just one * (WIP) Update conflict view rendering Conflict blueprints should render multiple conflict weapons instead of just one. Also adds Draconic Weapon Providence series to various places that check series by number * Finish last bugs We tested to ensure that conflict resolution appears for * Opus and Draconic * Draconic and Draconic 2 * Draconic 2 + Opus and Draconic 1 |
||
|---|---|---|
| .. | ||
| api_blueprint.rb | ||
| awakening_blueprint.rb | ||
| character_blueprint.rb | ||
| conflict_blueprint.rb | ||
| empty_blueprint.rb | ||
| error_blueprint.rb | ||
| favorite_blueprint.rb | ||
| grid_character_blueprint.rb | ||
| grid_summon_blueprint.rb | ||
| grid_weapon_blueprint.rb | ||
| guidebook_blueprint.rb | ||
| job_accessory_blueprint.rb | ||
| job_blueprint.rb | ||
| job_skill_blueprint.rb | ||
| party_blueprint.rb | ||
| raid_blueprint.rb | ||
| raid_group_blueprint.rb | ||
| search_blueprint.rb | ||
| summon_blueprint.rb | ||
| update_blueprint.rb | ||
| user_blueprint.rb | ||
| weapon_blueprint.rb | ||
| weapon_key_blueprint.rb | ||