globalfreeze change not backwards compatible

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.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: globalfreeze change not backwards compatible

Re: globalfreeze change not backwards compatible

by Graf Zahl » Sat Jan 12, 2019 7:42 am

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.

globalfreeze change not backwards compatible

by AFADoomer » Fri Jan 11, 2019 7:31 pm

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).

Top