Nothing eternal under the moon...Rachael wrote:There's no way to guarantee it will still work in future versions.
[3.4.1?] CanCollideWith() + destruction/damage desync+crash
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.
Re: [3.4.1?] CanCollideWith() + destruction/damage desync+cr
-
- Posts: 805
- Joined: Thu Apr 25, 2013 12:21 pm
- Preferred Pronouns: They/Them
- Operating System Version (Optional): Windows 11 for the Motorola Powerstack II
- Graphics Processor: nVidia with Vulkan support
- Location: The Corn Fields
- Contact:
Re: [3.4.1?] CanCollideWith() + destruction/damage desync+cr
I feel like this is one of those things that perhaps we should change to be const because if it breaks the engine that much, it probably shouldn't be allowed.
I know a lot of ZScript mods and TCs exist but if it's that easy to break the engine, it should be considered faulty by design... maybe we should have a discussion here about that, see what other mod authors say and suggest fixes to said code with this flaw.
This is one of those instances where I'm afraid no matter what direction we're gonna take, some major rewriting to ZScript code will need to be done, probably at a performance hit, but it beats using unsafe code. Either that or keep using unsafe code and hope it doesn't cause major errors if used carefully.
I know a lot of ZScript mods and TCs exist but if it's that easy to break the engine, it should be considered faulty by design... maybe we should have a discussion here about that, see what other mod authors say and suggest fixes to said code with this flaw.
This is one of those instances where I'm afraid no matter what direction we're gonna take, some major rewriting to ZScript code will need to be done, probably at a performance hit, but it beats using unsafe code. Either that or keep using unsafe code and hope it doesn't cause major errors if used carefully.