-- these only need to be added once
INSERT OR REPLACE INTO Types (Type, Kind)
VALUES ('MODIFIER_PLAYER_ALLOW_PROJECT_BUILDING_REMOVAL_LRS', 'KIND_MODIFIER');
INSERT OR REPLACE INTO DynamicModifiers (ModifierType, CollectionType, EffectType)
VALUES ('MODIFIER_PLAYER_ALLOW_PROJECT_BUILDING_REMOVAL_LRS', 'COLLECTION_OWNER', 'EFFECT_ADD_PLAYER_PROJECT_AVAILABILITY');
-- one each of these is needed for each Building Removal Project, re-using ModifierType 'MODIFIER_PLAYER_ALLOW_PROJECT_BUILDING_REMOVAL_LRS'
-- each of these individual setups needs its own ModifierId & SubjectSetRequirementId
-- the code does NOT include the method to attach these modifiers to all players, which will need an additional set of table inserts
-- it may also be necessary to use an OwnerRequirementSetId instead of 'Subject' -- the game is a bit strange sometimes as to when it wants Owner and when it wants Subject
INSERT OR REPLACE INTO Modifiers (ModifierType, ModifierId, SubjectSetRequirementId)
VALUES ('MODIFIER_PLAYER_ALLOW_PROJECT_BUILDING_REMOVAL_LRS', 'MODIFIER_ALLOW_PROJECT_REMOVE_GRANARY_LRS', 'PLAYER_HAS_GRANARY_TECH_LRS');
INSERT OR REPLACE INTO ModifierArguments (ModifierId, Name, Value)
VALUES ('MODIFIER_ALLOW_PROJECT_REMOVE_GRANARY_LRS', 'ProjectType', 'PROJECT_REMOVE_GRANARY_LRS');
INSERT OR REPLACE INTO Requirements (RequirementId, RequirementType)
VALUES ('REQUIRES_PLAYER_HAS_POTTERY_LRS', 'REQUIREMENT_PLAYER_HAS_TECHNOLOGY');
INSERT OR REPLACE INTO RequirementArguments (RequirementId, Name, Value)
VALUES ('REQUIRES_PLAYER_HAS_POTTERY_LRS', 'TechnologyType', 'TECH_POTTERY');
INSERT OR REPLACE INTO RequirementSets (RequirementSetId, RequirementSetType)
VALUES ('PLAYER_HAS_GRANARY_TECH_LRS', 'REQUIREMENTSET_TEST_ALL')
INSERT OR REPLACE INTO RequirementSetRequirements (RequirementSetId, RequirementId)
VALUES ('PLAYER_HAS_GRANARY_TECH_LRS', 'REQUIRES_PLAYER_HAS_POTTERY_LRS')
were not in the original text and were not intended -- thank you forum parser code.
