Nothing happens when finish import about fvtt-adventure-bundler

[Rafal-Pi]

I have no luck finding the bad 'actor'... it seems to not be only related to an 'actor'... can the error message be more in detail, please?
i.e. giving info - which item causes the issue? or an option to 'ignore' and continue?

[dmarcuse]

Sorry for the late response - I haven't had the chance to dig into this issue myself, but the last time I saw this error message, it was related to bad data in the actors. If this is the same issue, then it's not really something I can cleanly fix unfortunately. If you can, I would recommend trying to repeatedly re-create the adventure with subsets of the assets and seeing which ones work, in an attempt to narrow down exactly which documents are causing issues.

Would it be possible to make this module more error-tolerant? For example, if a file can't be loaded during import or found during export, then ... just skip it. Instead of halting the entire process.

I just bundled like 50 maps into a compendium and exported it....but now I can't import it anymore because it goes up to 100% and then gives that "_tombstone" error.

The problem is that this error originates in core Foundry code. I'll have to look into it more when I have the time, but as far as I could determine last time I ran into this issue, the data was valid, but Foundry itself was rejecting it. Adventure bundler wasn't touching the parts of the data that caused the error.

[Rafal-Pi]

Tysiąc Tronów.zip

[Chazori]

Almost the same error as above but for PF2E. Unsure of cause.

foundry.js:753 TypeError: Cannot read properties of null (reading '_tombstone')
at commons.js:6174:16
at Array.map ()
at EmbeddedCollectionDeltaField._cleanType (commons.js:6173:20)
at EmbeddedCollectionDeltaField.clean (commons.js:5074:19)
at ActorDeltaField._cleanType (commons.js:5393:28)
at ActorDeltaField.clean (commons.js:5074:19)
at SchemaField._cleanType (commons.js:5393:28)
at SchemaField.clean (commons.js:5074:19)
at commons.js:6098:41
at Array.map ()
onError @ foundry.js:753
#preCreateDocumentArray @ foundry.js:13537
_createDocuments @ foundry.js:13428
create @ commons.js:8629Understand this error
foundry.js:68326 Cannot read properties of null (reading '_tombstone')

[dmarcuse]

Sorry for the late response - I haven't had the chance to dig into this issue myself, but the last time I saw this error message, it was related to bad data in the actors. If this is the same issue, then it's not really something I can cleanly fix unfortunately. If you can, I would recommend trying to repeatedly re-create the adventure with subsets of the assets and seeing which ones work, in an attempt to narrow down exactly which documents are causing issues.

[Chazori]

I'm going to try and isolate the bad actor and see if I can pin-point the cause, then. Thank you!

[Chazori]

I managed to find the baddie and squashed it. Thanks for the advice!

[orangebutblue]

Sorry for the late response - I haven't had the chance to dig into this issue myself, but the last time I saw this error message, it was related to bad data in the actors. If this is the same issue, then it's not really something I can cleanly fix unfortunately. If you can, I would recommend trying to repeatedly re-create the adventure with subsets of the assets and seeing which ones work, in an attempt to narrow down exactly which documents are causing issues.

Would it be possible to make this module more error-tolerant?
For example, if a file can't be loaded during import or found during export, then ... just skip it. Instead of halting the entire process.

I just bundled like 50 maps into a compendium and exported it....but now I can't import it anymore because it goes up to 100% and then gives that "_tombstone" error.

[orangebutblue]

I have no luck finding the bad 'actor'... it seems to not be only related to an 'actor'... can the error message be more in detail, please? i.e. giving info - which item causes the issue? or an option to 'ignore' and continue?

It's not a "bad actor" issue for me either. I just packed a bunch of scenes (no actors at all) into a pack and can't restore them anymore

[Rafal-Pi]

I will try it on Foundry v12 - maybe will be better.

Is it v12 compatible?

[dmarcuse]

I'm not aware of any changes that would break it, but I haven't tested it myself.