ZDoom

Fixed in [url=https://github.com/coelckers/gzdoom/commit/78c0b7f2300c6b8c859e39cbc04c1b7718a9524e]78c0b7f[/url].

[quote="_mental_"]It's a code generation error because construct with a constant condition is valid.[/quote]

Yes, but that means that FxNop may not have an error type. FxNop is meant as a valid stand-in for an empty statement where null is not viable.

It's a code generation error because construct with a constant condition is valid.

[b]TypeVoid[/b] for [b]FxNop[/b] fixes the issue as well. Should we prefer this solution over my PR?

Errors, yes, but this should at most be a warning.

Probably, yes. Actually, I thought [b]TypeError[/b] was used to catch errors like this.

Wouldn't it be better to give FxNop a non-error type instead?

if (const_evaluated_to_false) // ...

It's caused by no-op expressions, like [code]if (const_evaluated_to_false) // ...[/code]
I think this should be fixed like [url=https://github.com/coelckers/gzdoom/pull/735]this[/url].

override void PostBeginPlay()

A mod I released last year has started failing on startup in recent-ish versions of GZDoom. 4 errors that all say "Invalid statement", two of them on the same line. A couple of the lines in question are simple function overrides, eg [code]override void PostBeginPlay()[/code], and no further information is given so it's pretty unclear what the real problem is or how to fix it.

You can download the latest released version of the mod here: https://jp.itch.io/mr-friendly