This commit seems to have completely eliminated the globalfreeze variable, so now any custom actor that used to reference that global variable errors out with an "Unknown identifier 'globalfreeze'" error for each line where it is used.
In my case, this specifically breaks Blade of Agony... I can fix it on my end, but I figured that the lack of a graceful deprecation should be reported (and previous releases are all broken, still).
globalfreeze change not backwards compatible
Moderator: GZDoom Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49067
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: globalfreeze change not backwards compatible
I had to refactor the entire handling for freezing a level because the closer I looked at the code the more broken it appeared and while doing that, added this variable again, but it's deprecated now.