Quake3World

Eraser wrote:

Code: Select all

void SP_info_null( gentity_t *self ) {
	G_FreeEntity( self );
}

I doubt info_null counts towards that limit?

You speak the truth. I wasn't aware of that.

dghost77 wrote:I'll have to leave more room for entities then, so I guess that all shots being fired in a map count as an entity? Even the machine gun shots?

No. Hitscan weapons use a different system. Only rockets and bolts (RL, GL, PG, BFG) take up entity slots.

ah ok, thx for the precision.

Isn't there this 256 func_door limit too?

I believe that dead bodies and gibs count as well - part of that goes toward the allocation of 64 for players - unless you had 64 players and then it would roll over into the remainder of the 1024 entities.

MrLego wrote:I believe that dead bodies and gibs count as well - part of that goes toward the allocation of 64 for players - unless you had 64 players and then it would roll over into the remainder of the 1024 entities.

I'm not sure about dead bodies, but gibs certainly don't. They're client side things. The server doesn't even know there is such a thing as a gib.

The server doesn't care about gibs or bodies but they still apply towards the entity count on the client side.

Once you hit the limit things start to randomly blink in and out or just disappear completely.

I have seen this more times on RTCW and Enemy Territory maps where there are more scripted events happening - Quake 3 maps are more run & gun and usually don't contain all of the extra eye-candy gamemodels.

MrLego wrote:The server doesn't care about gibs or bodies but they still apply towards the entity count on the client side.

Yeah but this is not directly related to the number of entities in maps. The client will only hold a list of entities that are of relevance to the client, so if there's 1000 entities elsewhere in the map, those won't be present on the client and won't work towards the client's entity limit.