Mr. NumNums said:
Seems the majority do want to move folders even in it's current version.
To summarize how it'd work (from what I understand):
1) You can move folders but you can't see what's in said folders just the names.
2. A) They can either have it so it erases any sheets that are duplicated due to the move. (much like how it is now)
2. B)Or it simply duplicates without erasing. (prob lean towards no erasing. Since players can always go and delete extra sheets themselves)
As it stands that's the best they can offer without new updates to the system in place. Later down the line they can make better systems but that's once everything settles with current overhauls etc etc.
So At this point do we need more people signing off?
Fallow this subject to give feedback.
Did join a demo and can confirm that 1 + 2A was shown. This is good enough for some use cases, like:
- pushing a bestiary or lore from a from a master game to other games
- moving curated folders between games
with the caveats:
- items in the target game will be overwritten.
- transfered links can be incomplete - a handout that refers a handout outside of a folder, can have a broken link.
- cannot move over a page/scene with all related objects in one go - pages are not part of the journal folder structure, not all referenced characters/notes might come over.
- attributes of characters need extra handling to prevent issues with edited characters.
As a personal opinion: rather have this version than no version. I can understand these limitations and i can live with these limitations.
There is a fundamental problem with 2B. There is no 'simply duplicates'. Each object has an ID, the ID is globally unique across all objects in this game. Attributes of characters are also objects. Copying an object as a duplicate implies that those objects are assigned new IDs, as there cannot be two items with the same ID. So if you copy over a page and a folder with associated monsters, duplicated objects will not be linked anymore and the links on tokens can be broken. Also, if you drop a folder twice you end up with many duplicates - it is not possible to curate your own bestiary/lore folders and sync those to other games.
As a personal opinion: don't do this. please.
The game copy proposal posted here was a result of joining the demo (thanks for the demo Andrew!) and thinking about the problem like a developer. What can you do given the complexity of reality. The proposal amounted to: Do not touch (ie destroy by accident) the current transmogrifier, or handle folders as per 2A which would be even nicer. Build a new functionality that adds a whole game in a single operation, taking care of object IDs and links. The functionality can be like: When you select a game to import, analyze the contents of both games, provide a meaningful report and then let the user decide how to handle existing objects and folder structures. Whether to keep or overwrite objects, whether to move existing objects to the source journal folder structure or whether the source is a oneshot that has to become a independent silo in the target game.
The report might be like a report as created by Campaign Survey (https://app.roll20.net/forum/post/10675897/script-campaign-survey). Show the amount of objects per type before and after adding, with a warning/limitation to prevent frankenstein games. I tried to break roll20 and if you transmogrify Curse of Strahd into Tomb of Annilihation and then drop in all monsters from the Creature Codex Compendium, you get pretty close to the breaking point - a user needs to at least be aware of reaching this borders.