ZDoom

Thats easy....Todd Howard.

Simplest way is to set 'door' moving speed to some ridiculously high, so it will move instantly on activation, and set line activation flags ONLY to projectile/hitscan hit in map editor. I.e. on hit it will move into the ground/ceiling. Put several such 'doors' close to each other and you have a ...

Github set a deadline on 6 october 2023, for me, to setup 2FA. According to official page https://github.blog/2023-03-09-raising-the-bar-for-software-security-github-2fa-begins-march-13/ it block my account from accessing githuib features which is....what exactly? It will straight up lock me from ...

Throw abort exception, if used in static event handlers on register virtual, are able to prevent gzdoom from loading further than line with a throw, after it finishes parsing scripts. Is this legal aka wont break(s) in future versions/something in gzdoom, like infamous ini file corruption bug?! Im ...

Ah yes, everything is a pointer in zscript...
Why it works with zscript arrays than?! array<int> list[3] supports list[0].push(1) without crashing.

Unless we talking about different things, c++ do this.
https://godbolt.org/z/Kq4Y33qfM
Yes there are hidden obligatory constructor calls, but point is, its not like in zscript static array are just a malloc call and thats it.

Probably more 'missing feature' than 'bug'. C like arrays (type name[number]) are missing implicit instantiation of an objects if its type is a user defined object. Next code class debug_build : eventhandler { vector_wrapper vec[3]; override void NetworkProcess (ConsoleEvent e) { if(e.name == "bug ...

Test example. line_iterator_bug.zip Start new game with it and type in console 'netevent bug'. Code BlockLinesIterator it = BlockLinesIterator.CreateFromPos(players[e.player].mo.pos, 64, 64); array<line> arr; arr.clear(); while(it.next()) arr.push(it); for(int i = 0; i < arr.size(); i++) console ...

Well, exception from destructor if there are already some exception happened, lead to instant termination of a program, but that not the point and not entirely what I meant. Just to be clear, this version "3.8" const MAX_SIZE = 6; class thing : thinker { pointer others[MAX_SIZE]; static thing ...

Out of curiosity, how often it (reset master/dev to some really old commit) happens in 'enterprise' development?

Found a reason. Overridden ondestroy virtual have leftover code from previous revision that writes pointer without checking is it null or not. So it goes like Gzdoom executes 'out of array bounds' bug crashes tries to destroy loaded level and all related to it data enters into overridden destructor ...

Yes, its not a ternary operation, its out of array bounds bug. Commenting aforementioned 6 lines also comment array access functions, since condition and array access related function are in one line. What is weird here is that instead of crashing after first out of bounds write, like it always ...

Multiple ternary operations in a row that have multiple checks inside of each, a la ( (condition && condition && condition) ? something : something), causes firstly vm crash with error message "DestroyAllThinkers failed" and than, on exit from Gzdoom, hard crash with a very dead marine. Reproducing ...

I have function that collect one sided map lines and then sort them into a groups of closed outline aka group of lines that 'draw' closed polygon. It works, but it also create groups of 'empty' sectors. On the example of a picture new.jpg it filter lines in three groups, rectangle, square and weird ...

Since there are no "new forum designs feedback" topic and this is the only relatively related topic: drd theme is a bit 'acid' prosilver dark edition is bit "dim" other themes are fine, except purplexion. Its a gzdoom forum not purplexion. + Probably color rendering quirks of my monitor.