virtuesky/sunflower

Core ScriptableObject architecture for building Unity games (Android & Ios)

sunflower's Issues

Have you looked into this project, it's creating something similar to your idea. https://github.com/pancake-llc/foundation

Admob Missing dependencies cause crash when registering AppStateChanged callback

googleads/googleads-mobile-unity#2645

What is the advantage of Spawner Script to have reference of object, if we also have to passing it to pool each time for Spawn

What is the advantage of Spawner object to have reference of spwanAble object.

Like here

using UnityEngine;
using VirtueSky.ObjectPooling;

public class TestPools : MonoBehaviour
{
    public Pools pools;
    // The Pool also have the same gameobject reference for pooling game object on Initializefor prewarm.
    public GameObject coinPrefab;

    private void Start()
    {
        pools.Initialize();
    }

    public void SpawnCoin()
    {
        // what is the advange of passing the prefab again to pool
        pools.Spawn(coinPrefab);
    }

    public void DeSpawnCoinPrefab()
    {
        pools.Despawn(coinPrefab);
    }
}

Reference: https://github.com/VirtueSky/sunflower/wiki/Object-Pooling

Can we have a discussion for this project

I have a suggestion, can we use Tri-Inspector

https://github.com/codewriter-packages/Tri-Inspector

Currently, there is no way of adding Tri-Inspector for Attributes for inspector as VirtueSky.Attributes takes over the Inspector rendering.
As it has more feathers regarding attributes (it supports button with Parameter).

If not possible for some reason, can you tell me why. I mean, I have no problem with using different attributes system. I just want a good reason to tell myself that it's fine.