Monitor221hz / Pandora-Behaviour-Engine-Plus

Patcher for behavior, character, and skeleton project files for Skyrim Special Edition.
GNU General Public License v3.0
239 stars 11 forks source link

[Bug]: MCO cannot be patched #157

Closed Roidtakor closed 3 months ago

Roidtakor commented 3 months ago

Version

1.2.2a

Provide Instructions on Reproducing the Problem

Pandora aborts patching of MCO 1.6.0.6. with the message. "CRITICAL FAILURE

If the cause is unknown: submit a report to the author of the engine and attach Engine.log Launch aborted. Existing output was not cleared, and current patch list will not be saved."

I just ticked MCO for testing and nothing else.

Skyrim 1.6.640

Provide Relevant Files

Engine.log

Provide Visual Proof (optional)

No response

Contributing To Development

Monitor221hz commented 3 months ago

Unreproducible so far. Have you tried reinstalling both MCO and Pandora? And made sure there isn't any file overwriting MCO files?

Roidtakor commented 3 months ago

I was almost desperate, because everybody else can patch MCO with Pandora. So after some time I found out, that the mod Jump Attack has overwritten one single file of MCO. As I'd disabled Jump Attack Pandora has patched MCO in less than 1 sec. I'm sorry for wasting your time.

elbadcode commented 3 months ago

This was previously addressed in another issue, though I'm not sure if its mentioned anywhere else. You have to take that one file from jumpingattack and change 10 to 8 both in the file name and inside the text itself for it to work with the latest few versions of MCO

Monitor221hz commented 3 months ago

oh right, I had an overwrite packaged for that in earlier versions but it got deleted along with the sweeping changes to the new pandora format. I'll restore it soon

Monitor221hz commented 3 months ago

https://github.com/Monitor144hz/Pandora-Behaviour-Engine-Plus/issues/47#issuecomment-1873468727 @Roidtakor here's the fix if you still want to use jump attack.

I've decided against including the fix in pandora as it's too volatile to change, and isn't the engine's area of responsibility.

Roidtakor commented 1 week ago

@Monitor221hz thank you.