[HELP] Issues loading Blade of Agony as IPK3 file

[Ozymandias81]

Recently I have done some fixes and implemented dummy placeholders such as SCRIPT00 and ORB sound due to silence some console warnings...
So everything was fine since gzdoom-3.4pre-345, but then stumbled now with this issue, which even happen on previous builds of GZDoom now.

CrashReport_WolfBoA_r253.zip

Old build, this was working fine before now doesn't

(14.35 KiB) Downloaded 32 times

CrashReport_WolfBoA_r387.zip

Happens the same with this and previous builds, can't track what's going on

(14.49 KiB) Downloaded 29 times

I can't build an example since idk what's going on, game runs fine with Doom2.wad and Freedoom.wad.
Anyone got some clues? Everything has been test with "fresh" builds of GZDoom, so no old .ini settings and sorta

PS: Crash happen even if I delete mentioned dummy lumps.

[Rachael]

Make sure you download GZDoom to the very very latest. A build was just dispatched less than an hour ago.

[Ozymandias81]

Make sure you download GZDoom to the very very latest. A build was just dispatched less than an hour ago.

Thanks, will try now and well I tested with r387 as you can see... Surely I should have been more patient, but well recently we got some crucial issues with GZDoom and that's why I decided to open this thread.
Let's see then, gonna test

[EDIT]: No way, still happens the same problem

[_mental_]

How can I build the same ipk3 myself? From your GutHub repo?

[Ozymandias81]

How can I build the same ipk3 myself? From your GutHub repo?

Yes, just run the "build.bat" file then rename the .pk3 as .ipk3 and that's all

[_mental_]

Fixed in 2c2b19b.

[Ozymandias81]

Thank you, so it was a bug! Thought so on first time to post on Bugs but wasn't sure.

[_mental_]

If the engine crashes, i.e. if it aborts with Very Fatal Error dialog where you can save a report, then it's a bug.
It can be a known bug but it can be a something new. It's always better to have duplicate reports than to do not have any.