From dc4f905097e9644f6a8dafaa23a9dcaf485b25f1 Mon Sep 17 00:00:00 2001 From: Logan Date: Mon, 21 Jan 2019 19:28:59 -0800 Subject: [PATCH] Updated Project PEQ Expansions Concept Doc (markdown) --- Project-PEQ-Expansions-Concept-Doc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Project-PEQ-Expansions-Concept-Doc.md b/Project-PEQ-Expansions-Concept-Doc.md index 7406211..3cd30ef 100644 --- a/Project-PEQ-Expansions-Concept-Doc.md +++ b/Project-PEQ-Expansions-Concept-Doc.md @@ -6,9 +6,9 @@ This document describes the challenges and solutions to creating a dynamic-expan - 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 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. + - adventure_template: add expansions field - char_create_combinations: expansions_req contains this data - - doors: Does this need expansion? I'm leaning no, zone will determine + - doors: add expansions field - fishing: add expansions field - forage: add expansions field - global_loot: add expansions field