Quote from: Joshex on May 27, 2025, 05:09 PMthis does not display PvP information, and currently would only cover "Info tab" information, where "Effects tab" information will have to be an additional {"Effects":[{}]} entry. I'm debating how to store PvP information. perhaps each attribute with have 2 sub dictionaries {"pve": value} and {"pvp": value} or perhaps I'll do 2 different entire dictionaries Under ['PowerName'] like ['PowerName']['PvE'] and ['PowerName']['PvP']...
The tricksy thing is that not every power has separation of effects for PvE vs PvP, they just do exactly the same thing in both contexts (so why separate/duplicate?).
And then you've got PvP Enhancement Sets that have different global set bonuses depending on what context you're in (the enhancement values remain unchanged).
Simplest solution (that I can think of, anyway) is that everything defaults to PvE context, but there will be a toggle option to switch to a PvP context (kind of like toggling between Hero and Villain in Mids'?) and then *IF* there are PvP data entries for things, they'll "overwrite" the PvE data with PvP data for computation through everything downstream of the lookups.
Quote from: EDekar on May 27, 2025, 08:26 PMDon't forget that there are also Challenge sets whose secondary set effects only activate while on a Task Force challenge (or whatever the condition may be)!
And that's another level of complication. Fortunately, to my knowledge, NONE of those Challenge sets have a PvE vs PvP context differential to them ... but designing the code structure around that fact could be a case of premature optimization.
Probably best to have an additional toggle option for Challenge: Y/N? and you'd be able to set it up such that (right now) the Challenge toggle would automatically toggle the PvE/PvP setting back to PvE. Doing things that way then makes it easier (later) if a PvP Challenge Set gets introduced and you need to enable that particular combination of setting at a later date.
