So - yes - some mods broke in 4.14.0.

Here, developers communicate stuff that does not go onto the main News section or the front page of the site.
[Dev Blog] [Development Builds] [Git Change Log] [GZDoom Github Repo]

Moderator: GZDoom Developers

User avatar
luigiman0640
Posts: 102
Joined: Mon Apr 28, 2014 6:18 pm
Graphics Processor: nVidia (Modern GZDoom)

Re: So - yes - some mods broke in 4.14.0.

Post by luigiman0640 »

I'm down for this change, but would this be the reason why some mods are just, like, hard locking on me? Namely dying in CherubCorps's "Showtime!!!" and firing the starting pistol in Slayer's Rampage v2.0. Both of these cause GZDoom to completely stop responding. Not asking for fixes here, just asking if they're related to the ZScript patch.
User avatar
Enjay
 
 
Posts: 26632
Joined: Tue Jul 15, 2003 4:58 pm
Location: Scotland

Re: So - yes - some mods broke in 4.14.0.

Post by Enjay »

In my experience, problematic scripts are caught as GZDoom loads and the errors are reported in a meaningful way.

More conclusively, I just tried Slayer's Rampage in GZDoom 4.14.0 and a test build from before the stricter script check was put in place. Both hung when I fired the pistol.
User avatar
luigiman0640
Posts: 102
Joined: Mon Apr 28, 2014 6:18 pm
Graphics Processor: nVidia (Modern GZDoom)

Re: So - yes - some mods broke in 4.14.0.

Post by luigiman0640 »

Okay, yeah, that makes more sense but has less answers. Thanks for that, either way.
User avatar
Zhs2
Posts: 1290
Joined: Fri Nov 07, 2008 3:29 pm
Graphics Processor: ATI/AMD with Vulkan/Metal Support
Location: Maryland, USA, but probably also in someone's mod somewhere

Re: So - yes - some mods broke in 4.14.0.

Post by Zhs2 »

I'm sure infinite freezes still work as they used to. Sounds like a modder didn't ensure that a state doesn't 0-tic loop to me.

Return to “Developer Blog”