Skip to content

Commit

Permalink
Fix combat_condition not being insertable on db end
Browse files Browse the repository at this point in the history
  • Loading branch information
killerwife committed Oct 5, 2023
1 parent 5816b0f commit 69cc2cf
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions sql/base/dbc/original_data/CombatCondition.sql
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
DROP TABLE IF EXISTS combat_condition;
CREATE TABLE combat_condition (
CREATE TABLE IF NOT EXISTS combat_condition (
`Id` INT(11) NOT NULL,
`WorldStateExpressionID` INT(11) NOT NULL DEFAULT '0',
`SelfConditionID` INT(11) NOT NULL DEFAULT '0',
Expand All @@ -21,6 +20,7 @@ CREATE TABLE combat_condition (
PRIMARY KEY(`Id`)
);

DELETE FROM combat_condition WHERE Id > 0; -- so that DB can add negative on their own
INSERT INTO combat_condition(Id,WorldStateExpressionID,SelfConditionID,TargetConditionID,FriendConditionLogic,EnemyConditionLogic,FriendConditionID_0,FriendConditionID_1,FriendConditionOp_0,FriendConditionOp_1,FriendConditionCount_0,FriendConditionCount_1,EnemyConditionID_0,EnemyConditionID_1,EnemyConditionOp_0,EnemyConditionOp_1,EnemyConditionCount_0,EnemyConditionCount_1) VALUES
(21,0,21,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0),
(22,0,2,0,0,0,0,0,0,0,0,0,22,0,1,0,0,0),
Expand Down

0 comments on commit 69cc2cf

Please sign in to comment.