ZDoom

Fixed in [url=https://github.com/coelckers/gzdoom/commit/e353201919a58a19bbab574e17709daafe5b2b9b]e353201[/url].

The other checks would be crash issues, but that particular one needs to be disable for Dehacked-modified states, because the non-Actor functions that can be set here would otherwise cause an abort. All Dehacked-usable functions should contain enough safety checks to not crash.

Is it about disabling of [url=https://github.com/coelckers/gzdoom/blob/159b45bd4602f81073bbdf2917eaad06d7522116/src/info.cpp#L138-L141]this check[/url] if the state was modified by Dehacked? Or is it about a whole [url=https://github.com/coelckers/gzdoom/blob/159b45bd4602f81073bbdf2917eaad06d7522116/src/info.cpp#L124-L155]FState::CheckCallerType()[/url] function?

While the check is correct, it needs to be disabled if a state gets modified by Dehacked.

The issue was introduced in [url=https://github.com/coelckers/gzdoom/commit/0a21d1972363cea3452ce2e7da4653e21155ec2f]this commit[/url]. It affects 3.7 release too.

[imgur]https://imgur.com/oeTac0F[/imgur]

[url=http://heroestospare.com/rabotik/harmony.php]Harmony is available here[/url]

When shooting any of the "ExplosiveBarrel" types in Harmony, a VM abort is immediately caused. This happens even with +vm_jit 0.