[HL2MP] Make info_null and infodecal server-side#1046
Closed
speedvoltage wants to merge 1 commit into
Closed
Conversation
|
That is not an issue. That is stating a fact without explaining anything. |
Contributor
|
Partial duplicate of #910? |
|
How does this affect named decals? How does the client know where to apply the decals? |
Bitl
added a commit
to FIREFIGHT-RELOADED/FIREFIGHT-RELOADED-src-sdk-2013
that referenced
this pull request
Mar 31, 2025
It seems decals are networked using a different system from the edict system, so yes, it is safe to de-edict them. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue:
The
info_nullandinfodecalentities are currently not server-side, which leads to unnecessary networked edicts.info_nullserves as a placeholder or temporary entity, but it still gets briefly networked. This can lead to crashes due to hitting entity limits, especially on maps filled with temporary entities.infodecalis used for applying decals but doesn’t need to be sent to clients. On larger maps, having too manyinfodecalentities can lead to edict exhaustion and, thereby, can cause crashes.Fix:
info_nullserver-side only to stop it from being networked. This will help reduce crashes related to entity limits by allowing it to exist for a tick before being removed without being networked.infodecalto be server-only to cut down on unnecessary edict usage. Since decals are usually static, they don’t need to be replicated on the client side. This will help avoid running out of edicts, especially on larger maps with numerous decals.