FoWEnhanced Extension (all rulesets) - Support Thread

[nephranka]

Thanks for the update!

[nephranka]

I assume we are still awaiting an answer from SW?

[pindercarl]

I assume we are still awaiting an answer from SW?

No. I responded to jharp in a different thread. The data format changed with 4.6 and I believe that this extension is manually updating the database with an outdated header, but I'm not familiar enough with the extension. If jharp has any follow-up questions, he can reach out to me directly [email protected].

[nephranka]

No. I responded to jharp in a different thread. The data format changed with 4.6 and I believe that this extension is manually updating the database with an outdated header, but I'm not familiar enough with the extension. If jharp has any follow-up questions, he can reach out to me directly [email protected].

Thank you for the clarification.

[jharp]

@carl

yes carl answered that question but the underlying bug that another person reported still exists. FoWEnhanced triggers the bug particularly often (always).

jason

[pindercarl]

@carl

yes carl answered that question but the underlying bug that another person reported still exists. FoWEnhanced triggers the bug particularly often (always).

jason

This bug has been fixed and will addressed in the next Release update. This bug only affects maps when metadata is applied, i.e. loading an asset with an accompanying XML file. Not sure if that impacts your extension as I don't know how it works.

[nephranka]

So I did the update from today and a quick test indicates the issue is still present. Just reporting back.

[Moon Wizard]

The issue in the client is fixed.

As @pindercarl has pointed out, the issue with the extension is that it is pulling data from a different data version than what it is writing. That is something that @jharp will need to address in his extension.

Regards,
JPG

[jharp]

So I did the update from today and a quick test indicates the issue is still present. Just reporting back.

Thanks,
I'll confirm the bug is fix from the other thread and if so then I'll try to fix FoWEnhanced.
Jason

[jharp]

@nephranka

Can you test this again. I'm seeing it working as expected. Verify you are running 4.6.4.

I tested with the Savage Worlds campaign and the campaign from the other thread. Both are as expected.

Jason