RedM Pool Sizes
RedM has internal limits called "Pools" that manage various entities, objects, and resources. When a server exceeds these limits—often due to high-quality mappings or many scripts—it can cause clients to crash with errors like Object Pool Overflow.
To prevent this, you can manually increase these pool sizes in your server configuration.
Recommended Overrides
Below is a list of common pool size increases recommended for servers running custom SPOONI mappings or extensive script setups.
| Pool Name | Recommended Size | Use Case |
|---|---|---|
Object | 2000 | General world objects and props. |
DrawableStore | 50000 | Model and texture loading limits. |
TxdStore | 26000 | Texture dictionary capacity. |
CDoorExtension | 160 | Custom interactable door limits. |
CAvoidanceComponent | 1300 | AI/Player pathing avoidance. |
AttachmentExtension | 430 | Entity attachments and props. |
CPropSetObjectExtension | 950 | MLO and prop set handling. |
OcclusionPathNode | 1500 | World visibility and occlusion. |
netGameEvent | 400 | Network event synchronization. |
How to Implement
To apply these changes, add the increase_pool_size command to your server.cfg file.
IMPORTANT
These lines must be placed at the very top of your server.cfg, before any resources are started.
Example server.cfg snippet:
# === Pool Size Overrides ===
increase_pool_size "Object" 2000
increase_pool_size "DrawableStore" 50000
increase_pool_size "TxdStore" 26000
increase_pool_size "AttachmentExtension" 430
increase_pool_size "CDoorExtension" 160
increase_pool_size "CAvoidanceComponent" 1300
increase_pool_size "CPropSetObjectExtension" 950
increase_pool_size "netGameEvent" 400
# ... add others as needed
# === Standard Server Config ===
endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"
# ...TIP
If you are experiencing specific crashes, check our Crash Codes Guide to identify which pool might be overflowing.