Instantiate more with a max limit and then recycle

Hi,

You are right as well that instantiating during play may slow down the game but it depends on how you use it (like instantiating bullets is not good at all).

Anyways I was able to implement the "Instantiate more with a max limit and then recycle" feature with a small change in the Spawn function, but it doesn't support editor scripting

// Instantiate a new one
var curCount = NumberOfClones(itemSettings);
if (curCount >= itemSettings.ItemHardLimit)
{

itemSettings.AllowInstantiateMore = false;
itemSettings.AllowRecycle = true;
if (itemSettings.AllowRecycle)
{
cloneToSpawn = itemSettings.SpawnedClones[0];
// keep the SpawnedClones and DespawnedClones arrays in line.
Despawn(cloneToSpawn);
}

//Debug.LogWarning(
// "The Transform '" + itemName +
// "' has reached its item limit in Pool Boss. Please increase your Preload Qty or Item Limit.");
//return null;
}


So far it works perfectly fine. Do let me know if this will cause any issues which I'm not able to see at the moment.


How this is more performant in my case -

As it's a sandbox game so it has and will have lots of objects. Currently, the pooled objects counts go up to 1500+ and this will increase with each new item added. So pooling this many objects at the start takes up a lot of memory and also increases loading time.
With this new feature "Instantiate more with a max limit and then recycle", only the required object will get instantiate to a limit, and then it will start recycling. Also, note that objects are not getting Destroyed.

Also, I think you should implement this feature as well as I saw a few more users wanted to implement this.

Thanks
Vineet

Mailed you