Any Pooler Documentation

📄 Documentation

*Please note documentation is AI generated (may contains errors) .
You can view the documentation right here:

🔗 Open Documentation in New Tab

Note: Most browsers will open the PDF in a new tab. If yours downloads it, just open the file manually.

✅ Usage Guidelines (Not Enforced)

We don’t force any specific implementation style when using this asset. However, based on performance considerations, we recommend the following best practices for most use cases:

1. void using GetForceObj() frequently. This method is designed for rare or emergency cases where you must retrieve an object, even if the pool is full. It’s currently less optimized and may impact performance in frequent-use scenarios. A more efficient forced-retrieval method will be included in a future update.
2. Avoid using PoolItemInfo for large pools or intensive object sets. This helper is intended for quick prototypes or low-volume pools. For larger setups, we suggest implementing a pool-wide tagging manager that reduces overhead and memory usage.

🔭 Future Roadmap

We’re continuously improving this asset to meet real-world demands. Here’s what’s planned:

• Improved Tagging System: Replace the per-object tagging (PoolItemInfo) with a more efficient pool-wide tag manager.
• Specialized Pool Variants: Add support for pools configured specifically for forced retrieval (GetForceObj()-optimized), suitable for unique cases like high-volume "object waterfalls" or environmental spawners.