Database structure for (future) support of saving quest data that is globally valid for all chars (this will support, for example, saving when a grandboss gatekeeper should become available again).

datapack_development/sql/quest_global_data.sql

@@ -0,0 +1,12 @@
+-- ----------------------------
+-- Table structure for global quest data (i.e. quest data not particular to a player)
+-- Note: We had considered using character_quests with char_id = 0 for this, but decided 
+-- against it, primarily for aesthetic purposes, cleaningness of code, expectability, and
+-- to keep char-related data purely as char-related data, global purely as global.
+-- ----------------------------
+CREATE TABLE IF NOT EXISTS `quest_global_data` (
+  `quest_name` VARCHAR(40) NOT NULL DEFAULT '',
+  `var`  VARCHAR(20) NOT NULL DEFAULT '',
+  `value` VARCHAR(255) ,
+  PRIMARY KEY  (`quest_name`,`var`)
+);

datapack_development/tools/database_installer.bat

@@ -582,6 +582,7 @@ pets.sql
 pets_stats.sql
 pledge_skill_trees.sql
 posts.sql
+quest_global_data.sql
 raidboss_spawnlist.sql
 random_spawn.sql
 random_spawn_loc.sql

datapack_development/tools/database_installer.sh

@@ -321,6 +321,7 @@ $MYG < ../sql/pets.sql &> /dev/null
 $MYG < ../sql/pets_stats.sql &> /dev/null
 $MYG < ../sql/pledge_skill_trees.sql &> /dev/null
 $MYG < ../sql/posts.sql &> /dev/null
+$MYG < ../sql/quest_global_data.sql &> /dev/null
 $MYG < ../sql/npcskills.sql &> /dev/null
 $MYG < ../sql/raidboss_spawnlist.sql &> /dev/null
 $MYG < ../sql/random_spawn.sql &> /dev/null