ZDaemon

Reconsidering this case, however moving this to the deferred section.

Design considerations.

Rejecting this case.

Provide more detail please.

Include exactly what you were loading, wads, settings and all for replication purposes.

It wasn't a bug, so no.

Just an erroneous entry.

Locked.

Located and fixed.

Similar to the other topic you posted of this nature, this one has been moved to the deferred section since a lot of internal investigation is required.

Deferred but not rejected.

This has been marked as fixed in a subsequent version.

Stop nitpicking.

Confirmation occurs after material has been examined by us.

Further replies will be made once this case is revisited.

Feel free to ask about it in private next time.

Other tests had to be performed before confirming; however as a result of what is occurring, it is confirmed but deferred.

This behaviour will be possible in 1.10.20 by way of two new dmflags3.

If both new dmflags3 are disabled then the existing behaviour is maintained.

Detail:
https://www.zdaemon.org/ktarticle.php ...

Thank you.

In this case if you could record a standard ZDaemon demo, that'll be what's needed in this context.

Thank you though.

Do you happen to have a demo of said behaviour? or are able to record one with the current version and provide a link to it here?

If yes, indicate the precise steps that were taken to get to the po ...

This behaviour will be possible in 1.10.20 by way of two new dmflags3.

If both new dmflags3 are disabled then the existing behaviour is maintained.

Detail:
https://www.zdaemon.org/ktarticle.php ...

Moved this to the deferred section since a great deal of investigation is required before any potential possibilities can be derived.

It hasn't been rejected.

We'll see what shakes out over time in that case.

As far as uncapped goes, that won't have any basis on what is transmitted to the server.

As for the "player1" / "player2" effect, that is a tough one, since that behaviour is wh ...

At a base level this topic brings up two subject matters:
1) Uncapped
2) Unlagged

Both are two completely different cases.

Keep the topics entirely separate to avoid conflaction.

Also Titan ...

Moving to confirmed; thank you ZeroDev.

For reference if you want to ask about a bug, you must provide detail.

Given that you've referenced something from 15 years ago, you really must provide detail otherwise how are we supposed to know ...