Add-ons nest within add-ons…

Purchased Where Evil Lives from MCDM. Added the first add-on, no issues. Any add-on added after that nested its Journal subfolders within the first add-only top level folder. (So multiple “Treasure,” “Handouts,” etc. folders under the first add-on’s folder.) I had to look within the folders to see what went with what and separate them out…

Hi RPGeezer,  Can you supply a screenshot of the nesting? Or which addons are being combined?  They should not be nesting like that. 

Since I had fixed that one I whipped up a new game and the behavior repeated (Tomb of the Keeper was the first add-on added.) I then tested an add-on NOT from the same book and it landed correctly (outside of the others,) so maybe its a same book (in this case Where Evil Lives) issue?…

It could be, or it could be that the creator did not use proper procedure. Can you supply the Marketplace links to the products?

Purchased it through DriveThruRPG but the Roll20 link is&nbsp; <a href="https://marketplace.roll20.net/browse/bundle/28641/where-evil-lives" rel="nofollow">https://marketplace.roll20.net/browse/bundle/28641/where-evil-lives</a>

And the other addons? Or is the issue with the others in this product?

The add-ons included in this one product are the issue. Added three from this one…

By the looks of it this author did not use proper procedure for creating their game. They reused some of the structures and as a result there is grouping where there shouldn't be.&nbsp; It also looks like all addons dump their maps into the original folder for the addon and renames it.&nbsp; Your options are:&nbsp; 1) Fix it yourself (as you have been doing) 2) Ask for a refund:&nbsp; <a href="https://help.roll20.net/hc/en-us/articles/360037254314-Refund-Policy" rel="nofollow">https://help.roll20.net/hc/en-us/articles/360037254314-Refund-Policy</a> If it is after the 15 day refund period you may still be able to get a refund if you can show the product is flawed. Make sure you cite every collision or incorrect grouping when doing so.&nbsp; 3) File a report with the Roll20 Devs, and also with MCDM Products and then hope something is done someday to fix it.&nbsp;

I will just work with it for now and maybe reach out to the Devs to give hem a heads up. Thanks for the help.