Auto Start Waves Off

Sorry but I've never had "can't auto spawn" problem, and no one has reported it. I suspect that's your main problem and the others are side effects. Is there an error in the Console? If not, I suggest you delete LevelWaveSettings and start over. I think you must have done *something* to mess it up but I have no idea what unless you send me your project. Quite strange.

I just tried with a fresh copy of Core GameKit from the Asset Store and turning off Auto Start Waves works fine after calling Unpause Wave. I also never see it say "wave 0".

Yeah then it most likely happened because of some code mod you did.

If you figure it out let me know. As I said no one has ever reported this.

All right.

Let’s clear it up. Actually, you are using Pool Boss. Absolutely everything that spawns in Core GameKit uses Pool Boss, even if you’re using a Prefab Pool instead of “Specific” prefab in the Inspector. Once another person asked “why can’t you just combine the 2 (Prefab Pool and Pool Boss), but it wouldn’t allow the flexibility. They serve different purposes. Explanation below.

Pool Boss is strictly for pooling (i.e. avoiding all Instantiate and Destroy calls). Here you specify the max number of each prefab that you will need (and create up front on Awake). Any time a prefab is spawned, whether it came as a random prefab from a Prefab Pool or “specific”, it uses Pool Boss.

Prefab Pools are an *optional feature*, and are strictly for probability-based, non-prefab-specific spawning. So that prefab A can be spawned twice as often as Prefab B, etc. In use, only a random Transform is returned from the chosen Prefab Pool, and then that matching prefab’s item in Pool Boss is used when it spawns. We could not add this weighted random functionality into Pool Boss because it would not allow you to make 2 different Prefab Pools with the same prefab in different probabilities (Pool Boss does not allow a single prefab more than once). Prefab Pools are an optional feature, but Pool Boss is mandatory for Core GameKit usage.

It is definitely unfortunate that we have 2 features with the word “pool” in them. Any suggestions if you understand how this works now?

About the wave setting, actually we shouldn’t be allowing 2 settings of the same level/wave. A spawner cannot track that. I didn’t think to add a detection for that error state. The next version will have this and log an error to the Console if this happens.

Ok cool.

I didn't see any console messages, but maybe they were there. I usually only look at console messages if I have my own debug in there. I generally don't see console output from an asset unless it's error messages that don't allow the game to run. It's somewhat unusual to take a warning approach to something that is a game-breaker. I personally would prefer that it didn't even allow the creation of additional wave settings if they aren't going to work anyway. No worries though. I know not to do that again and I'll certainly look at the console window in the future if Core Gamekit doesn't seem to be working as I would expect.