Open klingbolt opened 2 weeks ago
A 4th reason why a category would not have any markers in it is if there are no markers in that category on that map when using map split.
Does this happen for non map-split markers too?
1) This only works for map-split 2) I dont like this idea because it creates a lot of duplicate data in each map file, and then the burrito ui is in charge of pruning that so we are in the same spot as before but with more written data 3) This does not seem like a good idea either, the logic for map split would be "only include this category if it has any markers in it that are on this map unless it does not have any markers in it". 4) How would this be any different from 3 from a speedup standpoint (as 3 was called out for being slow). Additionally this would add complexity to the converter if it were being automatically managed as the converter would need to know when to strip these, which is just option 3 with extra work.
I think that there is also a user story for "I made a marker category on one map, which has markers in it, but now I am on a different map and want to use that category".
I also think that using category / displayname for credits is a bit hacky and not desirable in guildpoint. We might want to just think of a better solution for that problem specifically, which then makes the other usecases intended or ephemeral .
Description
It has been observed that categories which do not contain any POI (Point of Interest) children are not written when the files are split by Map ID. This data then is lost when the split files are recombined.
Current Behavior
When xml_converter is splitting by map_id, the program is iterating over every POI and writing it to a dictionary
"map_id : category_name: [POI]
. Then it iterates over that dictionary by map_id.User Stories
I believe there are at least 3 cases where a category may not have any POI's.
As an example for number 3. The pack "TehsTrails", uses categories to show the credits for the pack creator and those who assisted him as well as contact info. This is all shown using the attribute DisplayName so the info can be shown in the category selector.
Potential Solutions
I've brainstormed a few possible solutions and some complications that arise
I hope to get some other opinions on this and hear other possible solutions.