You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Export Compendium does not produce json file. It prints an error to the console.
To Reproduce
Steps to reproduce the behavior:
Select"Settings" from the GM menu.
In the "Compendium" section, click "Export Compendium"
Fill in a directory path ("R:"), then a filename ("compendium_exported").
Click Ok.
See error
Error in body of roll. Statement options (if any): h Statement Body : exportData(path+"/"+name+".json",jsonExport,0) Error trace : Json Export All@Lib:Campaign <<< macroLink
Expected behavior
I expect the json file to appear in the specified directory.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows 10
Maptool Version 1.11.5
Framework Version 2.5.7
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I'm happy to say that this is probably an invalid bug. This issue occurs because the Allow External Macro Access option in MapTool's Preferences must be enabled or the "exportData" function aborts with an error. See exportData() docs. I've written a short how-to that could be included on a wiki page here.
Describe the bug
Export Compendium does not produce json file. It prints an error to the console.
To Reproduce
Steps to reproduce the behavior:
Error in body of roll. Statement options (if any): h Statement Body : exportData(path+"/"+name+".json",jsonExport,0) Error trace : Json Export All@Lib:Campaign <<< macroLink
Expected behavior
I expect the json file to appear in the specified directory.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: