From cf9d1f4daa69a275503609278ac34f9c7113290f Mon Sep 17 00:00:00 2001 From: Logan Date: Mon, 21 Jan 2019 19:04:26 -0800 Subject: [PATCH] Updated Project PEQ Expansions Concept Doc (markdown) --- Project-PEQ-Expansions-Concept-Doc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Project-PEQ-Expansions-Concept-Doc.md b/Project-PEQ-Expansions-Concept-Doc.md index 12036f8..68e6dbf 100644 --- a/Project-PEQ-Expansions-Concept-Doc.md +++ b/Project-PEQ-Expansions-Concept-Doc.md @@ -5,7 +5,7 @@ This document describes the challenges and solutions to creating a dynamic-expan ## Areas of Concern - Load data based on expansion: Add a new expansion TINYINT(4)? to many tables to allow dynamic loading. - aa tables: This is handled I believe with db_string? Verify - - account: This stores the expansion value per account, used by other tables. + - account: This has an expansion field however it used to limit a specific account with a lesser-version expansion. Rule should be honored for the global expansion version - adventure_template: Since multiple expansions add different styles of adventures, add support for this. - char_create_combinations: expansions_req contains this data - doors: Does this need expansion? I'm leaning no, zone will determine